security: Update version pins to use SHAs instead#30
Merged
DariuszPorowski merged 1 commit intoraven-actions:mainfrom May 29, 2025
Merged
security: Update version pins to use SHAs instead#30DariuszPorowski merged 1 commit intoraven-actions:mainfrom
DariuszPorowski merged 1 commit intoraven-actions:mainfrom
Conversation
Spurred by the tj-actions supply chain attack, it is a good idea to harden actions by pinning to SHAs of custom github action commits instead of using their tags. See https://www.stepsecurity.io/blog/harden-runner-detection-tj-actions-changed-files-action-is-compromised for details of the attack.
Contributor
Author
|
@DariuszPorowski BTW in case you're interested since you manage so many of these -- I made a simple go executable to automatically update Github Action workflow files to use SHAs instead of tags/branches. It pulls the SHAs straight from Github itself: https://github.com/Skipants/update-action-pins |
Collaborator
|
@Skipants this is great! will take a look, thanks! :) |
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
2 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.
💌 Description
Hello! I love the work you did on this action and want to include it in my company's CI. It's saving me a ton of time.
I have made an update on my fork to to harden the security of this action and to help mitigate some upstream supply chain risks.
I bet you've heard of the tj-actions supply chain attack but for posterity there's more info here: https://www.stepsecurity.io/blog/harden-runner-detection-tj-actions-changed-files-action-is-compromised
That attack is the main reason for me making this change here and to some of our other upstream github actions.
Let me know if there's anything that needs changing.
🏗️ Type of change
✅ Checklist
Code of Conductdocument.Contributingguide.