Supply-chain evidence

Omnia publishes component transparency in two forms, for two different readers.

You are	Use
Completing a third-party risk questionnaire	The aggregate SBOM, linked below — no account needed
Auditing one image, or feeding a scanner	The per-image SBOMs, or the attestation on the image itself
Checking a published file against the image	The attestation, read with docker buildx imagetools inspect

Where to get them

Published alongside the Helm chart, on the same public host:

https://charts.altairalabs.ai/sbom/<version>/omnia-<version>.aggregate.spdx.json
https://charts.altairalabs.ai/sbom/<version>/omnia-<version>.sboms.tar.gz

Both are also attached to the GitHub release for anyone with repository access.

What is published

Two documents, both derived from the images’ own attestations rather than a separate scan:

• omnia-<version>.aggregate.spdx.json — every component across all nineteen images, deduplicated by name and version, each recording which images contain it. SPDX 2.3. This is the document to attach to a questionnaire.
• omnia-<version>.sboms.tar.gz — the per-image, per-architecture SPDX documents. linux/amd64 and linux/arm64 differ, because their base-image packages differ, so both are included.

The aggregate is a union of the per-image documents. It carries components, not the relationships between them — if you need the dependency graph, read the per-image document for the image you care about.

Note

The per-image documents are the ones attested to the images. The aggregate is derived from them and is not itself attested, which its creationInfo.comment states.

Attestations

Every image manifest carries an SPDX SBOM and a SLSA provenance attestation. BuildKit generates both during the image build (sbom: true, provenance: true) and attaches them to the image index. The release re-tags the published manifest, so the attestations are the same on the version tag.

Attestation	Read with
SBOM	docker buildx imagetools inspect <image>:<version> --format '{{json .SBOM}}'
Provenance	docker buildx imagetools inspect <image>:<version> --format '{{json .Provenance}}'

The attestations are not signed. No workflow step signs an image or an attestation with cosign.

For the commands that read the attestations, compare them with the published files and rebuild the aggregate, see Audit the supply chain of a release.

What is not published

Omnia does not publish a VEX document, so the SBOM says what is present rather than what is exploitable. The release workflow scans each released image with Trivy (CRITICAL and HIGH findings that have a fix) and retains the findings as build artifacts for 30 days.