[daily secrets] Secrets Analysis Report - 2026-04-30 #29386
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Daily Secrets Analysis Agent. A newer discussion is available at Discussion #29586. |
Beta Was this translation helpful? Give feedback.
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-04-30
Workflow Files Analyzed: 205
Run: §25188653607
📊 Executive Summary
secrets.*Referencesgithub.tokenReferencesTotal Secret Surface: 8,124 references across 205 compiled workflow files.
The dominant secrets are GitHub tokens (GITHUB_TOKEN: 2,608 and GH_AW_GITHUB_TOKEN: 2,521), accounting for ~62% of all secret references. The three-tier token cascade pattern (GH_AW_GITHUB_MCP_SERVER_TOKEN → GH_AW_GITHUB_TOKEN → GITHUB_TOKEN) is consistently applied across all workflows.
🛡️ Security Posture
All 205 workflows have both redaction steps and explicit permission blocks — full coverage on both controls.
🔍 Security Findings
✅ No Secrets Exposed in Job Outputs
No workflow exports a secret value as a job output. The 35 references found near
outputs:sections are false positives — they are env variable assignments in steps that happen to follow a job's outputs block in the YAML structure.✅
github.event.*Usage is Safe2,559 uses of
github.event.*were detected. Investigation confirms these are all in safe YAML expression contexts (if: conditions, concurrency group keys, env variable assignments) — none appear as raw shell string interpolation inrun:scripts.✅ Token Cascade Pattern Consistently Applied
766 instances of the three-tier cascade
GH_AW_GITHUB_MCP_SERVER_TOKEN || GH_AW_GITHUB_TOKEN || GITHUB_TOKENprovide resilient fallback without hard-coding a single token dependency.Several secrets appear in only 1–4 workflows (OPENROUTER_API_KEY, GH_AW_PLUGINS_TOKEN, SLACK_BOT_TOKEN, Azure credentials, Datadog keys, Sentry tokens). These are expected for specialized integrations but should be audited periodically to confirm they're still active and necessary.
💡 Recommendations
CONTEXTsecret name (2 occurrences) is ambiguous — consider renaming to a more descriptive name to improve auditability.🔑 All 31 Secrets by Usage
📖 Reference Documentation
scratchpad/secrets-yml.mdactions/setup/js/redact_secrets.cjsGenerated: 2026-04-30T20:52 UTC
Beta Was this translation helpful? Give feedback.
All reactions