48 of the 100 most-starred repos pin every third-party GitHub Action. 26 pin none.
A scan of every uses: line on the default branch of the 100 most-starred GitHub repos that use Actions, taken November 14, 2026.
On November 14 I scanned the workflows of the 100 most-starred GitHub repos that use Actions. I read every uses: line on each default branch and sorted the references into pinned and not pinned.
- 48 pin all
- 12 pin some
- 26 pin none
These are some of the most watched codebases on GitHub. In 26 of them, every build runs whatever commit a third party's tag points to that day.
Why a tag can move and a SHA can't
When a workflow says uses: some-org/some-action@v4, v4 is a git tag. A tag is a name, and whoever controls the action's repo can delete it and create it again on another commit. Plenty of projects do this on purpose, moving v4 up to the latest v4.x so users get fixes without touching anything. Your workflow file stays the same and the code it runs changes.
A commit SHA is a hash of the commit's contents. @ followed by 40 hex characters points to exactly one commit. New code gets a new hash, and the old hash keeps pointing at the old code. Nobody can make an existing SHA mean something else.
In March 2025 that difference mattered. Someone took over tj-actions/changed-files, an action used in more than 23000 repos, and moved its version tags to a malicious commit (CVE-2025-30066). The new code dumped CI secrets into build logs, and on public repos anyone can read those. Workflows that referenced a tag ran it on their next build. Workflows pinned to an older SHA kept running the old code, unless someone bumped the pin to the bad commit during the attack window.
Pinning won't tell you whether an action is safe. It means the code you run changes only when you edit the pin.
What the unpinned refs look like
Counted by reference instead of by repo: 2008 third-party refs across 231 distinct actions, and 1443 of them pinned to a SHA, about 72 percent. A few huge repos with hundreds of workflows swing that number, so I'd trust the repo count more.
The actions that show up most often without a SHA:
| Action | Unpinned refs |
|---|---|
pnpm/action-setup | 108 |
astral-sh/setup-uv | 89 |
dtolnay/rust-toolchain | 39 |
docker/login-action | 38 |
docker/build-push-action | 30 |
docker/setup-buildx-action | 26 |
oven-sh/setup-bun | 22 |
nick-fields/retry | 21 |
Nearly all of these are written the way each action's README shows, with a version tag like @v4. dtolnay/rust-toolchain uses branch names like @stable by design, because the branch picks the Rust version. Copying the README is the normal thing to do, and none of these projects did anything wrong. The ref still ends up on a name the action's owner can move.
This page names actions, never the scanned repos. Most of these refs were copied straight from an action's README, which is what anyone would do.
What this scan doesn't cover
- One snapshot, taken November 14. Workflows change every week.
- Default branch only. Release branches and forks weren't read.
- Composite actions kept inside a repo's own actions folder weren't opened. If one of them calls a third-party action, I missed it.
- YAML aliases weren't resolved, so a handful of
uses:lines with no@aren't counted either way. - Actions from GitHub and from the scanned repo's own organization don't count as third-party. Calls to reusable workflows were dropped.
A first pass I posted on November 14 said 42 pin everything and 27 pin none. That one counted a repo's own org actions and reusable workflows as third-party. The numbers above leave both out.
How to check your own repo
From the root of your repo:
grep -rn 'uses:' .github | grep '@' | grep -vE '@[0-9a-f]{40}'
That prints every uses: line whose ref isn't a full 40-character SHA. GitHub's own actions show up too, so skip those if third-party code is what you're after. Pin whatever touches secrets first: anything that logs in, publishes or deploys.
To pin one, find the commit behind the tag on the action's releases page, swap the tag for the full SHA, and keep the version as a comment after it, like @<sha> # v4. Dependabot bumps SHA pins and updates that version comment for you. Renovate bumps the SHA to match the tag you specified. With either one, pinning doesn't leave you stuck on an old release.
If you'd rather paste than grep, Pin Check takes a workflow and gives the file back pinned.