Conversation
sjn
left a comment
There was a problem hiding this comment.
Some comments about the optionality of the CPAN ID (author) namespace; We may want to consider keeping around tests and comments describing it's use (and recommended alternative when this is the wrong option).
stigtsp
left a comment
There was a problem hiding this comment.
Looks good to me. Thanks for fixing this
|
Anything left to address on this PR? With this change, we will be able to add package URLs to new and historical CVE records for example. |
Updated namespace definition to clarify usage of CPAN author/publisher ID and its preferred qualifiers.
I remember that GH Action converts to MD format, which is why I didn't include it in the PR |
The GH Action is not automatically running atm - we need to make adjustments for security such as pinning the GH Actions |
This PR proposes updates to the CPAN PURL type definition to improve adoption in vulnerability and packaging workflows.
Requiring a
namespaceis too restrictive when only the CPAN distribution name/version is available (e.g., CVE attribution, CSAF, vulnerability management, downstream packaging such as NixOS, etc.).Changes
namespaceis now optional (not deprecated). It may be reserved for future semantics.authorqualifier for the CPAN author/publisher ID (CPANID).distpathqualifier for a repository-relative distribution path (e.g.,authors/id/...).::(module naming).Examples