Will It Vibe?todo!()/unimplemented!() in shipped source
Part of Code Quality & Syntax, which counts for 20% 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
todo!()/unimplemented!() left in non-test source panics unconditionally if that code path is ever reached at runtime: an unfinished implementation shipped as if it were complete.
Why it matters
todo!() and unimplemented!() are meant as compile-time placeholders during development; if that code path is ever actually reached at runtime, the process panics unconditionally. Shipping one means some feature or branch was left unfinished, and the first user (or automated job) to exercise it gets a crash instead of a real error or result.
How to fix it
Implement the missing logic before shipping, or if the path is genuinely not supported yet, replace the panic with an explicit, recoverable error (return a Result::Err with a clear message, or an HTTP 501/400 in a handler) so callers get a real response instead of a crash. If the branch truly cannot be reached given the type system's guarantees, unreachable!() with a comment explaining why is more honest than todo!()/unimplemented!().
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