Apache-2.0 Single Go binary CycloneDX · SPDX · Syft

git diff for your SBOM.

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.

Install sbomlyze Gate a pull request
$ brew install rezmoss/sbomlyze/sbomlyze
$ sbomlyze nginx-1.28.0-apr.syft.json nginx-1.28.0-dec.syft.json
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 1

Real 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 →

3
SBOM formats parsed and converted
7
Output formats, from text to SARIF
17
Policy rules for CI gating
26
Minimum-element checks across NTIA, CISA, BSI
What's new · v0.8.0 · 2026-11-09
Features
  • site: real-world examples showcase; fix cross-format diff, Syft dependency direction, add deny_downgrades

Full changelog → · See real examples from this release →

The blind spot

Three comparisons. Three different questions.

A component can keep the same name and version while its bytes change. Treating these layers as interchangeable leaves that case unreviewed.

Layer 01
Manifest or lockfile diff
What dependency resolution did the developer request?
Blind spot: does not prove what entered the built artifact.
Layer 02
Ordinary SBOM component diff
What components does each build report?
Blind spot: a same-name, same-version replacement looks unchanged.
Layer 03 · sbomlyze
Integrity & owned-file drift
Did a package's digest, or the files it owns, change without its version changing?
Signals investigation; it does not by itself prove malicious intent.
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 →
Four surfaces, one binary

Review in the terminal, the browser, or the pull request.

Demonstration: sbomlyze blocking a same-version hash change in a test pull request
GitHub Action
Compares the head SBOM against a git, release, artifact, URL, or file baseline. Writes a Job Summary, enforces policy, uploads SARIF, maintains one PR comment.
uses: rezmoss/sbomlyze@v0.8.0
sbomlyze web UI showing components, details, and statistics panes
Web UI explorer
Drag-and-drop up to 500 MB. Dependency tree, deep search across raw JSON, statistics dashboard, and a full filesystem browser with layer filtering.
sbomlyze -web --port 8080
sbomlyze interactive terminal explorer searching and inspecting components
Terminal explorer (TUI)
Keyboard navigation, deep search with /, package-type filters, component detail, and raw JSON with syntax highlighting.
sbomlyze image.json -i
Pipe it anywhere
Read either side of a diff from standard input. Run it right after your generator, with no temporary file.
syft image:tag -o cyclonedx-json \
  | sbomlyze - --compliance

syft image:tag -o cyclonedx-json \
  | sbomlyze baseline.json -

sbomlyze convert cdx.json --to spdx
sbomlyze before.json after.json --format sarif
Where it fits

Many tools generate SBOMs. Few compare them.

Generators make SBOMs and scanners find CVEs. sbomlyze tells you what changed between two SBOMs and whether to trust it.

Capabilitysbomlyzecyclonedx-clisbomqssyft / trivy
SBOM-to-SBOM diffyesbasic——
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 riskyes———
NTIA / CISA / BSI compliance scoringyes—yes—
Format conversion (Syft / CycloneDX / SPDX)yesyes—partial
TUI + Web UI explorersyes———
Policy gate + SARIF / JUnit / Markdown / HTML / Patchyespartialpartialpartial
Capabilities

What it does with two documents.

01
Drift classification
Version, integrity, metadata and owned-file drift are separated, and scanner file entries (go.mod, workflows) are reported apart from packages.
02
Dependency graph diff
Added and removed edges, new transitive reachability, the exact path to each new dependency, and its depth.
03
Depth risk summary
Depth 1 is a choice you made. Depth 3+ is flagged for careful review.
04
Occurrence matching
Each package is matched by identity, version and location, so a package in two lockfiles is never dropped or paired across lockfiles, and results do not depend on input order.
05
Compliance scoring
NTIA, CISA 2025, and BSI TR-03183 minimum elements with per-check pass/fail detail.
06
Duplicate & collision detection
Multiple versions of one package, name mismatches, and same-version hash conflicts.
07
Format conversion
Any input format to CycloneDX 1.5, SPDX 2.3, or Syft JSON, preserving PURLs, hashes, and relationships.
08
Statistics mode
One document in, auto-detected key findings out: ecosystem dominance, licence profile, coverage warnings.
09
Tolerant parsing
Continue on malformed input with structured warnings, or use --strict to fail closed.
10
Ecosystem-correct versions
Upgrade, downgrade and major/minor/patch/revision follow each ecosystem's own rules, checked against dpkg, rpm, apk, pacman, RubyGems and Maven.
11
Owned-file drift
From Syft JSON and SPDX file inventories: a package that keeps its version while files it owns are modified, added or removed.
12
Digest coverage
Reports how many same-version packages could actually be checked, by digest kind (go-h1, SHA-256, cargo-checksum), so a clean result is not mistaken for proof.
Output

One diff, 7 ways to read it.

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.

text json sarif junit markdown html patch
.github/sbom-policy.json
{
  "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
}

Reproduce the blocked pull request.

Three public demo repositories carry five reproducible review scenarios each, with public workflow runs and SARIF evidence.