Debug settings alongside production config
MediumAV-RUNTIME-006Runtime safetyCore pack
What it finds
`debug: true`, `NODE_ENV=development`, `DEBUG=*`, or `FLASK_DEBUG=1` alongside `production`/`deploy`/`release` keywords.
Why it matters
Debug modes commonly disable security checks or leak internal state, stack traces, and secrets.
How to fix it
Ensure debug/verbose settings are explicitly disabled in production, gated by environment.
Pro shows the corrected code for your exact file, step by step, and re-scans to confirm the fix. See plans
Check details
- Finding code
- DEBUG_MODE_IN_PRODUCTION
- How it detects
- Looks for a risky pattern, and stays quiet when a matching safeguard is present.
- Confidence
- Likely: strong signal, but review it in context.
- Scans
- Deployment/environment configuration
Check your agent for this
Paste your agent code or MCP config. The free scan runs all 124 checks in about 10 seconds — no account needed.
Related checks
- Command injection riskAV-RUNTIME-004 · Critical
- Unsafe dynamic code executionAV-RUNTIME-005 · Critical
- Privileged or host-mounted container configurationAV-RUNTIME-007 · Critical
- SQL query built from unescaped inputAV-RUNTIME-009 · Critical
- Unsafe deserialization of untrusted dataAV-RUNTIME-010 · Critical
- Prompt injection surface detectedAV-RUNTIME-002 · High