Choose human or machine output and make violations fail the pipeline.
Reporting and CI integration
Output formats
| Format | Use |
|---|---|
| text | Terminal and local review with file, line, severity, rule ID, and message. |
| json | CI ingestion or custom post-processing. |
| html | Standalone scan report with totals, severity counts, and a detailed table. |
Minimal CI step
python -m salt check rtl tb --config salt.yaml --format json > salt-report.json
Because any violation returns 1, the command can gate a pipeline directly. If the report must be retained on failure, configure the CI system to upload salt-report.json in an always-run artifact step.
Add visibility without corrupting reports
Use --log-level info or debug to see configuration loading, discovery, enabled-rule totals, and completion counts on stderr while stdout remains parseable.