Attach SLSA provenance bundle as release asset#19
Merged
Conversation
Scorecard's Signed-Releases check inspects only release assets, not GitHub's Attestations API, so the cosign signature was recognised but the provenance was reported as missing: Warn: release artifact v2026.05.21 does not have provenance Capture the actions/attest-build-provenance bundle-path output, copy the bundle to dist/<base>.intoto.jsonl, and upload it as a release asset. The bundle remains in the Attestations API too, so online verification via 'gh attestation verify --repo' still works; the local file enables offline verification with 'gh attestation verify --bundle' and satisfies Scorecard. VERIFICATION.md updated with both online and offline verification flows and the new download pattern.
wnstfy
enabled auto-merge (squash)
May 21, 2026 10:51
Contributor
Trivy misconfiguration findings (HIGH + CRITICAL)Findings below. Fix the issue or add an ignore entry to |
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
1 participant
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.
Summary
Scorecard's Signed-Releases check reads release assets, not GitHub's Attestations API, so it sees our cosign signature but reports provenance as missing:
Fix
Capture the `actions/attest-build-provenance` `bundle-path` output and upload the bundle as a release asset with the `.intoto.jsonl` extension Scorecard recognises. The bundle still lives in the Attestations API as before — this just adds the local file alongside the other release assets.
`VERIFICATION.md` updated to document both online (`--repo`) and offline (`--bundle file`) verification flows.
Test plan