Skip to content
testcritic

Static Analysis & Code Quality

Catch defects, duplication and drift before the code ever runs.

8 specialist tools3 free or open source7 self-hostable

What this category is really about

Static analysis reads your code without executing it and flags bugs, code smells, duplication and dependency risk. Its value is compounding: a rule enforced from day one costs nothing, while the same rule applied to a five-year-old codebase produces 12,000 issues nobody will ever fix.

The practical strategy is the clean-as-you-code model — hold new and changed code to the standard, and let legacy debt sit behind a separate, deliberately planned effort. Nearly every tool in this category now supports that framing because the alternative demonstrably fails.

What to evaluate

01

Signal-to-noise ratio

False positives are the whole game. A tool at 40% noise gets disabled within a quarter.

02

Language coverage

Polyglot repos need one tool that covers all of it, or you maintain several quality gates.

03

PR-level gating

Inline comments on the diff, and a status check that can block merge on new issues only.

04

Self-hosting

Some organisations cannot send source code to a third party. Check for an on-prem edition.

Common mistakes

  • Enabling every rule on day one and burying the team.
  • Gating on total coverage rather than coverage of the diff.
  • Auto-fixing formatting and quality in one commit, making the review unreadable.

8 tools built for this

Sorted by how widely adopted they are, not by preference. Tick the compare boxes to put two or more side by side.

Filter these

Tools that also cover this

These are built primarily for something else but handle this category as part of a broader platform — often a way to consolidate two subscriptions into one.