New Check: time to fix security vuln
Open
Nobody has claimed this yet.
kind/enhancement
- Dominant language
- Go
- Stars
- 5.7k
- Forks
- 724
- Avg merge
- 19h 30m
- Merged PRs (30d)
- 1
Description
It would be nice to be able to provide insight into the time it takes for developers to fix issues, ie how responsive they are. That's not super easy since bugs have various levels or priority (critical vs medium vs etc).
OSV may be a good source of data for this. We could try to mine github data but that seems harder.
@jeffmendoza FYI
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. First clarify whether OSV or mined GitHub data will be the source, how vulnerability priority affects the metric, and what the new check should report; done means a defined, implementable measure of time to fix security vulnerabilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- analytics, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100