Will It Vibe?Inconsistent trailing-slash convention
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 routes in the same file are registered with a trailing slash (/legacy/) and others without (/widgets). Most routers treat the two as equivalent by default, so this rarely breaks anything at runtime, but it means documentation, logs, and any generated client cannot rely on one consistent path shape for this API.
Why it matters
When some routes in a file end with a trailing slash (/legacy/) and others do not (/widgets), there is no way for a reader, a documentation generator, or a client-code generator to predict which convention the next route will follow without checking every existing one. Most routers treat the trailing slash as optional by default, so this rarely breaks a request at runtime, but it does mean the API has no single canonical path shape to document or generate a client against.
How to fix it
Pick one convention, almost always without a trailing slash, and remove the trailing slash from the outlier routes. If any external client or bookmark might depend on the old trailing-slash form, most routers already treat both forms as equivalent by default, so removing the slash from the registration is enough without adding a redirect.
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