ci: attach an SBOM attestation to published images#707
Merged
Conversation
Each image built by CI and on release now carries an in-toto SBOM attestation alongside the SLSA provenance docker/build-push-action already generates by default (provenance was on but implicit; pin it explicitly so the attestation pair is self-documenting). Both are verifiable via `docker buildx imagetools inspect ghcr.io/rmyndharis/openwa:<tag>`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Add
sbom: true(and pinprovenance: true) to thedocker/build-push-actionstep in bothci.ymlandrelease.yml.Why — and a correction
I previously claimed the published images had no provenance or SBOM. That was half wrong. Inspecting the published image (
docker buildx imagetools inspect ghcr.io/rmyndharis/openwa:0.8.16) shows each platform already carries anattestation-manifestwith predicateTypehttps://slsa.dev/provenance/v1—build-push-action@v7defaultsprovenance: true. So provenance was already present. The real gap is SBOM (sbom:is opt-in and was unset). This adds it.Effect
Every image built by CI (PR/branch) and on release now carries an in-toto SBOM attestation alongside the existing SLSA provenance, verifiable via
docker buildx imagetools inspect.provenance: trueis now explicit rather than relying on the action default.Caveat
The release.yml job runs on tag push only; the ci.yml docker job runs on PRs, so PR CI will exercise
sbom: trueand confirm the SBOM builds cleanly before this merges.