We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Current usage of 3rd-party actions in .github/workflows uses broad versions instead of specific commit hashes, example:
.github/workflows
socialify/.github/workflows/build.yml
Line 22 in 082c960
Though unlikely, this exposes the project to supply chain attacks in case latest major version is compromised at the time of workflow run.
Pinning all 3rd party actions to commit hash corresponding to latest stable release, example:
- name: Setup pnpm uses: pnpm/action-setup@fe02b34f77f8bc703788d5817da081398fad5dd2 # Pinned to commit hash of release v4.0.0 on 05/07/24.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Vulnerability
Current usage of 3rd-party actions in
.github/workflows
uses broad versions instead of specific commit hashes, example:socialify/.github/workflows/build.yml
Line 22 in 082c960
Though unlikely, this exposes the project to supply chain attacks in case latest major version is compromised at the time of workflow run.
Solution
Pinning all 3rd party actions to commit hash corresponding to latest stable release, example:
The text was updated successfully, but these errors were encountered: