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

release/provenance

Releases attest build provenance

A capability: each stack checks it with its own tools. Implemented for any, node, python, ruby.

Combine: any. One implementation passing is enough: this belongs to the repository, not to each stack, so the stack that does it decides and the others pass with it.

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

Requirement

The release pipeline produces a provenance attestation that ties the artifacts to the source commit and the workflow that built them: the registry’s own provenance where the stack publishes to one (npm, PyPI, RubyGems), otherwise a stack-neutral attestation (GitHub artifact attestations, the SLSA generator, cosign attest, BuildKit, GitLab artifact metadata).

Why

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

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.