fleetlint Policy for a fleet of repositories
v0.6
Getting started

release/provenance/image

Releases attest build provenance

Implements release/provenance for the image artifact: it runs when the release publishes one (see artifacts).

Severitywarning
Tiers1
Artifactimage
Scoperoot
Kindoutcome
Sourcelibrary v0.3.1
Selected byfleetlint-recommended@v0.3.1

Requirement

Provenance is attached to the image digest: BuildKit (docker/build-push-action v4 or newer with provenance not set to false, docker buildx build --provenance), cosign attest --type slsaprovenance, actions/attest-build-provenance with subject-digest and push-to-registry, or the SLSA container generator.

Why

Provenance ties the artifact to the exact source and workflow that built it, which a signature alone does not.

Capability applies when

release.exists || repo.artifacts.size() > 0

Fix

Keep docker/build-push-action v4 or newer and do not set provenance: false; or run cosign attest --yes --type slsaprovenance --predicate provenance.json <image>@<digest>.

Agent instruction: Remove provenance: false from the docker/build-push-action step, or add actions/attest-build-provenance with subject-name, subject-digest from the build step and push-to-registry: true.

See: https://fleetlint.org/baseline/#releases, https://slsa.dev/spec/v1.0/provenance, https://docs.docker.com/build/metadata/attestations/slsa-provenance/


Generated by fleetlint docs from catalog v0.3.1.