Add optional checksum input for binary verification#4
Open
fernandezbaptiste wants to merge 1 commit intomainfrom
Open
Add optional checksum input for binary verification#4fernandezbaptiste wants to merge 1 commit intomainfrom
fernandezbaptiste wants to merge 1 commit intomainfrom
Conversation
Adds a `checksum` input that accepts an expected SHA-256 hash of the downloaded tarball. When provided, the action verifies the hash after download and before extraction, failing the step on mismatch. This is a backwards-compatible, client-side mitigation for the binary integrity concern raised in tesslio/skill-review#11 and tracked in #3. Callers who pin a version can now also pin a checksum without waiting for server-side SHA256SUMS files. Closes #3 (partial — server-side checksums and version resolution improvements remain open) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
checksuminput accepting an expected SHA-256 hash of the downloaded tarballUsage
Context
Addresses the binary integrity concern from tesslio/skill-review#11, tracked upstream in #3.
This is a client-side mitigation — callers who pin a version can now also pin a checksum without waiting for server-side
SHA256SUMSfiles to be published. The remaining items in #3 (server-side checksums, version resolution via Releases API) are separate efforts.Test plan
checksuminput (existing behavior unchanged)checksummatches the downloaded tarballchecksumdoes not match