flowguard — sample GitHub Actions security review

Generated from a real scan of bad-workflow.yml — a synthetic fixture, not a customer's repository.
1 file scanned  ·  4 high 2 medium 1 low  ·  7 total findings

Findings

SeverityRuleLocationFieldWhat it meansHow to fix
HIGH FG001 line 9 uses Action 'actions/checkout' uses mutable ref 'v4', not a pinned commit SHA Pin to a full 40-character commit SHA: uses: owner/repo@<40-hex-sha> # v1.2.3
HIGH FG002 line 9 checkout.ref pull_request_target workflow checks out a PR-controlled ref Avoid running PR code under pull_request_target; use pull_request with least-privilege permissions, or never execute checked-out PR code in the privileged job.
HIGH FG003 line 13 run Untrusted github.event text interpolated into a run: script Pass untrusted data through env: and reference it as "$VAR" instead of interpolating ${{ ... }} into the shell.
HIGH FG005 line 18 env.API_PASSWORD Possible hardcoded credential in env key 'API_PASSWORD' (value masked) Use repository/organization secrets via ${{ secrets.NAME }} and rotate any credential that was committed.
MEDIUM FG004 line 4 permissions Workflow uses permissions: write-all Use permissions: contents: read (or the minimum set) and elevate only the specific job that needs more.
MEDIUM FG006 line 15 run Remote content piped directly to a shell Fetch, verify a checksum, then execute a reviewed local copy, or vendor the script into the repository.
LOW FG007 line 9 checkout actions/checkout does not set persist-credentials: false Set persist-credentials: false on the checkout step unless a later step genuinely needs the token.
Scope of this review. flowguard is a line-based heuristic scanner over workflow YAML text. It does not execute workflows, contact GitHub, or read secrets. It may produce false positives/negatives and is not a substitute for a full workflow review. A clean result means none of the seven documented patterns were found — not that the workflow is secure. Credential values are masked.

What a paid review includes

  1. Run flowguard across the supplied workflow files.
  2. Written finding-by-finding report with severity, location, rationale, and concrete fix.
  3. A corrected example workflow (SHA-pinned actions, least-privilege permissions, env-safe scripts).
  4. Optional SARIF file for GitHub code-scanning integration.
  5. One recheck after fixes are applied.

Source and test suite: github.com/sidsri14/flowguard