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

release/provenance/any

Releases attest build provenance

The stack-neutral implementation of release/provenance: it checks stacks without an implementation of their own and repositories where no stack is detected, and its satisfiers count for every stack.

Severitywarning
Tiers1
Stacksany
Scoperoot
Kindoutcome
Sourcelibrary v0.2.0
Selected byfleetlint-recommended@v0.2.0

Requirement

The release pipeline attests provenance with actions/attest-build-provenance, the SLSA generator, cosign attest or cosign attest-blob, docker/build-push-action v4 or newer (provenance is on unless provenance: false), or GitLab’s artifact provenance (RUNNER_GENERATE_ARTIFACTS_METADATA: "true").

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 && tagged_workflows().size() > 0

Fix

Add actions/attest-build-provenance (GitHub), RUNNER_GENERATE_ARTIFACTS_METADATA: "true" (GitLab) or cosign attest-blob --predicate (Gitea) to the release pipeline; a package published to npm, PyPI or RubyGems gets it from trusted publishing.

Agent instruction: Add a step uses: actions/attest-build-provenance with subject-path covering the release artifacts; grant id-token: write and attestations: write to that job only. On GitLab set the variable RUNNER_GENERATE_ARTIFACTS_METADATA to “true” on the release job. On Gitea write a SLSA v1 predicate and run cosign attest-blob --type slsaprovenance1.

See: https://fleetlint.org/baseline/#releases, https://slsa.dev/spec/v1.0/provenance


Generated by fleetlint docs from catalog v0.2.0.