Reports and Export

Every scan detail page is the canonical report for dashboard, CLI, and hook-originated runs. The source changes how the scan began, not how evidence is displayed.

Included data

• target, type, source, timestamps, status, score, and verdict;
• MCP detection and explicit coverage limitations;
• every stage status and redacted execution error;
• findings grouped by severity and OWASP MCP category;
• file, line, manifest field, tool name, remediation, and verification state;
• resolved and false-positive findings with audit reasons.

Export

Hobby and Team accounts can open the HTML export from scan details and use the browser's Print / Save as PDF action. The printable report retains incomplete-coverage warnings so a saved document cannot turn an inconclusive scan into a clean-looking artifact.

Machine consumers should use aevrin scan --json or authenticated REST endpoints. Do not scrape the printable HTML as an API format.