77 add consistent creationinformation as a SBOM quality check #97
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
riteshnoronha
force-pushed
the
77-add-consistent-creationinformation-as-a-sbom-quality-check
branch
from
ced0705 to
f1f5713
Compare
surendrapathak
deleted the
77-add-consistent-creationinformation-as-a-sbom-quality-check
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SBOM generators should consistently report their name and version in the SBOM. We have noticed this is not always the case. For consumption, its essential to understand which tool was used to generate this sbom, to understand its quality.
We have added a quality score to help highlight this issue with sbom generators.
A couple of examples from the spdx ecosystem