Will It Vibe?Third-party action not pinned to a commit SHA
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
A third-party action is pinned to a tag rather than a full commit SHA. Git tags are mutable, so a maintainer (or an attacker who takes over the account) can move the tag to point at new code. This is a heuristic best-practice check.
Why it matters
A tag like @v4 is a mutable pointer. The action maintainer can move it, and if their account is taken over the attacker can move it to malicious code that runs inside your pipeline with your token and secrets. The tj-actions incident in 2025 worked exactly this way. Pinning to a commit SHA removes the moving target.
How to fix it
Replace the tag with the full commit SHA it currently resolves to, keeping the version in a trailing comment (uses: owner/action@<sha> # v4). Automate updates with Dependabot or Renovate, both of which understand SHA-pinned actions. This is a hardening step, so prioritize third-party actions that receive your token or secrets.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo