Add cra-sbom-evidence to compliance automation#28
Open
plusultra-ops wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds cra-sbom-evidence to the Compliance automation section as an open-source tool.
It is a small EU Cyber Resilience Act preflight: scores a CycloneDX 1.5/1.6 or SPDX 2.3 SBOM against BSI TR-03183-2 mandatory fields and NTIA Minimum Elements, then emits an Article 14 evidence bundle for the technical file. Deterministic exit codes for CI gating, MIT-licensed Python CLI.
Entry placed alphabetically (c-section) inside Compliance automation. Uses the same Open Source badge as the Probo entry.
Disclosure: I am the author.