Pin versions of GitHub Actions to full commit hash#3
Open
Dan P (cuotos) wants to merge 1 commit into
Open
Conversation
Dan P (cuotos)
force-pushed
the
pin-github-actions
branch
from
154d23c to
204b931
Compare
## What? This PR pins versions of GitHub Actions to full commit hash by pinact. In general, this PR doesn't change the behavior of the workflows, so you can merge this safely. ## Why? A while ago, the popular GitHub Action tj-actions/changed-files action was compromised. - https://semgrep.dev/blog/2025/popular-github-action-tj-actionschanged-files-is-compromised/ - https://www.stepsecurity.io/blog/harden-runner-detection-tj-actions-changed-files-action-is-compromised All tags were tampered and they pointed to a revision with malicious code. The issue was solved, but similar issues could happen again. To avoid this kind of issues, we should pin versions of GitHub Actions. This is a common practice of GitHub Actions. https://docs.github.com/en/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions#using-third-party-actions > Pin actions to a full length commit SHA > Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. > Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. > When selecting a SHA, you should verify it is from the action's repository and not a repository fork. ## How was this pull request created? This pull request was created by [pinact](https://github.com/suzuki-shunsuke/pinact) and [multi-gitter](https://github.com/lindell/multi-gitter). ## Deadling We will be turning on a global setting that will ENFORCE that all actions can only use pinned versions, if others are in use, the workflow will fail ## Contact If you have any question, please ask at the Slack channel #tech-platform
Dan P (cuotos)
force-pushed
the
pin-github-actions
branch
from
204b931 to
680b2b5
Compare
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.
What?
This PR pins versions of GitHub Actions to full commit hash by pinact.
In general, this PR doesn't change the behavior of the workflows, so you can merge this safely.
Why?
A while ago, the popular GitHub Action tj-actions/changed-files action was compromised.
All tags were tampered and they pointed to a revision with malicious code.
The issue was solved, but similar issues could happen again.
To avoid this kind of issues, we should pin versions of GitHub Actions.
This is a common practice of GitHub Actions.
https://docs.github.com/en/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions#using-third-party-actions
How was this pull request created?
This pull request was created by pinact and multi-gitter.
Deadling
We will be turning on a global setting that will ENFORCE that all actions can only use pinned versions, if others are in use, the workflow will fail
Contact
If you have any question, please ask at the Slack channel #tech-platform