Source code
Stability
await on external call without try/catch
Part of the Error handling & resilience check · fix arrives as a pull request
What it is
An await on a network call, a database query, or another external dependency sits outside any try/catch.
Why it matters
External calls fail routinely — timeouts, resets, 500s from someone else's deploy. Without handling, a normal upstream blip becomes an unhandled exception and a 500 for the user.
How to fix it
Wrap the call and decide what failure means here: retry it, fall back to a cached value, or return a clear error. The decision belongs at the call site, where you know what the caller can tolerate.
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.