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.
{{ $r.summary }}
exit status {{ $r.exit }}
Real output: {{ $ex.finding }} 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 drift
Read 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 |
|---|---|---|---|---|
| {{ .cap }} | {{ .a }} | {{ .b }} | {{ .c }} | {{ .d }} |
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.