feat: use namespace with name for golang purl decoder #2636
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #2580
Description
Currently the PURL decoder is too aggressive when constructing
name
for golang packages.pkg:golang/k8s.io/ingress-nginx@v1.11.2
will useingress-nginx
as the package name. When doing a search of the v6 db this would returnno results
for popular vulnerabilities like GHSA-mgvx-rpfc-9mpv.These vulnerabilities are instead stored under:
More complex paths also exist as names like the following
These commands can be used to view the related vulnerability records in grype:
This PR updates the PURL provider to use namespace && name for the package name so searching the DB provides better results when submitting queries by PURL.