Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Turn on renovate best practice preset #77

Merged
merged 1 commit into from
Oct 8, 2024

Conversation

gberche-orange
Copy link
Contributor

https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions suggests

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.

Renovate best practice automates this process, see https://docs.renovatebot.com/upgrade-best-practices/#extends-helperspingithubactiondigests

We recommend pinning all Actions. That's why the helpers:pinGitHubActionDigests preset pins all GitHub Actions.

For an in-depth explanation why you should pin your Github Actions, read the Palo Alto Networks blogpost about the GitHub Actions worm.

@jaxxstorm jaxxstorm merged commit 62cace1 into jaxxstorm:master Oct 8, 2024
@gberche-orange
Copy link
Contributor Author

thanks @jaxxstorm !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants