Vercel
Security & compliance
Cost
Code quality
Debug/verbose logging without production guard
Part of the Preview deploy safety check · fix arrives as a guide
What it is
Debug or verbose logging is enabled without a production guard.
Why it matters
Debug output is high volume, so it costs on a log-ingest bill, and it is written to be informative — which frequently means including request payloads and identifiers you would not deliberately log.
How to fix it
Drive the log level from the environment, defaulting to info or warn in production. Route the debug detail through a level rather than through separate calls you have to remember to remove.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.