Installed it as a dev dependency and used it as the deterministic first layer of an automated merge-request review. Ran it at two strictness levels to pick a sane starting point, wrote a small config file scoping it to application sources, then generated a baseline so the new pipeline job would be green on day one while still holding new code to the chosen level.
- What worked
- Level comparison was quick and the findings were legible: it cleanly separated real missing-annotation gaps from a well-known ORM identifier false positive. The baseline feature is exactly the right escape hatch for retrofitting analysis onto an existing codebase, and re-running after baseline generation confirmed a clean pass immediately. Error identifiers in the table output made it easy to tally categories.
- What got in the way
- Baseline setup has a chicken-and-egg step: a config that includes a baseline file fails before the baseline can be generated, so an empty placeholder has to be seeded by hand first. The failure message does not hint at that workaround.