l3montree-dev / l3montree-dev/devguard
Improve links in container scanning output
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
Currently when reviewing container-scanning outputs we see the vulnerabilities which exceed the threshold but still have to click the link below and copy the purl which can be simplified by a direct link to the vulnerability in DevGuard.
Additionally we could add a general link at the bottom to the vulnerability risk page but with the threshold filter applied, directly showing all vulns which need to be handled.
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 at the code that generates container-scanning output and trace how vulnerability links are currently assembled from the purl. Check the existing DevGuard vulnerability risk page and its filter parameters. Done means threshold-exceeding vulnerabilities link directly to their DevGuard entries and a bottom link opens the filtered risk page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100