Empty catch block
Part of Code Quality & Syntax, which counts for 20% of the overall score. When this check fires it deducts 15 points from that category, once per scan, no matter how many places it turns up.
What it detects
A catch block (same-line {} or an empty Allman-style block) has no body, so the exception is silently swallowed and the failure it represents becomes invisible until something downstream breaks in a more confusing way.
Why it matters
An empty catch block, whether written as catch (Exception) {} or as an Allman-style catch block with nothing between the braces, discards the exception entirely. The failure it represents does not stop, does not get logged, and does not surface anywhere, so the same problem tends to resurface later as a much more confusing symptom far from its actual cause.
How to fix it
At minimum, log the exception (including the original exception object, not just a generic message) so the failure is visible. If the code genuinely intends to ignore a specific, expected exception type, catch that specific type by name and add a short comment explaining why swallowing it is safe, rather than catching the broad Exception type silently.
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