No environment-specific configuration
Part of Architecture & Best Practices, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
No per-environment config/env files were found, suggesting dev and production share identical configuration.
Why it matters
With a single config for every environment, dev conveniences like verbose logging, disabled caching, and local URLs ship to production, or production values sit in the file every developer runs locally. Per-environment configuration is what lets the same code run safely in both places. It also keeps production secrets out of day-to-day dev setups.
How to fix it
Split deploy-specific values out of the shared config into environment variables, with per-environment files (.env.development, .env.production, following your framework’s convention) or config.dev/config.prod variants selected by NODE_ENV or APP_ENV. Keep only environment-independent settings in the shared config file, and commit a .env.example naming the variables. Next.js, Vite, and Django all have this convention built in.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo