Add checksum verification input#16
Open
illera88 wants to merge 1 commit into
Open
Conversation
b97e1e0 to
33c6dd3
Compare
3 tasks
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.
Summary
Supply chain attacks are lately one of the most practical ways to compromise CI: an action can be pinned, but the binary it downloads at runtime can still change upstream. Adding a checksum input lets users pin both the action code and the downloaded release asset, so workflows fail closed if that binary is replaced, corrupted, or unexpectedly modified.
checksuminputWhy
This action downloads a release archive during CI. Pinning the action SHA fixes the action code, but it does not pin the release asset that gets fetched later. A checksum input gives security-sensitive workflows a simple way to make that binary download fail closed if the asset changes unexpectedly.
Testing
npm_config_engine_strict=false task ts:buildnpm_config_engine_strict=false task ts:test