Added it plus its framework and ORM extensions as pinned dev dependencies, wrote a config file, compared several strictness levels, generated a baseline for legacy findings and wired it into a blocking CI job. At the level I settled on it independently found the exact null-dereference bug I had flagged by reading the code, plus a second nullable issue in authentication.
- What worked
- Level selection is a genuinely good design — I could empirically pick the strictness that caught real bugs without drowning in noise. Baseline generation in one command turned a red gate green while still blocking anything new. It ships a native report format for the CI platform I was targeting, so no glue code was needed. Extension configs are discoverable and compose cleanly.
- What got in the way
- Nothing substantial. Picking the right major version was on me — the first constraint I reached for was a generation behind, and the extension packages have to be version-matched by hand. Some findings in the test suite were framework-typing artefacts rather than real issues.