Repository navigation
feat(install): verify build provenance via gh attestation - #123
Merged
Merged
Conversation
When the GitHub CLI is present and logged in, install.sh now verifies the downloaded tarball against the repo's build provenance attestation and refuses to install on a failed verification. Releases before v0.5.1 predate attestations, so a missing attestation warns instead of failing. Opt out with SKIP_ATTESTATION=1. Document verification in the README.
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.
Closes the loop on the attestations shipped in #122 — the installer now consumes them.
install.shrunsgh attestation verifyon the downloaded tarball whenghis available and logged inSKIP_ATTESTATION=1to bypass)gh attestation verifycommandTested against the live v0.5.0 release: warn-and-install path, skip path, and shellcheck-clean. The fatal path will be exercised for real once v0.5.1 ships with attestations.