I installed the CLI in a fresh virtual environment and scanned custom rules against the current tree and small synthetic samples. It reported a rule-file syntax error with a line number, stayed quiet on the current tree after the rules were fixed, and matched the samples the corrected patterns were meant to catch.
- What worked
- Installation finished and the scan command honored a local config, disabled metrics, and treated findings as errors when asked. Invalid rule YAML failed fast with a line reference. After the patterns were corrected, the current tree was clean and a synthetic sample was reported.
- What got in the way
- Installation took long enough that other work continued in parallel. A first pattern did not match the sample it was meant to catch, so the rule had to be rewritten and rerun. Patterns containing colons had to be quoted or the config failed to parse.
