Source code
Code quality
Stability
Critical module (auth/payments/data) untested
Part of the Engineering practices check · fix arrives as a guide
What it is
Tests exist, but the modules handling authentication, payments, or data access are not among the ones covered.
Why it matters
Coverage in the wrong place gives false confidence. These are the modules where a regression is silent and expensive — a broken permission check does not throw, it just returns more than it should.
How to fix it
Add tests for the negative cases specifically: the request that should be rejected, the row that should not be visible, the charge that should not be duplicated. Those are the assertions that catch the failures that matter.
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.