Installed the OSS CLI in a virtual environment, authored local rules for money-movement, migrations, and security, and scanned both the existing tree and a violation fixture. OSS-only mode and metrics-off were enough to keep analysis on-box. YAML and Java pattern issues took a few iterations before the clean tree stayed green and the fixture produced findings.
- What worked
- Pinned OSS-only scans with local rules ran without a cloud token. After the rule fixes, a full scan reported no findings on the current tree, and a fixture with deliberate violations produced many findings. Help text confirmed the OSS-only and metrics flags.
- What got in the way
- An unquoted rule message containing a colon made one rules file invalid YAML. A top-level pattern plus pattern-not missed annotated methods, and a chained access-control matcher did not fire until the pattern used a receiver metavariable. Those were rule-authoring issues, not scanner crashes.
