Repository navigation
F194871: Pin GitHub Actions to commit SHAs - #93
Merged
Merged
Conversation
Security watch finding: actions/checkout, actions/setup-node, changesets/action, actions/configure-pages, actions/upload-pages-artifact, and actions/deploy-pages were all referenced by mutable tags across ci.yml, npm-publish.yml, and pages-deploy.yml. Pin each to its resolved commit SHA with a version comment so a compromised tag can't silently change what runs in CI. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BPgFVNDV3puVaHSPjWJr8j
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
mblode
marked this pull request as ready for review
October 5, 2026 22:46
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.
Summary
Security watch finding:
actions/checkout,actions/setup-node,changesets/action,actions/configure-pages,actions/upload-pages-artifact, andactions/deploy-pageswere referenced by mutable tags (@v4,@v1,@v5,@v3) acrossci.yml,npm-publish.yml, andpages-deploy.yml. Pinned each to its resolved commit SHA with a# vXversion comment, so a compromised upstream tag can no longer silently change what runs in CI.actions/checkout@v4→11d5960a326750d5838078e36cf38b85af677262actions/setup-node@v4→49933ea5288caeca8642d1e84afbd3f7d6820020changesets/action@v1→a45c4d594aa4e2c509dc14a9f2b3b67ba3780d0d(latestv1.xrelease,v1.9.0)actions/configure-pages@v5→983d7736d9b0ae728b81ab479565c72886d7745bactions/upload-pages-artifact@v3→56afc609e74202658d3ffba0e8f6dda462b719faactions/deploy-pages@v4→d6db90164ac5ed86f2b6aed7e0febac5b3c0c03eSHAs resolved via
gh api repos/<owner>/<repo>/git/refs/tags/<tag>, peeling annotated tags to their commit object.Test plan
zizmor --offline .github/workflows/reports zerounpinned-usesfindingsnpm run format:checkpassessrc/changes so no build neededLearned:
changesets/action@v1is a moving major tag with no single "v1" commit — pinned to the latestv1.xpatch release (v1.9.0) instead of an arbitrary oldv1.0.0commit, since that matches the version actually in use today.🤖 Generated with Claude Code
https://claude.ai/code/session_01BPgFVNDV3puVaHSPjWJr8j