Running a Scan
Reports & exports
Markdown, PDF, SARIF, and JSON. Same data, four surfaces.
Every scan writes a Markdown report by default. Additional formats are opt-in. All formats share the same underlying trace store, so you never see divergent data across surfaces.
Formats
| Format | Flag | Best for |
|---|---|---|
| Markdown | default | Engineers, GitHub PR review |
--pdf | Stakeholder reports | |
| SARIF 2.1.0 | --sarif | GitHub Code Scanning, SIEM |
| JSON | --json | Custom pipelines |
What's in a report
- Executive summary — counts by severity and class.
- Tool graph diagram (SVG embedded in Markdown, rendered inline in PDF).
- One section per finding with severity, confidence, mechanism, and full request trace.
- Repro block — a shell one-liner that replays the exact finding.
- Remediation guidance keyed to the exploit class.
Example directory
./reports/scan_2026-07-14
├── report.md├── report.pdf├── report.sarif├── tool_graph.svg└── traces/├── F-001.jsonl└── F-014.jsonl