{{ define "main" }}
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
{{ with site.Data.gen.showcase }}{{ $ex := index .examples 0 }}{{ $r := index $ex.runs 0 }}
$ {{ $r.command }}
{{ $r.summary }}
exit status {{ $r.exit }}

Real output: {{ $ex.finding }} See the example →

{{ end }}
3
SBOM formats parsed and converted
{{ len site.Data.gen.cli.formats }}
Output formats, from text to SARIF
{{ len site.Data.gen.policy }}
Policy rules for CI gating
{{ $checks := 0 }}{{ range site.Data.gen.compliance }}{{ $checks = add $checks (len .checks) }}{{ end }}
{{ $checks }}
Minimum-element checks across NTIA, CISA, BSI
{{ with site.Data.gen.whatsnew }}
What's new · v{{ .version }}{{ with .date }} · {{ . }}{{ end }}
{{ range .sections }}
{{ .title }}
    {{ range first 6 .items }}
  • {{ . | markdownify }}
  • {{ end }}
{{ if gt (len .items) 6 }}
+ {{ sub (len .items) 6 }} more
{{ end }}
{{ end }}

Full changelog → · See real examples from this release →

{{ end }}
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@{{ (partial "release.html" .).tag }}
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
{{ if site.Params.showComparisonTable }}
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.

{{ range site.Data.home.matrix }} {{ end }}
Capability sbomlyze cyclonedx-cli sbomqs syft / trivy
{{ .cap }} {{ .a }} {{ .b }} {{ .c }} {{ .d }}
{{ end }}
Capabilities

What it does with two documents.

{{ range site.Data.home.features }}
{{ .num }}
{{ .t }}
{{ .d }}
{{ end }}
Output

One diff, {{ len site.Data.gen.cli.formats }} 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.

{{ range site.Data.gen.cli.formats }} {{ .name }} {{ end }}
.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.

{{ end }}