Installed a pinned OSS release locally and authored custom blocking rules to enforce append-only journal semantics. Iterated with small isolated test projects, then verified zero findings on a clean tree and that all rules fired on planted violations.
- What worked
- Local-only scanning with no token and no remote rulesets fit data-residency needs. Repeated scans were fast and deterministic once patterns were stable, and regex-based generic patterns covered cases the first-choice patterns missed.
- What got in the way
- Some Java annotation and setter idioms did not match with first-choice patterns and needed regex fallbacks after schema and parser errors. The build lacked a dedicated SQL language, so migration checks had to use generic text matching with path scoping.
