You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remediates GitHub Workflow Dependency Locking (public preview, no changelog entry), which rejects runs at startup_failure — zero jobs, no logs, nothing in REST or GraphQL. Full analysis: hyperpolymath/standards#657.
Proven on hyperpolymath/anamnesis: 6 of 6 workflows dead → 0 startup_failure, 13 running.
Five steps, in order — each blocks the next
1. Unbreak the workflow YAML. Any permissions: carrying a scalar with an indented mapping under it:
permissions: read-allactions: read # <- mapping under a scalar. Unparseable.
This reaches past the one file: gh actions-lock refuses to run when any workflow in the repo fails to parse, so the repo can never acquire a lockfile and can never self-heal.
2. Repin standards reusables off commits with no actions.lock. The rejection requires the callee to be covered at the pinned SHA — unsatisfiable at a pre-lockfile commit.
3. Generate the lockfile with gh actions-lock.
4. Hand-add the reusable-caller entries the tool omits, as '<path>': [].
⚠️ Measured across 218 repos: P(startup_failure | has lockfile) = 91.7% vs 15.8% without — because every workflow a lockfile omits is rejected. A partial lock is worse than none. Running gh actions-lock and stopping there is how this outage spread.
5. Restore SPDX-License-Identifier to line 1, which the tool displaces with its own banner and which the workflow-security linter greps via head -1.
Verified before this PR was opened
0 unparseable workflows · lockfile covers every workflow, no omissions · SPDX on line 1 in every file. The script refuses to push if any of the three fails.
Remediates GitHub Workflow Dependency Locking (public preview), which
rejects runs at startup_failure with zero jobs and no logs. See
hyperpolymath/standards#657.
Five steps, in order, because each blocks the next:
1. Unbroke any workflow whose `permissions:` carried a scalar with an
indented mapping under it - blind-permissions-insertion damage. This
matters beyond the one file: gh actions-lock refuses to run when ANY
workflow in the repo fails to parse, so the repo could never acquire a
lockfile and could never self-heal.
2. Repinned hyperpolymath/standards reusables off commits that have no
actions.lock. The rejection requires the CALLEE to be covered at the
pinned SHA, which is unsatisfiable at a pre-lockfile commit.
3. Generated the lockfile with gh actions-lock.
4. Hand-added the reusable-workflow caller entries the tool omits, as
'<path>': []. Measured across 218 repos: P(startup_failure | has
lockfile) = 91.7% vs 15.8% without, because every workflow a lockfile
OMITS is rejected. A PARTIAL lock is worse than none - running
gh actions-lock and stopping there is how this outage spread.
5. Restored SPDX-License-Identifier to line 1, which the tool displaces
with its own banner and which the workflow-security linter greps with
head -1.
Verified before push: 0 unparseable workflows, lockfile covers every
workflow with no omissions, SPDX on line 1 in every file.
Proven on hyperpolymath/anamnesis: 6 of 6 workflows dead -> 0
startup_failure, 13 running.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A rabbit checks each workflow line,
Tags hop neatly into place.
SHA pins rest beneath the moon,
New actions run their steady race.
“gh actions-lock,” whispers the hare,
While YAML dreams in careful rows.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR remediates CI workflow failures and standardizes file structures, including the addition of a managed banner and SPDX license identifiers. However, the current implementation is not up to standards due to security risks.
A systemic issue was identified where actions are pinned to mutable tags (e.g., @v4.0.1) instead of full commit SHAs, exposing the workflows to supply chain vulnerabilities. Furthermore, in the scorecard workflow, job-level permission blocks override workflow-level settings, which will prevent the job from receiving the necessary 'actions: read' permission. These issues must be addressed to ensure the stability and security of the CI/CD pipeline.
About this PR
Several workflows have been updated to use mutable tags for third-party actions. To comply with security best practices and protect against supply chain attacks, all third-party actions should be pinned to a full-length commit SHA, with the version tag included only as a comment.
Test suggestions
Verify all modified workflows have the SPDX-License-Identifier on line 1 for security linter compatibility.
Verify 'actions: read' permission is added to workflows calling reusables to support dependency locking metadata.
Confirm every workflow contains the standard management banner.
Verify that versions for standard actions (like checkout, upload-artifact) are synchronized across files.
The reason will be displayed to describe this comment to others. Learn more.
🔴 HIGH RISK
The setup-beam action should be pinned to a full commit SHA for security. Tags are mutable and can be pointed to different code over time.
Try running the following prompt in your IDE agent:
Find the full commit SHA for 'erlef/setup-beam' at version 'v1.24.1' and update line 128 in '.github/workflows/static-analysis-gate.yml' to use the SHA, adding '# v1.24.1' as a comment.
The reason will be displayed to describe this comment to others. Learn more.
🔴 HIGH RISK
Ensure this action is pinned to an immutable commit SHA. This prevents external changes to the action from executing in your privileged workflow.
Try running the following prompt in your IDE agent:
Find the full commit SHA for 'dependabot/fetch-metadata' at version 'v3.1.0' and update line 58 in '.github/workflows/dependabot-automerge.yml' to use that SHA, keeping 'v3.1.0' as a trailing comment.
The reason will be displayed to describe this comment to others. Learn more.
🔴 HIGH RISK
Use a full-length commit SHA for third-party actions to ensure the build remains immutable.
Try running the following prompt in your IDE agent:
Find the full commit SHA for 'dawidd6/action-send-mail' at version 'v3.12.0' and update line 19 in '.github/workflows/push-email-notify.yml' to use the SHA, adding '# v3.12.0' as a comment.
The reason will be displayed to describe this comment to others. Learn more.
🔴 HIGH RISK
Pinning to a tag instead of a commit SHA allows the underlying code to change without notice. Use the immutable commit SHA instead.
Try running the following prompt in your IDE agent:
Find the full commit SHA for 'peter-evans/repository-dispatch' at version 'v4.0.1' and update line 33 in '.github/workflows/instant-sync.yml' to use the SHA, adding '# v4.0.1' as a comment.
The reason will be displayed to describe this comment to others. Learn more.
🟡 MEDIUM RISK
The job-level permissions block (lines 23-26) overrides the workflow-level permissions. To ensure the 'scorecard' job has 'actions: read' permission, it must be added directly to the job-level permissions block.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![codacy-production[bot]](https://avatars.githubusercontent.com/in/56611?s=60&v=4){kind=small}
Remediates GitHub Workflow Dependency Locking (public preview, no changelog entry), which rejects runs at
startup_failure— zero jobs, no logs, nothing in REST or GraphQL. Full analysis:hyperpolymath/standards#657.Proven on
hyperpolymath/anamnesis: 6 of 6 workflows dead → 0startup_failure, 13 running.Five steps, in order — each blocks the next
1. Unbreak the workflow YAML. Any
permissions:carrying a scalar with an indented mapping under it:This reaches past the one file:
gh actions-lockrefuses to run when any workflow in the repo fails to parse, so the repo can never acquire a lockfile and can never self-heal.2. Repin
standardsreusables off commits with noactions.lock. The rejection requires the callee to be covered at the pinned SHA — unsatisfiable at a pre-lockfile commit.3. Generate the lockfile with
gh actions-lock.4. Hand-add the reusable-caller entries the tool omits, as
'<path>': [].P(startup_failure | has lockfile) = 91.7%vs15.8%without — because every workflow a lockfile omits is rejected. A partial lock is worse than none. Runninggh actions-lockand stopping there is how this outage spread.5. Restore
SPDX-License-Identifierto line 1, which the tool displaces with its own banner and which the workflow-security linter greps viahead -1.Verified before this PR was opened
0unparseable workflows · lockfile covers every workflow, no omissions · SPDX on line 1 in every file. The script refuses to push if any of the three fails.🤖 Generated with Claude Code