zizmor
Purpose
Audits every GitHub Actions workflow in your organizations with zizmor, the static analyzer for GitHub Actions. zizmor finds weaknesses that let an attacker take over a workflow or its secrets: template injection, unpinned actions, excessive GITHUB_TOKEN permissions, credential persistence through actions/checkout, cache poisoning, dangerous triggers such as pull_request_target, and actions with known vulnerabilities.
Each finding lands in the graph as a ZizmorFinding linked to the repository, the workflow, and, for findings on a uses: line, the action it concerns. Findings carry the SecurityIssue label, so they sit next to your other security findings in the graph.
The zizmor module has no configuration of its own. It audits the repositories the GitHub module syncs, with the GitHub module's credentials.
Prerequisites
- The GitHub module is configured and has synced at least once.
- The GitHub App installation, or the personal access token, has Contents: Read on the repositories. The recommended GitHub permissions already include it.
Required Fields
None. Enable the module and save.
Setup Steps
- Confirm the GitHub module is configured and has synced.
- In Modules → zizmor, toggle the module enabled and save.
- Trigger a sync from Run Sync, or wait for the next GitHub sync. zizmor runs after GitHub finishes.
What Runs
- Subimage lists every repository that has at least one workflow and is not archived.
- zizmor audits each repository at its default branch, reading the workflows, composite actions, and Dependabot configuration through the GitHub API. Online audits, such as known-vulnerable actions, run too.
- Findings load into the graph. Findings that no longer reproduce are removed.
zizmor uses its regular persona, which keeps false positives to a minimum. It honors a zizmor.yml configuration in the repository. A finding suppressed with a # zizmor: ignore[...] comment is still recorded, with ignored set to true, so you can review what was waived.
Example Query
Workflows with high-severity findings, and the action each one concerns:
MATCH (f:ZizmorFinding {severity: 'high'})-[:AFFECTS]->(w:GitHubWorkflow)
OPTIONAL MATCH (f)-[:AFFECTS]->(a:GitHubAction)
RETURN f.repository, w.path, f.audit_id, f.start_line, a.full_name
ORDER BY f.repository, w.pathTroubleshooting
- "GitHub not connected": no GitHub organization has a usable credential. Configure the GitHub module, let it sync, then run zizmor again.
- Some repositories could not be audited: the run finishes as degraded and names them. Findings for those repositories are kept as they were until a later run audits them again.