ci(supply-chain): SLSA build-provenance + consumer verification doc (#176) - #271
Merged
Conversation
Closes #176. Wires `actions/attest-build-provenance@v2` into the release pack-and-validate job. Every release now cryptographically links each shipped .nupkg / .snupkg / .bom.json to this repo + commit + workflow run (SLSA level 3 via GitHub's Sigstore-signed attestation service). Consumer verifies with: gh attestation verify Wolfgang.TryPattern.<v>.nupkg \ --repo Chris-Wolfgang/Try-Pattern Adds `id-token: write` + `attestations: write` to the job's permissions block (contents: read baseline preserved). No new secret / API-key procurement — the OIDC-based release identity is already established (PR #254 wired NuGet/login@v1 via OIDC). Adds `docs/SUPPLY-CHAIN.md` listing the four independent verification signals now shipped per release: 1. CycloneDX SBOM (already present) 2. Reproducible-build manifest (added in #193) 3. SLSA build-provenance attestation (this PR) 4. SourceLink URL resolution (verified in CI per #181) Deferred (with explicit rationale): NuGet author code-signing via a certificate. Requires paid procurement + KeyVault setup + user account action. Sigstore provenance covers "built by this repo" chain-of-custody; a code-signing cert would additionally cover "signed by named author" — a strictly incremental value for the cost. Documented in SUPPLY-CHAIN.md's "What we do NOT ship" section. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This was referenced Jul 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #176.
Summary
actions/attest-build-provenance@v2torelease.yaml'spack-and-validatejob. SLSA level 3 attestation via GitHub's Sigstore-signed service, over.nupkg+.snupkg+.bom.json. Consumer verification:gh attestation verify <file> --repo Chris-Wolfgang/Try-Pattern.id-token: write+attestations: writepermissions to the job. No new secret required — the OIDC identity is already established.docs/SUPPLY-CHAIN.mdexplaining the four verification signals shipped per release (SBOM, reproducible-build manifest, SLSA attestation, SourceLink) withgh/jq/sha256sumrecipes.What's deferred with rationale
NuGet author code-signing via a certificate. Requires paid procurement (~$X/year) + KeyVault setup + user account action (identity verification). Documented in
SUPPLY-CHAIN.md's "What we do NOT ship" section. Sigstore provenance already covers "built by this repo" chain-of-custody; a cert would additionally cover "signed by named author" — incremental value at real cost.Stacked-PR base
Base =
vNext. Ninth of the 11-PR batch.Protected-file guard
Touches
.github/workflows/release.yaml— protected. Expected admin-bypass at merge.Test plan
gh attestation verify Wolfgang.TryPattern.<v>.nupkg --repo Chris-Wolfgang/Try-Patternsucceeds against the shipped .nupkg