ci: pin wasm-pack with SHA256 verification#5
Merged
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Replace `curl | sh` install with a pinned GitHub release tarball and in-workflow SHA256 check. Closes a CRITICAL supply-chain finding from the March 2026 audit (#4). Co-Authored-By: Claude Opus 4.7 (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
curl https://rustwasm.github.io/wasm-pack/installer/init.sh | shin.github/workflows/deploy.ymlwith a pinned GitHub release tarball.wasm-pack-v0.13.1-x86_64-unknown-linux-musl.tar.gzis hardcoded in the workflow (c539d91ccab2591a7e975bcf82c82e1911b03335c80aa83d67ad25ed2ad06539) and verified viasha256sum -c -before extraction.Why this and not
cargo install?cargo installdoes verify the crate tarball against the SHA256 in the crates.io git index, but that index is the trust root — there's no flag to pass cargo your own out-of-band SHA for the top-level crate, and--lockedonly pins transitive versions. Anchoring the hash in our own repo gives an independent, auditable check that survives a registry compromise. (Issue body has the full reasoning.)Test plan
wasm-pack --versionstep shows0.13.1in the job logcurl | sh/wget | shin any workflow🤖 Generated with Claude Code