Unreachable code after return
Part of Code Quality & Syntax, which counts for 20% 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
Code found at the same indentation level immediately after a return statement will never execute.
Why it matters
Code sitting after a return at the same indentation never executes, so whatever it was meant to do (cleanup, logging, a second write) silently does not happen. Either the code is dead and misleading, or the return is early by mistake and a real behavior is missing.
How to fix it
For each site decide which one is the bug: delete the trailing code if it is obsolete, or move it above the return (or restructure the branch) if it was supposed to run. Turn on ESLint's no-unreachable and TypeScript's allowUnreachableCode: false for JS/TS, and pylint's unreachable warning for Python, to catch new cases.
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