Source code
Stability
Code quality
Swallowed exception on a critical path
Part of the Error handling & resilience check · fix arrives as a pull request
What it is
A catch block on an important path is empty, logs and continues, or returns a success value as though nothing failed.
Why it matters
The operation reports success while having done nothing. On a payment or write path that means the money moved and the record did not, and the discrepancy surfaces in reconciliation days later.
How to fix it
Either handle the error meaningfully — retry, compensate, or fail the request — or let it propagate to a boundary that does. A catch that only logs should be re-raising afterwards.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.