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
Step-Level Usage: 4,558 (100.0%) — note: the job/step split uses a line-proximity heuristic and likely undercounts job-level env: blocks; treat this figure as directional only, not authoritative.
🛡️ Security Posture
✅ Redaction System: 299/299 workflows have redaction steps (100% coverage)
✅ Token Cascades: 1,014 instances of fallback chains (GH_AW_GITHUB_MCP_SERVER_TOKEN || secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN)
✅ Permission Blocks: 299 explicit permissions: definitions (1 per workflow — full coverage)
Deterministic Go test checks (pkg/workflow):
✅ TestCompiledLockFiles_NoGitHubEventExpressionsInRunScripts — PASS: no direct github.event.* interpolation found in executable run: scripts across all compiled workflows (template injection risk check).
✅ TestCompiledLockFiles_NoSecretsInOutputs — PASS: no secrets detected in job outputs or workflow_call outputs.
🎯 Key Findings
Full redaction and permission coverage: All 299 compiled .lock.yml files include a redaction step and an explicit permissions: block — no workflow is running with implicit/default permissions.
GITHUB_TOKEN and GH_AW_GITHUB_TOKEN dominate usage: together they account for ~97% of all secrets.* references (5,348 + 4,557 of 10,253), consistent with the standard token-cascade pattern used for GitHub API access.
Observability secrets are widespread but scoped: OTEL/Sentry/Grafana/Datadog credentials (GH_AW_OTEL_*) appear in a few hundred workflows each, all following the GH_AW_ naming convention rather than raw provider secret names — good namespacing hygiene.
No anomalous or unexpected secret names: all 40 unique secret identifiers match established naming conventions (GH_AW_* custom secrets, standard vendor API keys like OPENAI_API_KEY/ANTHROPIC_API_KEY/CODEX_API_KEY, and GitHub tokens). No signs of ad hoc or leaked-looking secret names.
No historical baseline available: this is the first "[daily secrets]" discussion in this repository, so no day-over-day trend comparison could be performed yet. Tomorrow's run will be the first with a comparable baseline.
💡 Recommendations
Refine job vs. step-level accounting: replace the current line-proximity grep heuristic with a structured YAML-aware count (similar to the Go tests used for template-injection/output checks) to get an accurate job-level vs. step-level secret usage breakdown.
Continue enforcing the two deterministic Go security tests (NoGitHubEventExpressionsInRunScripts, NoSecretsInOutputs) as CI gates on every compile — both passed cleanly today and should remain required checks.
Persist historical stats (e.g., as a discussion or artifact) across runs so future daily reports can surface real secret-usage trend deltas instead of only point-in-time snapshots.
🔑 Top 15 Secrets by Usage
Rank
Secret Name
Occurrences
Type
1
GITHUB_TOKEN
5,348
GitHub Token
2
GH_AW_GITHUB_TOKEN
4,557
GitHub Token
3
GH_AW_GITHUB_MCP_SERVER_TOKEN
1,945
GitHub Token
4
GH_AW_OTEL_SENTRY_AUTHORIZATION
744
Observability
5
COPILOT_GITHUB_TOKEN
527
GitHub Token
6
GH_AW_OTEL_SENTRY_ENDPOINT
497
Observability
7
GH_AW_OTEL_GRAFANA_AUTHORIZATION
495
Observability
8
OPENAI_API_KEY
398
AI Provider
9
CODEX_API_KEY
397
AI Provider
10
ANTHROPIC_API_KEY
255
AI Provider
11
GH_AW_OTEL_GRAFANA_ENDPOINT
248
Observability
12
GH_AW_DEFAULT_OTLP_HEADERS
102
Observability
13
GH_AW_CI_TRIGGER_TOKEN
70
GitHub Token
14
GH_AW_SIDE_REPO_PAT
24
GitHub Token
📈 Trends
No historical data available yet — this is the first "[daily secrets]" discussion generated in this repository. Starting with today's run, statistics will be persisted so future reports can show day-over-day deltas (new secret references, removed secrets, cascade pattern changes, etc.).
📖 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-09-10
Workflow Files Analyzed: 299
Run: 34509526676
📊 Executive Summary
secrets.*)github.token)env:blocks; treat this figure as directional only, not authoritative.🛡️ Security Posture
✅ Redaction System: 299/299 workflows have redaction steps (100% coverage)
✅ Token Cascades: 1,014 instances of fallback chains (
GH_AW_GITHUB_MCP_SERVER_TOKEN || secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN)✅ Permission Blocks: 299 explicit
permissions:definitions (1 per workflow — full coverage)Deterministic Go test checks (
pkg/workflow):TestCompiledLockFiles_NoGitHubEventExpressionsInRunScripts— PASS: no directgithub.event.*interpolation found in executablerun:scripts across all compiled workflows (template injection risk check).TestCompiledLockFiles_NoSecretsInOutputs— PASS: no secrets detected in job outputs orworkflow_calloutputs.🎯 Key Findings
.lock.ymlfiles include a redaction step and an explicitpermissions:block — no workflow is running with implicit/default permissions.GITHUB_TOKENandGH_AW_GITHUB_TOKENdominate usage: together they account for ~97% of allsecrets.*references (5,348 + 4,557 of 10,253), consistent with the standard token-cascade pattern used for GitHub API access.GH_AW_OTEL_*) appear in a few hundred workflows each, all following theGH_AW_naming convention rather than raw provider secret names — good namespacing hygiene.GH_AW_*custom secrets, standard vendor API keys likeOPENAI_API_KEY/ANTHROPIC_API_KEY/CODEX_API_KEY, and GitHub tokens). No signs of ad hoc or leaked-looking secret names.💡 Recommendations
NoGitHubEventExpressionsInRunScripts,NoSecretsInOutputs) as CI gates on every compile — both passed cleanly today and should remain required checks.🔑 Top 15 Secrets by Usage
📈 Trends
No historical data available yet — this is the first "[daily secrets]" discussion generated in this repository. Starting with today's run, statistics will be persisted so future reports can show day-over-day deltas (new secret references, removed secrets, cascade pattern changes, etc.).
📖 Reference Documentation
For detailed information about secret usage patterns, see:
scratchpad/secrets-yml.mdactions/setup/js/redact_secrets.cjsGenerated: 2026-09-10 17:43 UTC
Workflow: daily-secrets-analysis
All reactions