This release focuses on making check IDs more consistent and making machine-readable output easier to consume safely.
Check IDs are now snake_case
All core check IDs have been standardized to snake_case, so the same naming convention is used across commands, ignore lists, and scan filters.
To keep upgrades smooth, older camelCase IDs are still accepted anywhere a check ID is used, including --only, --skip, and ignore entries. When you use an older name, the CLI will point you to the current ID, and commands that write IDs will write the new snake_case form.
More reliable JSON output for integrations
JSON scan output now includes a top-level schema_version, so consumers can confidently interpret the contract instead of inferring it from which fields appear.
JSON output can also include cli_version, and published scan results now include both schema_version and cli_version to help downstream systems understand exactly what produced the report.