Skip to content

docs: SLSA provenance is declined for a source-only project, not deferred #774

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DavidCozens merged 1 commit into from
Aug 17, 2026
Merged

docs: SLSA provenance is declined for a source-only project, not deferred #774

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 8 additions & 7 deletions docs/security/sbom.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -313,12 +313,13 @@ whether GitHub, Sigstore, or this project still exist at the time of audit.
For a step-by-step verification guide aimed at downstream integrators, see
[`release-verification.md`](./release-verification.md).

## Deferred

- Signed SLSA provenance attestation. `cosign attest` on top of
`sign-blob` is a natural next step: it produces an attestation
statement that says "this SBOM was produced by this workflow from
these inputs" rather than just "this SBOM was signed by this
workflow."
## Out of scope

- Signed SLSA provenance attestation. An attestation states "this SBOM
was produced by this workflow from these inputs"; the signature above
states only "this SBOM was signed by this workflow". The difference
matters for a binary the consumer cannot inspect. This project is
source-only and the content-tree hash is reproducible from any clone,
so the integrator checks the source itself.
- Binary-artefact signing. The project is source-only; nothing to
sign beyond the SBOM and content-tree hash.
Loading