Will It Vibe?Duplicate route registration
Part of Architecture & Best Practices, which counts for 15% 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
The same HTTP verb and exact path are registered more than once in one file. The router matches the first registration and never reaches the second, so the later handler is unreachable dead code; if the two were meant to behave differently, the second implementation is simply never used and any bug fix made only there has no effect.
Why it matters
When the same HTTP verb and path are registered twice in one file, the router dispatches to whichever was registered first and the second registration never runs. If the two implementations differ, whoever wrote the second one likely believes their version is live and will be confused when bug fixes or new behavior there have no visible effect. This is easy to introduce during a merge or a copy-paste refactor and easy to miss in review since both blocks look like legitimate route definitions.
How to fix it
Decide which implementation should win, delete the other one, and if both had diverging logic, merge whatever the deleted one was doing into the surviving handler before removing it. Search for any tests or callers that assumed the removed handler was the active one.
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