
github-actions-hardening
Security hardening reviewer for GitHub Actions workflow files
by githubFree
Description
github-actions-hardening is an agent skill from the github/awesome-copilot collection that reviews GitHub Actions workflow files for security weaknesses. It focuses on the threat model specific to Actions rather than the application code a general scanner checks. Its premise is that most workflow risks are invisible to language linters, because the dangerous part is the YAML itself and the way GitHub expands expressions into a shell before a script runs. The review looks at where trust boundaries sit in the different trigger types, what permissions the workflow token has and whether they are scoped down, and whether untrusted input, such as a pull request title or branch name, is interpolated into a shell command where it could inject commands. It applies to workflow files under .github/workflows and to requests about securing CI. The output points to the specific lines and explains how each risk could be exploited, along with a hardened alternative. It is useful for maintainers of repositories that accept contributions from outside, because workflows triggered by outside pull requests are a common route to leaked secrets. A review is not a guarantee, so the team should test the changed workflows and rotate any secret that may have been exposed. The skill is installed with the skills CLI from the github/awesome-copilot repository. Its skills.sh page showed about 1.9K installs and passing results from three security audits at the time of the scan.…
Highlights
- Actions-specific threat model review
- Trust boundaries across trigger types
- Token permission scoping
- Expression injection in shell steps
- Specific fixes for each finding
- Installs with the skills CLI
Ratings & Reviews
No ratings yet
Be the first to rate github-actions-hardening.
People also visit

mtls-configuration
Configure mutual TLS (mTLS) for zero-trust service-to-service communication
github-actions-hardening FAQ
What kind of risks does it find?
Workflow-specific issues such as broad token permissions, trust boundaries in triggers, and untrusted input injected into shell commands.
Why is this different from a normal scanner?
The risk is in the YAML and how expressions expand into shell, which general code scanners and linters miss.
Why do outside pull requests matter?
Workflows triggered by them can be a route to leaked secrets, so they need the closest review.
Does a clean review mean the workflow is safe?
No. Test the changed workflows, and rotate any secret that may have been exposed.
How do I install it?
Run npx skills add https://github.com/github/awesome-copilot --skill github-actions-hardening.
What security audits does it have?
skills.sh lists three audits: Gen Agent Trust Hub Pass, Socket Pass and Snyk Pass.
What are the best github-actions-hardening alternatives?
Popular alternatives to github-actions-hardening include codeql, SkillSpector and attack-tree-construction. See all github-actions-hardening alternatives




