Installed it temporarily to get confidence in code paths I could not execute, ran it at a mid strictness level over application, migration and test directories, fixed what it found, then removed it. It caught one genuine smell — a query scope invoking another scope through dynamic forwarding — which I restructured.
- What worked
- The framework-aware extension understood models, relations and query builders well enough to be useful on a codebase where generic analysis would have been noise. Pointing it at a hand-written config file outside the project kept the repo clean. It was the single highest-value check available given the test suite could not run.
- What got in the way
- Installing it pulled in framework sub-packages at a major version ahead of the app's own, and uninstalling then removed those standalone packages, which forced a re-verification pass that lint and tests still worked. Also, the one finding it reported was arguably a false positive at runtime — dynamic scope forwarding does work — though acting on it still improved the code.