SLSA
Build track: distributing provenance – SLSA

SLSA BD.3: Immutable attestations in an accepted format

What does BD.3 require?

Once published for an artifact, an attestation should be immutable and never overwritten by a different one for the same artifact; a correction means a new release with new artifacts. The provenance should be in-toto SLSA Build Provenance, or another format both producer and consumer accept that meets the other requirements. Ecosystems that install through an intermediary that transforms source (for example a proxy or bottle service producing source archives) are performing a build and should supply build provenance for what they serve; installation straight from the repository needs no provenance.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

Other controls in Build track: distributing provenance – SLSA

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.