Compare two Software Bills of Materials and see what changed between builds, versions, and releases.
sbomlyze compares package digests and installed-file hashes, not only version strings, wherever the SBOM records them. When a package is swapped or its files change without a version bump, sbomlyze flags it; a version-only diff sees nothing.
Key Findings:
🔄 Scanned index.docker.io/library/nginx changed: sha256:7c46bce526d9abd904d656b4afe3742be3fffd9bc2d361dc4ba68bcbc22ca301 → sha256:3b03dfd827515a07ccf4946000f0bbdd2a4fb6aca7499249fcb6b1f9726823d6
📈 Inventory: +3 files (0.1%), +2 relationships (0.1%)
💻 OS changed: Debian GNU/Linux 12 (bookworm) 12.10 → Debian GNU/Linux 12 (bookworm) 12.12
🔄 40 version upgrades (2 minor, 2 patch, 36 revision) among 150 shared packages
🙈 Integrity drift checked only 1 of 110 same-version packages; the rest carry no comparable digest
📄 960 file entries changed content: 906 in packages that changed version, 0 in same-version packages, 54 not owned by any package: /var/lib/dpkg/info/base-files.md5sums, /var/lib/dpkg/info/bash.md5sums, /var/lib/dpkg/info/ca-certificates.config, /var/lib/dpkg/info/ca-certificates.list, /var/lib/dpkg/info/ca-certificates.md5sums + 49 more
ℹ️ 1 version changes where every hashed owned file is byte-identical: gcc-12-base 12.2.0-14→12.2.0-14+deb12u1 (1 file)
🔄 deb: 149 packages before and after (40 version changes)
exit status 1Real output: nginx:1.28.0 built in April and in December 2025 both run nginx 1.28.0, but 40 Debian packages differ, including the OpenSSL fix for CVE-2025-9230. See the example →
A component can keep the same name and version while its bytes change. Treating these layers as interchangeable leaves that case unreviewed.
component: pkg:golang/example/project@1.4.2
version: 1.4.2 -> 1.4.2
hash: c4e3...aa89 -> 345c...fa36
verdict: integrity driftRead the full analysis →Generators make SBOMs and scanners find CVEs. sbomlyze tells you what changed between two SBOMs and whether to trust it.
| Capability | sbomlyze | cyclonedx-cli | sbomqs | syft / trivy |
|---|---|---|---|---|
| SBOM-to-SBOM diff | yes | basic | — | — |
| Integrity drift (package digest changed, same version) | yes | — | — | — |
| Owned-file tamper detection (files inside a package changed, same version) | yes | — | — | — |
| Ecosystem-correct upgrade/downgrade (deb, rpm, apk, pacman, Maven, Go, PEP 440, …) | yes | — | — | — |
| Dependency-graph diff + transitive depth risk | yes | — | — | — |
| NTIA / CISA / BSI compliance scoring | yes | — | yes | — |
| Format conversion (Syft / CycloneDX / SPDX) | yes | yes | — | partial |
| TUI + Web UI explorers | yes | — | — | — |
| Policy gate + SARIF / JUnit / Markdown / HTML / Patch | yes | partial | partial | partial |
Every format is produced from the same analysis, so the terminal, the code-scanning alert, and the report you email to an auditor never disagree.
{
"deny_integrity_drift": true,
"deny_owned_file_drift": true,
"deny_licenses": ["GPL-3.0", "AGPL-3.0"],
"require_licenses": true,
"max_depth": 3,
"min_overall_compliance": 80
}Three public demo repositories carry five reproducible review scenarios each, with public workflow runs and SARIF evidence.