Real output · sbomlyze v0.8.0

Examples

Eight real cases: images, source trees and jars scanned once, then diffed by the released sbomlyze binary after every release. Commands, raw output in every format, and the input SBOMs to download.

Example 1
Same tag, different image
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.
containerdeb
Example 2
Go module re-tagged after release
The same go-containerregistry v0.20.4, two different checksums: the maintainer moved the tag after Go's checksum database had recorded it.
gosource
Example 3
Same version, files changed inside
scanelf 1.3.7-r2 has the same version in Alpine 3.19.9 and 3.20.10, but its binary /usr/bin/scanelf changed.
containerapk
Example 4
Downgrades hiding in a minor bump
Upgrading node:20.11.1-alpine to 20.18.0-alpine put older major versions of ansi-regex and strip-ansi at the same paths inside npm.
containernpmapk
Example 5
An app upgrade that swapped the runtime
ZooKeeper 3.8.3 → 3.9.2 also moved the Java runtime from 11 to 17 and added bundled native BoringSSL builds for Linux, macOS and Windows.
containermavendeb
Example 6
Transitive churn in a point release
ripgrep 14.0.3 → 14.1.1 swapped winapi for the windows-sys crate family: 11 crates added, 9 removed, new dependencies up to five levels deep.
rustsource
Example 7
One image, three formats
The same nginx image as Syft JSON, CycloneDX and SPDX diffs to nothing in every pairing, while their compliance scores differ: NTIA 57, 71 and 71.
containerdeb
Example 8
A license change in a minor release
Akka 2.6.20 → 2.7.0 changed its license from Apache-2.0 to the Business Source License 1.1, and deny_licenses catches it on the upgrade.
javamaven

How these are made