Consider supporting embedded CPEs in package URLs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 271
- Forks
- 129
- Avg merge
- 3h 46m
- Merged PRs (30d)
- 4
Description
https://github.com/anchore/grype/blob/dfa540f727454da3172bc0cc5b5bc36a925bbd04/grype/pkg/purl_provider.go#L45 is doing something interesting with embedded CPE strings as part of the package URL, e.g.
It might be worth considering explicitly supporting this behaviour in the OSV Schema and in OSV.dev.
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 reviewing the referenced grype/pkg/purl_provider.go code and grype/pkg/test-fixtures/valid-purl.txt, then inspect how package URLs are represented in the OSV Schema and OSV.dev. Determine the expected treatment of embedded CPE strings and document the agreed schema behavior; the issue is done when that support has a defined, reviewed implementation or specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100