Repository navigation
No-op - Pinning github actions to commit SHAs - #52
Merged
Merged
Conversation
lopert
approved these changes
Apr 27, 2026
saga-dasgupta
approved these changes
Apr 27, 2026
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
3 participants
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.
Why?
By using
some-org/some-action@v3you are trusting a mutable tag. If the upstream repo is compromised, a force-pushedv3ships malicious code into your workflow on the next run — see tj-actions/changed-files (March 2025) for recent real-world cases that leaked secrets across thousands of downstream workflows.Pinning to a full 40-char SHA (
uses: tj-actions/changed-files@<sha> # v45.0.3) makes the reference immutable and helps to mitigate this type of supply chain attacks.cc @saga-dasgupta @lopert for review.