l3montree-dev / l3montree-dev/devguard
Automatic Vexing of Withdrawn Vulnerabilities
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
When managing vulnerabilities, a lot of time could be saved if withdrawn vulnerabilities either could be filtered for and handled all at once, or even if DevGuard goes ahead and handles them for you automatically.
The vulnerability database already collects the withdrawn tag, but a decision would have to be made how to allow the user to make use of it in a transparent manner.
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
Start by tracing how the vulnerability database's withdrawn tag enters DevGuard's vulnerability-management flow. The issue leaves filtering versus automatic handling open, so first clarify the transparent user-facing behavior and its scope. Done means one approach is defined and implemented with appropriate coverage for withdrawn vulnerabilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100