Outdated major version of a core GitHub action
Part of Testing & CI, which counts for 10% 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 core actions/* step is pinned to a major that has been superseded. Older majors run on retired Node runtimes (Node 12/16) and, for the artifact actions, on a backend GitHub is shutting down.
Why it matters
A core actions/* step pinned to an older major (for example actions/checkout@v3) runs on a Node runtime that GitHub has deprecated (Node 12 or 16), and for the artifact actions on a backend that is being shut down. Deprecated majors emit warnings now and stop working later, breaking the workflow. Newer majors also carry security and bug fixes.
How to fix it
Bump each flagged action to its current major and read the release notes, since majors sometimes change inputs or outputs (for example upload-artifact v4 changed how artifacts merge). Pin the new version to a commit SHA with the version in a comment for supply-chain safety while you are editing the line anyway.
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