Generate SBOMs where your code lives
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.
Generating an SBOM is a single CI step. Managing hundreds of them across products and releases, keeping them accurate, and answering 'are we affected?' in minutes is the hard part. That is what SBOMBox is for.
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.
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.
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.
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.
Set a minimum quality score, licence allow and deny lists and required metadata. GitHub and GitLab integrations post the result as a commit status.
3 projects free, then $29 per project per month. No per-seat or per-scan fees.
SBOMBox is offered as a service. If you need a free self-hosted tool, OWASP Dependency-Track is a good option.
No. Generation runs in your environment and only the SBOM is uploaded.
A 30-minute walkthrough focused on SBOM management. Bring a CycloneDX or SPDX file and we will score it live against BSI TR-03183-2, CISA, NTIA and CRA checks.