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.
A container image carries operating-system packages from its base image as well as your application dependencies, and it changes every time the base image is rebuilt. SBOMBox stores an SBOM per image release and keeps matching it against new vulnerabilities.
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.
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.
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.
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.
Yes. Any CycloneDX or SPDX SBOM can be uploaded and scored.
No. Generation happens in your CI. SBOMBox receives the SBOM, not the image.
Generate from the final image so build-only tools are not listed.
A 30-minute walkthrough focused on Container images. Bring a CycloneDX or SPDX file and we will score it live against BSI TR-03183-2, CISA, NTIA and CRA checks.