-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve SBOM Product Management #2685
Comments
terriko
added
the
gsoc
Tasks related to our participation in Google Summer of Code
label
Feb 14, 2023
This may be of relevance. |
Darn, I was hoping that they were proposing infrastructure fixes. But better namespaces are good too. |
This was referenced Mar 9, 2023
This didn't wind up worked explicitly into any gsoc applications this year. We already have Name support so I'm going to open two separate issues and initially invite the hackathon folk to work on them this week:
|
terriko
removed
the
gsoc
Tasks related to our participation in Google Summer of Code
label
Apr 25, 2023
This was referenced Apr 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SBOMs can specify a product in a number of different ways. For example, a SBOM can include a product as a Name, a CPE or a PURL (and possibly all three!). Whilst the quality of SBOMs is variable (and in some cases inconsistent) extending the mechanisms beyond a name should increase the reliability of the SBOM scanning and reduce false reports as CPE and/or PURL can include vendor information as well.
If a PURL record is used, there is also the possibility of interogating an ecosystem to get more accurante product information.
This task will also require changes to the SBOM parsing routines to use external libraries e.g. SPDX Python Tools
Possibly add to GSOC task?
The text was updated successfully, but these errors were encountered: