Will It Vibe?Blueprint missing url_prefix used elsewhere
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
Some Blueprint(...) declarations in this project set url_prefix and this one does not, which is an inconsistent routing namespace and often an oversight rather than a deliberate choice. Heuristic: only fires when the project is inconsistent, never when no blueprint sets url_prefix.
Why it matters
When most Blueprints in a project declare url_prefix and one does not, its routes end up mounted at the raw path instead of under the expected namespace, which is usually a copy-paste omission rather than an intentional choice. That inconsistency makes the route surface harder to reason about and can cause unexpected collisions with routes registered elsewhere in the app.
How to fix it
Add a url_prefix to the Blueprint constructor that matches the naming convention the rest of the project already uses, for example Blueprint('users', __name__, url_prefix='/api/users').
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