Repository navigation
SEC-2: Dependency pinning by hash - #30
Open
avx-manpreetsingh wants to merge 1 commit into
Open
avx-manpreetsingh wants to merge 1 commit into
avx-manpreetsingh wants to merge 1 commit into
Conversation
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
This PR pins all GitHub Actions in our workflows to a full commit SHA instead of a version tag (part of SEC-2).
Why
A tag like
actions/checkout@v4can be moved to different code anytime by the action owner or by an attacker. A commit SHA cannot be changed, so only the exact code we have checked will run in our pipeline. This protects us from supply chain attacks.What changed
Only the action references are changed. Workflow logic is same as before.
How to test
uses:line has a full SHA with the version comment.Kindly review and approve. Thanks!