Source code
Stability
No error-reporting integration
Part of the Observability gaps check · fix arrives as a guide
What it is
No error-reporting service is wired up — exceptions are logged, or not, but nothing aggregates and alerts on them.
Why it matters
Errors in logs are only found by someone already looking. A new exception introduced by this morning's deploy runs for as long as it takes a user to complain, and you get no signal that its rate is climbing.
How to fix it
Add an error reporter, hook it into your unhandled exception and rejection paths, and set the release version so regressions are attributed to the deploy that introduced them.
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.