Reports & Compliance

Professional security reports in four formats. Compare scans side-by-side, track finding lifecycle, and share results with your team and stakeholders.

Four Formats, One Complete Picture

Different teams need different formats. Developers want SARIF in GitHub, analysts want CSV in spreadsheets, executives want PDF summaries, and CI pipelines want JSON. Vuln0x generates all four from every scan so you never have to choose.

SARIF

GitHub Integration

The Static Analysis Results Interchange Format is the industry standard for security tooling. Upload SARIF reports directly to the GitHub Security tab to surface vulnerabilities alongside your code. Every finding maps to a CWE, includes severity, confidence, and remediation guidance so your developers can fix issues without leaving their pull request workflow.

  • Native GitHub Security tab integration
  • CWE-mapped findings with severity levels
  • Machine-readable for tool chaining

CSV

Spreadsheet Analysis

Export raw findings data to CSV for custom analysis in Excel, Google Sheets, or any data tool. Filter by severity, group by scanner, calculate remediation time, or build executive dashboards. CSV exports include every field: finding ID, title, severity, scanner, URL, evidence, recommendation, and status.

  • Open in Excel or Google Sheets
  • Pivot tables for executive dashboards
  • Full field set for custom analysis

PDF

Professional Reports

Generate branded, print-ready PDF reports that you can share with stakeholders, compliance auditors, and management. Each report includes an executive summary with your risk score and grade, a detailed findings table with severity breakdown, scanner-by-scanner results, and actionable remediation steps. PDFs are designed to communicate security posture clearly to both technical and non-technical audiences.

  • Executive summary with risk score
  • Detailed findings and remediation steps
  • Shareable with non-technical stakeholders

JSON

CI/CD Pipelines

The JSON export provides the complete scan response in a structured, machine-parseable format. Use it to build custom dashboards, feed data into SIEM systems, or create quality gates in your CI/CD pipelines. JSON reports include metadata, scan configuration, all findings with evidence, and the aggregate risk score.

  • Complete scan data in structured format
  • Ideal for CI/CD quality gates
  • Feed into SIEM or custom dashboards
Scan Comparison

Diff Two Scans Side-by-Side

Deployments should make your application more secure, not less. The scan comparison feature lets you select any two scan records and see exactly what changed between them: new findings that appeared, existing issues that were resolved, and findings that remain unchanged.

This is especially powerful when combined with scheduled scans. After every weekly run, you can compare the latest scan against the previous one to understand whether your latest deploy introduced regressions or successfully closed open issues. The comparison view highlights risk score deltas, severity distribution shifts, and individual finding changes.

New

Findings that appeared since the baseline scan

Resolved

Findings that were fixed between the two scans

Unchanged

Findings present in both scans

Comparison Summary

Baseline ScanFeb 24, 2025
Latest ScanMar 3, 2025
Risk Score
6882
Grade
DB
New Findings
2
Resolved
7
Unchanged
12

Finding Lifecycle Management

Security findings are not binary — they move through a lifecycle from discovery to resolution. Vuln0x tracks every status transition with timestamps and user attribution, giving you a complete audit trail for compliance and accountability.

Open
Acknowledged
Fixed
Risk Accepted
Open

A newly discovered finding that requires attention. Open findings contribute to your risk score and remain visible in all reports until they are triaged.

Acknowledged

Your team has reviewed the finding and confirmed it is a genuine issue. Acknowledging a finding signals that remediation work is planned or in progress.

Fixed

The vulnerability has been remediated. Run a verification scan (1 credit) to confirm the fix. Once verified, the finding is excluded from your active risk score.

Risk Accepted

Your team has deliberately accepted the risk after evaluation. The finding is documented for audit purposes but no longer inflates your active risk score.

Finding Status History

Every status change is recorded with the user, timestamp, and optional note. This audit trail is invaluable for compliance reviews, incident post-mortems, and understanding your team's remediation velocity.

Opened — Missing Content-Security-Policy header detected by Header Scanner

Feb 24, 2025 at 02:04 UTC — Automated

Acknowledged — Triaged and added to sprint backlog

Feb 25, 2025 at 14:32 UTC — by alex@example.com

Fixed — CSP header added in middleware, verified with rescan

Mar 1, 2025 at 09:18 UTC — by alex@example.com

Start securing your vibe-coded projects today

20 free credits on signup. No credit card required.