Miles builds

Is your CI pinned, or does it only look pinned?

In March 2025 someone moved the tags of tj-actions/changed-files to a commit that printed CI secrets into build logs (CVE-2025-30066). Workflows pinned to a commit SHA kept running the old code.

Paste a workflow. Pin Check looks up the commit behind every tag and branch in your uses: lines and gives the file back pinned to full SHAs. It also catches a 40-character "SHA" that is really a branch name.

Runs in your browser. Your workflow never leaves this page; only action names and refs go to api.github.com.
— paste a workflow and check pins

    Run it in your project

    1. Open each file in .github/workflows/, paste it into the box above, and commit the pinned YAML it gives back.
    2. If the page can't reach GitHub, add this helper to your shell and run pin actions/checkout v4 to print the commit SHA. Annotated tags resolve to the commit they point at.
      pin() {
        out=$(git ls-remote "https://github.com/$1" "refs/tags/$2" "refs/tags/$2^{}" "refs/heads/$2")
        sha=$(printf '%s\n' "$out" | awk '/\^\{\}$/{print $1; exit}')
        [ -z "$sha" ] && sha=$(printf '%s\n' "$out" | awk 'NF{print $1; exit}')
        if [ -n "$sha" ]; then echo "$sha"; else echo "not found: $1@$2" >&2; return 1; fi
      }
    3. Keep the pins current with Dependabot. It opens PRs that bump each SHA along with the version comment next to it. Save this as .github/dependabot.yml:
      version: 2
      updates:
        - package-ecosystem: "github-actions"
          directory: "/"
          schedule:
            interval: "weekly"
    4. Block new unpinned refs. In the repo or org settings under Actions > General, turn on "Require actions to be pinned to a full-length commit SHA". Reusable workflows can still use tags under that policy.

    How the 100 most-starred repos pin their actions, from a scan on November 14, 2026.