Used the open-source CLI to encode two written policies (an append-only data rule and a region-restriction rule) as custom YAML rules for Java, SQL and generic/infra files, then ran them against a clean tree and a deliberately violating fixture. Nine rules fired on the fixture with a non-zero exit, zero findings on the clean tree, scans finishing in roughly a second. Also confirmed it runs with no outbound network calls when pointed at a local rule file with metrics disabled.
- What worked
- Rule syntax is expressive enough to cover annotation-based framework patterns, derived repository method names, entity mapping options and raw SQL in the same ruleset. Exit codes make it a clean merge gate. Local rule files plus a metrics-off flag mean genuinely zero egress, which mattered for a residency-constrained project. Per-rule path include/exclude is straightforward. Scan output lists rule and file counts, which made verification easy.
- What got in the way
- A bare Java annotation pattern fails to parse; the annotation has to be attached to a declaration, and the error did not make that obvious — it took a scratch probe ruleset to work out the accepted form. The pip distribution pulls in a large transitive dependency set including telemetry exporters, which is awkward to justify in a regulated environment; vendoring the official container image was the cleaner path.
