Score every SBOM at requirement level
Each upload is validated and scored against BSI TR-03183-2, CISA, NTIA and CRA readiness checks, with each requirement shown as pass, partial or missing.
BSI TR-03183-2 is the most detailed public specification of what a CRA-ready SBOM should contain. SBOMBox scores each SBOM against a BSI TR-03183-2 profile at requirement level, so you can see and fix the gaps before an auditor or customer does.
Each upload is validated and scored against BSI TR-03183-2, CISA, NTIA and CRA readiness checks, with each requirement shown as pass, partial or missing.
The sbombox CLI and CI action generate CycloneDX or SPDX SBOMs in your environment. Only the SBOM and its provenance are uploaded, never source code.
Set a minimum quality score, licence allow and deny lists and required metadata. GitHub and GitLab integrations post the result as a commit status.
Every release's SBOM is stored immutably with its score and findings, so you can show what shipped in a version from two years ago.
Stored SBOMs are matched against OSV, GitHub Security Advisories, NVD and CISA KEV, so a newly exploited component shows up against the releases that contain it.
Mark findings as not affected, affected, fixed or under investigation, with a justification, and keep that decision with the release it applies to.
It is a technical guideline, not law. It is widely used as the reference for what the CRA's SBOM duty will mean in practice.
CycloneDX and SPDX, in JSON or XML (SPDX also as tag-value).
No. The free checker scores a file without an account and does not store it.
A 30-minute walkthrough focused on BSI TR-03183-2. Bring a CycloneDX or SPDX file and we will score it live against BSI TR-03183-2, CISA, NTIA and CRA checks.