[daily secrets] Daily Secrets Analysis Report #48704
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Daily Secrets Analysis Agent. A newer discussion is available at Discussion #48953. |
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-07-28
Workflow Files Analyzed: 264
Run: §30385571017
📊 Executive Summary
secrets.*)github.token)env:entries rather than job-levelenv:)🛡️ Security Posture
✅ Redaction System: 264/264 workflows have
redact_secretssteps (100% coverage)✅ Token Cascades: 947 instances of
GH_AW_GITHUB_MCP_SERVER_TOKEN || secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKENfallback chains✅ Permission Blocks: 264 explicit
permissions:definitions (one per workflow — full coverage)Template injection scan: 4,703 raw
github.event.matches were found across all lock files, but these are expected — the compiler consistently routes untrustedgithub.event.*values through intermediateenv:variables before use in scripts, rather than interpolating them directly into shell/JS bodies. No raw unguarded${{ github.event.* }}interpolation insiderun:script bodies was found on manual spot-check of several matches.Secrets-in-outputs scan: 33 raw matches, but on inspection every one is a step-level
env:assignment (e.g.,ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}) that happened to fall within 5 lines of an unrelatedoutputs:block — not an actual joboutputs:exposing a secret value. ✅ No genuine secret exposure via job outputs found.🎯 Key Findings
GH_AW_GITHUB_MCP_SERVER_TOKEN→GH_AW_GITHUB_TOKEN→GITHUB_TOKENfor MCP server auth, which limits blast radius if a narrower-scoped token is unavailable.redact_secretsstep and an explicitpermissions:block — a strong baseline security control ensuring least-privilege intent and secret-leak mitigation are present everywhere.💡 Recommendations
secrets.GITHUB_TOKENdirectly without the fallback cascade; consider auditing for consistency during the next workflow update pass.github.event.*usage inrun:script bodies (not justenv:blocks) is recommended to guard against future template-injection regressions as new workflows are added.🔑 Top 10 Secrets by Usage
📈 Trends
This is the first recorded run of the daily secrets analysis in this environment — no prior "[daily secrets]" discussion was found to compare against. Baseline stats have been captured for future day-over-day comparison.
📖 Reference Documentation
For detailed information about secret usage patterns, see:
scratchpad/secrets-yml.mdactions/setup/js/redact_secrets.cjsGenerated: 2026-07-28 18:05 UTC
Workflow: daily-secrets-analysis
All reactions