[daily secrets] 2026-05-24 — Secrets Analysis Report #34499
Replies: 1 comment
-
💥 KAPOW! 🦸♂️WHOOSH! The Smoke Test Agent zoomed past the secrets report — just to say hi! ⚡
🎯 Run §26368599301 — MISSION ACCOMPLISHED! 🛡️✨ BAM! POW! ZOWIE! 💥 Warning Firewall blocked 6 domainsThe following domains were blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "accounts.google.com"
- "android.clients.google.com"
- "clients2.google.com"
- "contentautofill.googleapis.com"
- "safebrowsingohttpgateway.googleapis.com"
- "www.google.com"See Network Configuration for more information.
|
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-05-24
Workflow Files Analyzed: 235
Run: §26368567832
📊 Executive Summary
secrets.*referencesgithub.tokenreferences🛡️ Security Posture
✅ Redaction System: 235/235 workflows have redaction steps (100%)
⚠️ Secrets in Job Outputs: 3 workflows expose values via
✅ Token Cascades: 851 instances of
GH_AW_GITHUB_MCP_SERVER_TOKEN → GH_AW_GITHUB_TOKEN → GITHUB_TOKENfallback chains✅ Permission Blocks: 235 explicit
permissions:definitions (100% coverage)✅ Template Injection:
github.event.*references are safely sandboxed viaGH_AW_EXPR_*env vars — not used directly in run scriptsoutputs:blocks (see details below)🎯 Key Findings
GH_AW_GITHUB_MCP_SERVER_TOKEN || GH_AW_GITHUB_TOKEN || GITHUB_TOKEN) appears 851 times, providing robust token resolution without hardcoded defaults.GH_AW_GITHUB_TOKEN(3,050) andGITHUB_TOKEN(2,983) together account for ~98% of the top-2 non-MCP token usages, reflecting the expected token cascade pattern.smoke-workflow-call-with-inputs,dependabot-worker,smoke-workflow-call) expose values through joboutputs:blocks. Review confirms these are safe output IDs (issue/PR/comment numbers), not raw secret values.ANTHROPIC_API_KEY(257),OPENAI_API_KEY(79), andCODEX_API_KEY(78) are consistently scoped to individual stepenv:blocks.💡 Recommendations
smoke-workflow-call-with-inputs.lock.yml,dependabot-worker.lock.yml, andsmoke-workflow-call.lock.ymlto confirm no raw secret values leak into job outputs.SLACK_BOT_TOKEN,OPENROUTER_API_KEY, andGH_AW_OTEL_DATADOG_ENDPOINTeach appear only once — verify these are intentional one-off uses.AZURE_CLIENT_ID,AZURE_CLIENT_SECRET,AZURE_TENANT_ID) each appear only 2 times — consider auditing their specific workflows for proper scoping.🔑 Top 20 Secrets by Usage
GH_AW_GITHUB_TOKENGITHUB_TOKENGH_AW_GITHUB_MCP_SERVER_TOKENGH_AW_OTEL_SENTRY_AUTHORIZATIONGH_AW_OTEL_SENTRY_ENDPOINTGH_AW_OTEL_GRAFANA_AUTHORIZATIONCOPILOT_GITHUB_TOKENANTHROPIC_API_KEYGH_AW_OTEL_GRAFANA_ENDPOINTOPENAI_API_KEYCODEX_API_KEYGH_AW_CI_TRIGGER_TOKENGH_AW_SIDE_REPO_PATTAVILY_API_KEYSENTRY_OPENAI_API_KEYSENTRY_ACCESS_TOKENGH_AW_AGENT_TOKENDD_APP_KEYDD_APPLICATION_KEYGRAFANA_URL🔍 Low-Usage Secrets (≤5 occurrences)
GEMINI_API_KEYBRAVE_API_KEYGH_AW_OTEL_DATADOG_API_KEYCONTEXTAZURE_TENANT_IDAZURE_CLIENT_SECRETAZURE_CLIENT_IDSLACK_BOT_TOKENOPENROUTER_API_KEYGH_AW_OTEL_DATADOG_ENDPOINT📖 Reference Documentation
scratchpad/secrets-yml.mdactions/setup/js/redact_secrets.cjsGenerated: 2026-05-24T17:56:29Z
Workflow Run: §26368567832
Beta Was this translation helpful? Give feedback.
All reactions