Will It Vibe?Route path contains a doubled slash
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
A registered route path contains '//' in the middle, for example /api//legacy. This is almost always a leftover from string concatenation or a template literal whose base already ended in a slash, and it means the route never matches the path a developer actually intended.
Why it matters
A route path with a doubled slash, like /api//legacy, does not match the path a client would naturally send for /api/legacy: depending on the router, it either fails to match at all or only matches a request that itself contains the same literal double slash, which almost no client will send unintentionally. This strongly suggests a string-concatenation bug, most often a base path that already ends in '/' having another '/' appended to it.
How to fix it
Find the doubled slash in the route registration and remove the extra one, for example changing /api//legacy to /api/legacy. If the path is built by concatenating a prefix variable with a literal, check whether the prefix already includes a trailing slash and normalize it once at the source instead of patching each route individually.
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