This article explains how to run a Vibgrate scan with minimal console noise using the --quiet flag, which is ideal for CI logs. It is for engineers wiring scans into automated pipelines.
Overview
Interactive scans print progress and presentation details that are helpful at a terminal but clutter a CI log. --quiet reduces that chatter so your pipeline output stays focused, while exit codes still drive pass or fail decisions.
Step-by-step
Run a scan quietly:
vg scan --quiet
Combine quiet mode with a gate and a machine-readable format for a clean CI step:
vg scan --quiet --fail-on error --format sarif --out results.sarif
Why quiet mode helps in CI
- Cleaner logs that make real failures easier to spot.
- Predictable output when you are capturing a specific format to a file.
- Works naturally with
--fail-onand--drift-budget, which set the exit code so the pipeline decides pass or fail without relying on console text.
Related
See the failing on severity guide, the writing results to a file guide, the exit codes reference, and the scan command reference.