SBOM tools by language in 2026: what each package manager can do
By SBOMBox SBOM experts · · 3 min readShort answer: in November 2026, npm, pnpm and uv can write an SBOM with a built-in command, and Spring Boot can package one inside your application. Cargo has an unstable precursor on nightly. Go, Maven, Gradle, .NET, Bundler and Composer still need a CycloneDX plugin or a scanner such as syft or cdxgen.
Why built-in support matters
A package manager knows exactly what it resolved and installed. An external scanner has to reconstruct that from manifests and lockfiles, and sometimes guesses. Built-in commands also mean one less tool to install, pin and trust on every CI runner. The trade-off is that built-in commands are young: they leave out fields that regulators ask for, as our test of npm, pnpm and uv showed.
The state of each ecosystem
| Ecosystem | Built in? | Command or feature | Otherwise use |
|---|---|---|---|
| npm | Yes, npm 9.5+ | npm sbom | - |
| pnpm | Yes, pnpm 11+ | pnpm sbom | - |
| Yarn | No | - | cdxgen, syft |
| Python (uv) | Preview, uv 0.9.11+ | uv export --format cyclonedx1.5 | cyclonedx-py |
| Python (pip, Poetry) | No | PEP 770 lets wheels carry SBOMs in .dist-info/sboms/ | cyclonedx-py |
| Rust | Nightly only | cargo -Zsbom precursor files; stabilizing is a 2026 project goal | cargo-cyclonedx, cargo-auditable |
| Go | No | go version -m -json prints a binary's build info (Go 1.25+) | cyclonedx-gomod, syft |
| Java | Spring Boot 3.3+ | SBOM packaged in the jar, served at /actuator/sbom if you expose it | CycloneDX Maven and Gradle plugins, cdxgen |
| .NET | No | - | CycloneDX .NET tool, Microsoft sbom-tool, syft |
| Ruby | No | On the RubyGems roadmap | bundler-sbom plugin, syft |
| PHP | No | - | CycloneDX Composer plugin, syft |
| Container images | Yes, BuildKit | docker buildx build --sbom=true attaches an SPDX attestation | syft on the image |
What this means for a team with many languages
You will run several generators for years, because the ecosystems are moving at different speeds. Two habits keep that manageable. First, commit a lockfile in every repository: every tool above is more accurate with one, and most are wrong without one. Second, put one entry point in front of all of them, so a repository calls sbom.sh or sbombox generate and never a specific tool. When an ecosystem gains a built-in command, you change the entry point once.
The unify SBOMs across stacks guide has a tested script for that entry point and an eight-rule standard every generator's output should meet. Per-language commands are in the language guides: Python, Java, Go, Rust, .NET, Ruby, PHP and containers.
What to watch in 2027
- Cargo stabilizing its SBOM precursor, which would let cargo-cyclonedx and cargo-auditable read Cargo's own resolution.
- PEP 770 adoption by build backends, so Python wheels carry the SBOM of anything they bundle.
- uv moving its CycloneDX export out of preview.
- RubyGems.org publishing SBOMs alongside gems.
Frequently asked questions
Is syft or cdxgen still worth installing?
Yes, for languages without a built-in command, for multi-language repositories and for container images. See Syft vs Trivy vs cdxgen.
Should I trust a package manager's SBOM more than a scanner's?
For which packages and versions are included, usually yes. For metadata such as licenses, hashes and suppliers, check the output: built-in commands often leave them out.