GitHub Actions now supports native workflow dependency lockfiles at .github/workflows/actions.lock, generated by the gh actions-lock CLI extension.
However, githubactions:S7637 still reports:
Use full commit SHA hash for this dependency.
This produces false-positive findings for tag-based action references whose exact commits are pinned and enforced through the workflow’s lockfile.
Official GitHub documentation:
GitHub explicitly states:
For repositories that adopt a lockfile, SHA pinning within workflow files is no longer necessary.
The documentation also explains that lockfiles cover transitive action dependencies, verify source repository identity, and satisfy GitHub’s “Require actions to be pinned to a full-length commit SHA” policy for onboarded workflows.
Expected behavior
S7637 should recognize action references covered by an onboarded workflow’s valid actions.lock, rather than requiring an additional inline commit SHA.
It should continue reporting unpinned references when:
- The workflow is not onboarded to the lockfile.
- The action reference is not covered by the lockfile.
- The reference is a reusable workflow call (
jobs.<job_id>.uses), which GitHub explicitly excludes from lockfile pinning.
Could you confirm whether native lockfile support is planned or already tracked? If not, please consider this a false-positive report and request to update S7637.
I investigated contributing a fix through SonarSource/sonar-iac, but could not find the GitHub Actions check implementation in the public repository. Is there a public contribution path for this change?