Software bill of materials · CycloneDX · SPDX
SBOM generator and checker
No software bill of materials yet? This tool turns a lock file into a CycloneDX SBOM as a first version within seconds. Already have an SBOM? Then you see which mandatory fields of BSI TR-03183-2 are missing and what can be matched against vulnerabilities. Everything runs in your browser: the file is neither uploaded nor stored.
What the result does not do
A lock file describes what your package manager resolves – not what ends up in the product. So the result is a starting point, not evidence:
- Anything the package manager does not know is missing: copied-in code, native libraries, the operating system, container contents, firmware.
- The generated file does not meet the mandatory fields of the BSI guideline TR-03183-2. Hash values, file names and the relationships between components, among others, are missing.
- The Cyber Resilience Act requires a software bill of materials in a commonly used, machine-readable format covering at the very least the top-level dependencies. Whether this result is enough for your product is for you to check: it does not certify conformity.
- For customers and authorities, an SBOM from the build is the better choice, for example with Syft or cdxgen.
- ROS 2: from a package.xml, the declared dependencies are read; from a .repos file, the source repositories. There is no package URL (purl) for ROS packages, only GitHub sources get one – so matching against vulnerability databases is hardly possible. A .repos file only contains fixed versions after “vcs export --exact”. For the product you ship, an SBOM from the build is the better basis.
- Checking a finished SBOM only sees what is in the file. It cannot tell whether the details are correct or whether components are missing, nor can it assess the depth of recursion under section 5.1 of the guideline.
Reference: Annex I Part II(1) CRA · BSI TR-03183-2 · This tool is not legal advice.
Supported files
All resolved dependencies, with fixed versions
- package-lock.json
- npm-shrinkwrap.json
- yarn.lock
- pnpm-lock.yaml
- Cargo.lock
- go.mod
- Gemfile.lock
- poetry.lock
- uv.lock
- composer.lock
Direct dependencies only, versions often as ranges
- package.json
- Cargo.toml
- requirements.txt
- pom.xml
- package.xml (ROS 2)
- *.repos (ROS 2, vcstool)
Finished SBOMs to check
- CycloneDX 1.4–1.7 (JSON, XML)
- SPDX 2.2, 2.3 (JSON, Tag-Value)
- SPDX 3.0 (JSON-LD)