-
Notifications
You must be signed in to change notification settings - Fork 15
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
Handle SBOM package external references of type "security" different #509
Comments
ctron
added a commit
to ctron/trustify
that referenced
this issue
Jul 5, 2024
The "security" category is intended to find security information about this package, but not describing the package itself. Works around trustification#509
ctron
added a commit
to ctron/trustify
that referenced
this issue
Jul 5, 2024
The "security" category is intended to find security information about this package, but not describing the package itself. Works around trustification#509
Ok, it looks like ignoring all but |
ctron
added a commit
to ctron/trustify
that referenced
this issue
Jul 8, 2024
The "security" category is intended to find security information about this package, but not describing the package itself. Works around trustification#509
ctron
added a commit
to ctron/trustify
that referenced
this issue
Jul 8, 2024
The "security" category is intended to find security information about this package, but not describing the package itself. Works around trustification#509
github-merge-queue bot
pushed a commit
that referenced
this issue
Jul 8, 2024
The "security" category is intended to find security information about this package, but not describing the package itself. Works around #509
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In recent SBOMs (not sure when that was added) the SBOM packages contain additional external CPE references of type "security" (also see: https://spdx.github.io/spdx-spec/v2.3/external-repository-identifiers/#f2-security):
As they don't act as a reference to the packages/components, but are an additional information "where to find security information for". In fact, this is how it looks for a random component out of this SBOM:
This means that we can't simply assign the CPEs to the SBOM packages as reference without a further qualifier.
The text was updated successfully, but these errors were encountered: