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
Template injection check: 5,112 occurrences of github.event. patterns found across lock files. These are expected — expressions are consistently routed through env: interpolation rather than direct shell/script interpolation, which is the safe pattern gh-aw enforces at compile time. No raw unsafe interpolation detected in spot checks.
Secrets-in-outputs check: Initial grep flagged 34 matches, but manual verification confirmed these are false positives from context-window overlap in the search (unrelated outputs: blocks followed much later by unrelated secrets.* lines in Docker command construction). ✅ No actual secret exposure in job outputs: found.
🎯 Key Findings
GITHUB_TOKEN and GH_AW_GITHUB_TOKEN dominate usage — combined ~9,000+ references (97% of all secret refs), consistent with the token-cascade pattern used for GitHub API auth across MCP servers and safe-outputs.
Step-level-only secret injection — no job-level env: blocks reference secrets directly; every workflow scopes secrets to the specific step that needs them, minimizing blast radius/exposure surface.
LLM provider keys are well-isolated — ANTHROPIC_API_KEY (264), OPENAI_API_KEY (107), and CODEX_API_KEY (106) appear only in engine-specific steps, with no overlap into unrelated jobs based on sampling.
Full redaction and permission coverage — 100% of the 275 lock files include both a redaction step and an explicit permissions: block, indicating consistent application of the compiler's safety defaults.
💡 Recommendations
No action required — secret usage patterns remain consistent with expected step-scoped, redacted, cascade-based design; no anomalies or regressions detected.
Continue monitoring GH_AW_SIDE_REPO_PAT (24) and GH_AW_AGENT_TOKEN (15) usage — these are lower-frequency, higher-privilege tokens; periodic review of which workflows use them is worthwhile to ensure least-privilege stays intact as new workflows are added.
🔑 Top 10 Secrets by Usage
Rank
Secret Name
Occurrences
Type
1
GITHUB_TOKEN
4,828
GitHub Token
2
GH_AW_GITHUB_TOKEN
4,154
GitHub Token
3
GH_AW_GITHUB_MCP_SERVER_TOKEN
1,809
GitHub Token
4
COPILOT_GITHUB_TOKEN
791
GitHub Token
5
GH_AW_OTEL_SENTRY_AUTHORIZATION
711
Observability
6
GH_AW_OTEL_SENTRY_ENDPOINT
475
Observability
7
GH_AW_OTEL_GRAFANA_AUTHORIZATION
473
Observability
8
ANTHROPIC_API_KEY
264
LLM Provider
9
GH_AW_OTEL_GRAFANA_ENDPOINT
237
Observability
10
OPENAI_API_KEY
107
LLM Provider
📈 Trends
No historical baseline is available yet for this repository run — this establishes the first tracked snapshot (2026-08-05: 275 workflows, 9,249 secret refs, 41 unique secret types, 100% redaction coverage). Future runs will compare against this baseline.
📖 Reference Documentation
For detailed information about secret usage patterns, see:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
🔐 Daily Secrets Analysis Report
Date: 2026-08-05
Workflow Files Analyzed: 275
Run: §31033152097
📊 Executive Summary
secrets.*)github.token)env:blocksenv:blocks🛡️ Security Posture
✅ Redaction System: 275/275 workflows have redaction steps (100% coverage)
✅ Token Cascades: 985 instances of fallback chains (
GH_AW_GITHUB_MCP_SERVER_TOKEN || secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN)✅ Permission Blocks: 275 explicit permission definitions (1 per workflow — fully covered)
Template injection check: 5,112 occurrences of
github.event.patterns found across lock files. These are expected — expressions are consistently routed throughenv:interpolation rather than direct shell/script interpolation, which is the safe pattern gh-aw enforces at compile time. No raw unsafe interpolation detected in spot checks.Secrets-in-outputs check: Initial grep flagged 34 matches, but manual verification confirmed these are false positives from context-window overlap in the search (unrelated
outputs:blocks followed much later by unrelatedsecrets.*lines in Docker command construction). ✅ No actual secret exposure in joboutputs:found.🎯 Key Findings
env:blocks reference secrets directly; every workflow scopes secrets to the specific step that needs them, minimizing blast radius/exposure surface.ANTHROPIC_API_KEY(264),OPENAI_API_KEY(107), andCODEX_API_KEY(106) appear only in engine-specific steps, with no overlap into unrelated jobs based on sampling.permissions:block, indicating consistent application of the compiler's safety defaults.💡 Recommendations
🔑 Top 10 Secrets by Usage
📈 Trends
No historical baseline is available yet for this repository run — this establishes the first tracked snapshot (2026-08-05: 275 workflows, 9,249 secret refs, 41 unique secret types, 100% redaction coverage). Future runs will compare against this baseline.
📖 Reference Documentation
For detailed information about secret usage patterns, see:
scratchpad/secrets-yml.mdactions/setup/js/redact_secrets.cjsGenerated: 2026-08-05T18:11 UTC
Workflow: daily-secrets-analysis
All reactions