Consider add PURL to advisories
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.2k
- Forks
- 544
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 45
Description
crates.io now list a PURL on each crates page, like pkg:cargo/aho-corasick@1.1.3 for https://crates.io/crates/aho-corasick
It would be awesome to also adopt PURL in the advisories here, especially since CVE.org is fast tracking adopting PURL in the CVE schema.
Tell me how I can help!
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. Start by reviewing the repository's advisory format and existing entries, then compare the Cargo PURL format with the current advisory schema and CVE's PURL direction. Done means the scope is resolved and advisories can consistently represent the appropriate PURL with any needed validation updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100