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.
Section 524B of the FD&C Act requires manufacturers of cyber devices to provide an SBOM and to monitor and address post-market vulnerabilities. SBOMBox gives you a complete, scored SBOM for each release and keeps watching it after the device ships.
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.
Every SBOM is scored against NTIA and CISA minimum elements, which FDA guidance references, plus BSI TR-03183-2.
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.
Export SBOMs in CycloneDX or SPDX for submissions and customer requests.
No. SBOMs are scored against NTIA, CISA, BSI TR-03183-2 and CRA readiness checks. FDA-specific content such as support level and end-of-support dates remains your responsibility.
Cyber devices: devices that include software, can connect to the internet and could be vulnerable to cybersecurity threats.
Yes. Source code never leaves your environment, and SBOMs are only shared when you choose to.
A 30-minute walkthrough focused on Medical devices (FDA). Bring a CycloneDX or SPDX file and we will score it live against BSI TR-03183-2, CISA, NTIA and CRA checks.