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

release/provenance/maven

Releases attest build provenance

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

Severitywarning
Tiers1
Artifactmaven
Scoperoot
Kindoutcome
Sourcelibrary v0.4.0
Selected byfleetlint-recommended@v0.4.0

Requirement

The workflow that publishes the Maven artifacts attests its provenance: actions/attest-build-provenance (the subject path covering the files), the SLSA generator, cosign attest-blob, or GitLab’s artifact provenance (RUNNER_GENERATE_ARTIFACTS_METADATA: "true"). Maven Central accepts no attestations yet, so the attestation is published with the forge release or in the sigstore log.

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

Add actions/attest-build-provenance with subject-path covering the Maven artifacts (GitHub), RUNNER_GENERATE_ARTIFACTS_METADATA: "true" (GitLab) or cosign attest-blob --predicate (Gitea) to the release workflow.

Agent instruction: Add a step uses: actions/attest-build-provenance with subject-path covering the release files (or subject-name and subject-digest for an image, with push-to-registry: true); 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.

Sources


Generated by fleetlint docs from catalog v0.4.0.