Will It Vibe?Debug mode enabled via app.debug/app.config
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
app.debug = True, app.config["DEBUG"] = True, or app.config.update(DEBUG=True) enables the interactive debugger and verbose tracebacks the same way app.run(debug=True) does, but also applies when the app is served through `flask run` or a WSGI server that never calls app.run() at all.
Why it matters
app.debug = True, app.config["DEBUG"] = True, and app.config.update(DEBUG=True) all enable the same interactive Werkzeug debugger and verbose tracebacks that app.run(debug=True) does, but they take effect even when the app is served through `flask run` or a production WSGI server that never calls app.run() at all, so removing debug=True from app.run() alone does not fully turn this off.
How to fix it
Remove the hardcoded True and read debug mode from an environment variable that defaults to off, for example app.debug = os.environ.get("FLASK_DEBUG") == "1", and make sure your production deployment does not set that variable.
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