Output: JSON, SARIF, reports
Scout can speak to humans and to machines. By default it prints a graded terminal report; flags switch it to JSON or SARIF.
The terminal report (default)
Section titled “The terminal report (default)”scout scan --target http://localhost:3000Findings grouped by severity, each with confidence, CWE/OWASP, evidence and a fix, followed by a letter grade for the categories assessed.
scout scan --target http://localhost:3000 --jsonEmits the full scan result — target, mode, findings, score, grade — as JSON on
stdout. Pipe it into jq or your own tooling:
scout scan --repo . --json | jq '.findings[] | select(.severity=="high") | .title'SARIF 2.1.0
Section titled “SARIF 2.1.0”scout scan --repo . --sarif scout.sarifWrites SARIF alongside the normal output, ready to upload into GitHub code scanning (see Gate your CI) or any SARIF-aware viewer.
You can combine it with --json or the report — --sarif is additive.
HTML / re-printing a scan
Section titled “HTML / re-printing a scan”Every scan saved to the history DB can be re-printed later by id:
scout report <scan-id>Run scout report with no id to list recent scans. See
Scan history & diff.
Keeping (or not keeping) history
Section titled “Keeping (or not keeping) history”Results are saved to the SQLite file named by --db (default scout.db). To keep
nothing on disk:
scout scan --target http://localhost:3000 --db ""