How these are made
- Real targets, pinned. Each input SBOM came from Syft 1.56.0 on an image pinned by its linux/amd64 digest, a source release, or published jars. The exact command is on every page.
- Inputs never change. The SBOMs are kept in
{{ $sc.inputs_dir }} in the repository, with SHA-256 sums the build verifies. Only sbomlyze changes from one release to the next.
- Output is generated, never edited. After every successful sbomlyze release, the website job runs the released binary on these SBOMs and publishes the output in every format.
- Facts are checked. Each page lists the checks behind its claims, such as 40 upgrades matching
dpkg. If a release breaks one, the site keeps the previous version.
{{ with $sc.archives }}
Earlier releases
{{ range $i, $t := . }}{{ if $i }} · {{ end }}{{ $t }}{{ end }}
{{ end }}