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.
Article 21 of NIS2 requires essential and important entities to manage supply-chain security and vulnerability handling. If you sell software to them, their questionnaires and contracts land on your desk. SBOMBox turns the answer into evidence you can share.
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.
Publish your security practices and compliance attestations in a Trust Center, and share results privately with customers instead of emailing files.
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.
Not by name. Article 21 requires supply-chain security and vulnerability handling, and an SBOM is the practical evidence for both.
Possibly directly, if you are a medium or large entity in a listed sector such as ICT service management or digital providers. Otherwise you are usually affected through your customers' supplier requirements.
Then the Cyber Resilience Act likely applies to you directly, and it does require an SBOM.
A 30-minute walkthrough focused on NIS2 supply chain. Bring a CycloneDX or SPDX file and we will score it live against BSI TR-03183-2, CISA, NTIA and CRA checks.