[daily secrets] Daily Secrets Analysis - February 18, 2026 #16635
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-02-21T20:09:18.972Z.
|
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 automated scan of secret usage across all 152 compiled workflow files (
.lock.yml). All 152 workflows have redaction enabled and explicit permission blocks — the security posture remains strong.Key Metrics
secrets.*referencesgithub.tokenreferencesSecret Type Distribution
GITHUB_TOKENGH_AW_GITHUB_TOKENGH_AW_GITHUB_MCP_SERVER_TOKENCOPILOT_GITHUB_TOKENCLAUDE_CODE_OAUTH_TOKENANTHROPIC_API_KEYOPENAI_API_KEYCODEX_API_KEYTAVILY_API_KEYNOTION_API_TOKENView All 24 Secret Types
GITHUB_TOKENGH_AW_GITHUB_TOKENGH_AW_GITHUB_MCP_SERVER_TOKENCOPILOT_GITHUB_TOKENCLAUDE_CODE_OAUTH_TOKENANTHROPIC_API_KEYOPENAI_API_KEYCODEX_API_KEYTAVILY_API_KEYNOTION_API_TOKENGH_AW_PROJECT_GITHUB_TOKENGH_AW_AGENT_TOKENBRAVE_API_KEYDD_SITEDD_APPLICATION_KEYDD_API_KEYSENTRY_OPENAI_API_KEYSENTRY_ACCESS_TOKENCONTEXT7_API_KEYAZURE_TENANT_IDAZURE_CLIENT_SECRETAZURE_CLIENT_IDSLACK_BOT_TOKENGH_AW_BOT_DETECTION_TOKENCategory Totals:
Security Posture
✅ Redaction System: 152/152 workflows (100%) include secret redaction steps
✅ Permission Blocks: 152/152 workflows (100%) have explicit
permissions:definitions✅ Token Cascade Pattern: 473 instances of
GH_AW_GITHUB_MCP_SERVER_TOKEN || GH_AW_GITHUB_TOKEN || GITHUB_TOKENfallback chains — ensures graceful degradation✅ No Secrets in Outputs: 0 instances of secrets leaked into job outputs
✅ Input Sanitization: 146/152 workflows use sanitized inputs to prevent injection
View Security Check Details
Template Injection Risk Assessment
1,897 uses of
github.event.*expressions were found outside ofenv:blocks. These are expected in activation job conditions and if/step conditionals, but should not be used directly in shell scripts. Thesafe-inputssystem handles sanitization of user-supplied content (title, body, text) for 146/152 workflows.6 workflows without explicit sanitization steps may handle only non-user-supplied event data (e.g., scheduled workflows, internal triggers). This warrants a review to confirm none process untrusted user input directly.
Secret Exposure Checks
GH_AW_GITHUB_MCP_SERVER_TOKEN || GH_AW_GITHUB_TOKEN || GITHUB_TOKEN) is consistent across 473 usages, ensuring workflows always have a valid token ✅Trends (vs. Feb 17, 2026)
The previous run (Feb 17) reported a similar profile. Secret types and counts remain stable. No new secret types introduced, no unusual deviations detected.
Recommendations
AZURE_*secrets — Azure credentials (CLIENT_ID, CLIENT_SECRET, TENANT_ID) appear in only 2 workflows each; verify they are scoped to minimal permissions.SENTRY_OPENAI_API_KEY— combination of Sentry + OpenAI key suggests a specific integration; confirm it's intentionally scoped.Reference Documentation
scratchpad/secrets-yml.mdactions/setup/js/redact_secrets.cjsReferences:
Beta Was this translation helpful? Give feedback.
All reactions