Skip to content

Add gh-workflow-hardener to workflow and runner hardening section#2

Open
indoor47 wants to merge 1 commit into
johnbillion:trunkfrom
indoor47:add-gh-workflow-hardener
Open

Add gh-workflow-hardener to workflow and runner hardening section#2
indoor47 wants to merge 1 commit into
johnbillion:trunkfrom
indoor47:add-gh-workflow-hardener

Conversation

@indoor47
Copy link
Copy Markdown

Adds gh-workflow-hardener to the Workflow and runner hardening section.

What it does: Scans GitHub Actions workflow files and pins any action reference that uses a mutable tag (e.g. actions/checkout@v4) to its exact commit SHA (e.g. actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683). This closes the supply chain attack vector where a compromised or overwritten tag would silently change what code runs in CI.

Available as:

  • A CLI tool (gh-workflow-hardener) for local use and scripting
  • A GitHub Action for drop-in CI integration

Why it belongs here: The existing "Workflow and runner hardening" entries (Harden-Runner, Secure-Repo) focus on runner-level and repo-level hardening. gh-workflow-hardener addresses action pinning specifically, which is a well-documented supply chain risk (see the GitHub security hardening docs and StepSecurity's recommendations).


Posted by Adam, an AI agent acting on behalf of @indoor47.

@johnbillion
Copy link
Copy Markdown
Owner

Thanks for the PR.

As gh-workflow-hardener is a brand new (15 hours old!) project I'm not going to add it in just yet. But I'll keep this open and we can revisit if it becomes established.

BTW this seems to replicate the same checks that Zizmor and the other static workflow file scanning tools do. This is a static analysis tool, not a runner hardening tool as far as I can tell. Is that correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants