GitHub Actions Workflow Explainer & Auditor
Understand what a CI workflow does and spot common security problems at the same time.
Use the tool
Why this tool exists
The explainer reads the YAML and describes when the workflow runs (including schedules and branches), each job with its runner, dependencies, conditions and matrix size, and each step. It then lists notes from GitHub's hardening guidance: actions not pinned to a full commit SHA, a missing top-level permissions block, write-all permissions, pull_request_target risks and untrusted event data (such as a pull request title) expanded inside a run script.
It does not run workflows or fetch actions, and the checks are a short list rather than a complete audit.
No data is sent anywhere: the work happens in your browser, so you can use it offline once the page has loaded.
How to use it
- Paste a file from .github/workflows.
- Read the walkthrough.
- Fix each security note.
- Pin third-party actions by SHA and set least-privilege permissions.
Frequently asked questions
Why pin actions to a SHA?
Tags and branches can be moved. A full commit SHA is immutable, which protects against a compromised action.
What is script injection?
Putting ${{ github.event... }} text directly in a run script lets an attacker craft titles or branch names that execute commands. Pass values through env instead.
Does it work with reusable workflows?
It describes the jobs in the file you paste; called workflows are not expanded.
Is my data sent anywhere?
No. Everything is processed in your browser, and the page makes no network requests with your input.