You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Daily static analysis scan of 236 workflow files using four tools. Fully stable day — all four tool totals are identical to 2026-05-29, no new runner-guard rule+file pairs. Highest-severity actionable item remains 2 zizmor High github-env findings on dev-hawk.lock.yml, persisting 8 consecutive days since 2026-05-23.
Tools: zizmor, poutine, actionlint, runner-guard
Total Findings: 1,838 — Net change vs 2026-05-29: 0
Issues created this run: none. All High rule+file pairs already have prior issues (closed → skipped; open → commented). Added one recurring-finding comment to open issue #35653 (RGS-018 / daily-byok-ollama-test).
You are fixing a High-severity zizmor finding: github-env (dangerous use of environment file).
Ref: (docs.zizmor.sh/redacted)
Issue: a step writes a runtime-derived value into $GITHUB_ENV, e.g.
GH_HOST="${GITHUB_SERVER_URL#https://}"
echo "GH_HOST=${GH_HOST}" >> "$GITHUB_ENV"
If the value can contain a newline/attacker-influenced data, an attacker can inject extra env
vars (NODE_OPTIONS, PATH) → environment poisoning / code execution in later steps.
Fix (apply in the gh-aw COMPILER TEMPLATE that emits this block — lock files are generated):
1. Validate the derived value against a strict allowlist before writing (hostnames: [A-Za-z0-9.-] only; abort otherwise).
2. Prefer $GITHUB_OUTPUT + steps.<id>.outputs.<name> over $GITHUB_ENV when only later steps in the same job read it.
3. If $GITHUB_ENV is required, use the heredoc-with-random-delimiter form and forbid newlines.
After:
- name: Derive GH_HOST
id: ghes-host-config
run: |
GH_HOST="${GITHUB_SERVER_URL#https://}"; GH_HOST="${GH_HOST#(redacted)
case "$GH_HOST" in *[!A-Za-z0-9.-]*) echo "::error::Unexpected GH_HOST"; exit 1 ;; esac
echo "gh_host=${GH_HOST}" >> "$GITHUB_OUTPUT"
# later: ${{ steps.ghes-host-config.outputs.gh_host }}
Search the compiler for "GH_HOST" + "GITHUB_ENV", apply the validation + GITHUB_OUTPUT migration, recompile so dev-hawk.lock.yml no longer triggers the audit.
Historical Trends
Date
zizmor
poutine
actionlint
runner-guard
2026-05-27
73
24
1,293
285
2026-05-28
73
24
1,450
285
2026-05-29
73
25
1,451
289
2026-05-30
73
25
1,451
289
Previous total 1,838 → current 1,838 → change 0 (0%), fully stable.
New issues: none. Resolved: none — dev-hawk github-env High persists (8th day).
Recommendations
Immediate: Remediate the persistent zizmor High github-env in dev-hawk.lock.yml (741, 1606) via the compiler-template fix above — highest-severity item, unaddressed 8 days.
Analysis Summary
Daily static analysis scan of 236 workflow files using four tools. Fully stable day — all four tool totals are identical to 2026-05-29, no new runner-guard rule+file pairs. Highest-severity actionable item remains 2 zizmor High
github-envfindings ondev-hawk.lock.yml, persisting 8 consecutive days since 2026-05-23.Findings by Tool
Critical / High Severity Issues
github-env[High] ×2 —dev-hawk.lock.ymllines 741 & 1606. Dangerous$GITHUB_ENVwrite. Persisting 8 days.q,ai-moderator,dev-hawk). Prior issues closed.untrusted_checkout_exec[error] ×12 — Arbitrary code exec from untrusted changes (suppressed via# poutine:ignore):dependabot-worker,smoke-workflow-call,smoke-workflow-call-with-inputs.Clustered Findings
Zizmor
GH_AW_WIKI_NOTE: ${{ '' }}(many)Poutine
Actionlint
Runner-Guard (289 findings; no score/grade in output)
Issues created this run: none. All High rule+file pairs already have prior issues (closed → skipped; open → commented). Added one recurring-finding comment to open issue #35653 (RGS-018 / daily-byok-ollama-test).
Runner-Guard dedup decisions
Fix Suggestion — Zizmor
github-env[High]Affected:
dev-hawk.lock.ymllines 741 & 1606 (persisting 8 days). Ref: (docs.zizmor.sh/redacted)Prompt to Copilot Agent:
Historical Trends
github-envHigh persists (8th day).Recommendations
github-envindev-hawk.lock.yml(741, 1606) via the compiler-template fix above — highest-severity item, unaddressed 8 days.untrusted_checkout_execsuppressions.concurrency.queuesyntax-check noise (393); verify whether it is an unrecognized gh-aw extension key.author_associationguard into the compiler so new comment-triggered workflows don't reintroduce RGS-004.Next Steps
github-envin the compiler template (dev-hawk)untrusted_checkout_execsuppressionsconcurrency.queuenoiseauthor_associationguardReferences: §26676218168