SBOMs are generated, then forgotten
A file saved somewhere in the build tells nobody whether it is complete, whether suppliers are named or whether it can be trusted.
An SBOM is the ingredients list for your software. Create one with a single command or in your build, check it against the EU Cyber Resilience Act and other rules, and keep signed proof for every release. Your source code never leaves your environment.
Most software is assembled from hundreds of open-source pieces written by other people. An SBOM (software bill of materials) lists every one of them, with its version and who made it.
When a serious security flaw turns up in one of those pieces, the list tells you in minutes whether you are affected. That is why the EU, the US government and large customers now ask for one. SBOMBox creates these lists, checks them against the rules and keeps watching them for new problems.
The EU Cyber Resilience Act, US government buyers and large customers now ask for SBOMs, a plan for fixing security flaws, and proof. Most teams can make the file. Few can show it is complete, up to date and trustworthy.
A file saved somewhere in the build tells nobody whether it is complete, whether suppliers are named or whether it can be trusted.
Germany’s BSI, the US agencies CISA and NTIA, and the EU’s CRA each define a “complete” SBOM in a different way.
A new security flaw can turn up in a release you have already shipped. If attackers are using it, the CRA gives you 24 hours to warn the authorities.
When an auditor or customer asks “prove it”, teams rebuild the story from CI logs and chat threads.
SBOMBox creates SBOMs where your code lives, checks them against published rules, watches them for new security flaws and keeps signed proof for every release.
These are the real SBOMBox screens rendered with sample data. Nothing here is a screenshot, and nothing is sent anywhere.
Every field is checked against BSI, CISA, NTIA and CRA profiles. Each finding names the rule, the affected components and the fix.
Core identity and dependency data conforms to the rules checked. Supplier and support-period metadata remain incomplete.
BSI-SUP-01Supplier name is missingBSI TR-03183-2 v2.137automaticfailCISA-HASH-02Cryptographic hashes are incompleteCISA 202512automaticpartialNTIA-DEP-01Dependency relationship is not declaredNTIA8manualpartialCRA-SUP-03Support period is not documentedCRA readiness1manualfailpkg:npm/%40fastify/cors@9.0.19.0.1MITFastify-pkg:npm/jsonwebtoken@9.0.29.0.2MITAuth01pkg:npm/lodash@4.17.214.17.21MITOpenJS-pkg:npm/postgres@3.4.53.4.5Unlicenseunknown-Every day your SBOMs are matched against newly published security flaws, with the ones attackers are already using (KEV) and the ones most likely to be used next (EPSS) at the top. CRA 24-hour and 72-hour reporting clocks start the moment you confirm an issue.
CVE-2026-31142KEVjsonwebtoken@9.0.29.0.3criticalEdge AgentopenCVE-2026-20881KEVopenssl@3.0.113.0.14criticalDevice FirmwareopenCVE-2026-19204busybox@1.36.01.36.1highDevice Firmwarein-progressCVE-2026-15337fastify@4.26.04.27.0highCheckout APIopenCVE-2025-49812lodash@4.17.204.17.21mediumAdmin ConsoleresolvedSigned provenance, a tamper-evident audit log and shareable reports let customers and assessors verify instead of trust.
mfa.totp.enabledsuccess9f3a…c21eauth.loginsuccess41be…07daauth.login_failedfailedb7c0…92f4token.issuedsuccess02d8…5aa1project.sbom.uploadsuccesse4a1…3b60org.member.role_changedsuccess7c55…d0e8export.personal_datasuccessa9f2…18c7Add an authenticator app in a minute, keep recovery codes safe, and let organisations require MFA for every member.
4820193770314856159274039206817433851609Export what we hold about you, close your account with a grace period, or file a request that is tracked to its 30-day deadline.
Generate at the source, measure against published requirements, and keep evidence linked to the exact release.
Run locally or in CI. Your source stays where it belongs.
Check every field against BSI, CISA, NTIA and CRA profiles.
Track vulnerability and compliance drift across releases.
Share signed, verifiable evidence with customers and auditors.
SBOMBox keeps each release's SBOM, compliance results, vulnerability decisions and support dates together, without adding another scanner to your pipeline.
name: Generate signed SBOM
uses: sbombox/action@v1
with:
project: checkout-api
attest: trueWhether the question comes from the CRA, NIS2, the FDA, a PCI assessor or a customer questionnaire, and whether you are a startup or a global enterprise, start from the guide written for you.
A Software Bill of Materials (SBOM) is an ingredients list for software. It is a machine-readable file that names every component, library and version inside a product, so you can tell at once whether a newly found security flaw affects you. CycloneDX and SPDX are the two standard formats.
Yes, if you sell software or connected devices in the EU. The CRA requires a machine-readable SBOM that lists at least your direct dependencies. The SBOM rule applies from 11 December 2027. Reporting exploited vulnerabilities has been required since 11 September 2026.
Install the SBOMBox CLI with one command and run it in your repository, or add the SBOMBox GitHub Action to generate a signed SBOM on every release. GitLab CI is also supported.
No. SBOMs are generated locally or in your CI. SBOMBox receives only the finished SBOM, never your source code.
Drop a CycloneDX or SPDX file into the free checker on this page. In seconds you get a quality score across 8 categories, showing what passes and what to fix. Nothing is stored.
CycloneDX 1.4 to 1.7 and SPDX 2.2 to 3.0, in JSON or XML.
SBOMBox checks your SBOMs for new vulnerabilities, including ones attackers are already exploiting. If one affects you, log it as a CRA incident. Its reporting deadlines stay next to the affected release.
Publish selected SBOMs and compliance results to your SBOMBox Trust Center and share them privately with customers, instead of emailing files.
Three projects are free. After that it is $29 per project per month, with no per-seat or per-scan fees.