[daily secrets] Secrets Usage Analysis — 284 Workflows, 100% Redaction Coverage #51620
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Daily Secrets Analysis Agent. A newer discussion is available at Discussion #52126. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🔐 Daily Secrets Analysis Report
Date: 2026-08-09
Workflow Files Analyzed: 284
Run: 31327252093
📊 Executive Summary
secrets.*)github.token)GH_AW_GITHUB_MCP_SERVER_TOKEN || secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKENpermissions:definitions (1 per workflow, as expected)🛡️ Security Posture
✅ Redaction System: 284/284 workflows (100%) have
redact_secretssteps — full coverage✅ Token Cascades: 1,013 fallback-chain usages, indicating consistent least-privilege token selection pattern
✅ Permission Blocks: every compiled workflow declares explicit permissions
✅ No secrets in outputs: the 37 raw matches on
secrets\.nearoutputs:blocks were checked manually — all are unrelatedenv:assignments (e.g.ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }},COPILOT_GITHUB_TOKEN) that happen to fall within the grep context window, not actualoutputs:fields. No genuine secret leakage into job/step outputs was found.✅
github.event.*interpolation: 5,298 matches found, but all are assigned intoenv:blocks (456+ occurrences directly adjacent toenv:) rather than interpolated directly into shell command strings — this is the expected, safe gh-aw pattern that avoids template/script injection. No unsafe direct interpolation detected.🎯 Key Findings
GITHUB_TOKENandGH_AW_GITHUB_TOKENdominate usage (4,977 and 4,286 occurrences respectively), consistent with gh-aw's standard token-cascade design for GitHub API access across MCP servers and safe-output jobs.ANTHROPIC_API_KEY(264),OPENAI_API_KEY(107),CODEX_API_KEY(106) appear only in workflows using their respective agentic engines, with no cross-contamination observed.GH_AW_OTEL_SENTRY_AUTHORIZATION/GH_AW_OTEL_GRAFANA_AUTHORIZATION(735/489) plus matching endpoint secrets, reflecting the shared OTel logging pipeline rather than isolated one-off configuration.redact_secrets.cjs) is applied uniformly across all compiled workflows — no workflow bypasses this control.💡 Recommendations
redact_secretsstep as a compilation defect to fail CI on.GH_AW_GITHUB_MCP_SERVER_TOKEN || secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN) in new workflows to avoid directsecrets.GITHUB_TOKENusage without fallback ordering.🔑 Top 10 Secrets by Usage
📈 Trends
No prior-day stats file was found in this run environment (
/tmp/gh-aw/agent/secrets-stats.jsonwas absent at start), so this is treated as the current-day baseline snapshot. Future runs should compare against this baseline: 284 workflows, 9,773 secret refs, 44 unique secret types, 100% redaction coverage.📖 Reference Documentation
For detailed information about secret usage patterns, see:
scratchpad/secrets-yml.mdactions/setup/js/redact_secrets.cjsGenerated: 2026-08-09T17:48:15Z
Workflow: daily-secrets-analysis
All reactions