supabase-report-compare

You can compare two security audit reports by providing structured Markdown files of past and current audits. The tool analyzes findings by severity, calculates remediation rates, and visualizes score changes to highlight fixed vulnerabilities and new regressions.

Detecting new vulnerabilities introduced after a security audit involves comparing the latest report against the previous one. This regression detection process automatically flags newly introduced issues alongside unresolved findings to pinpoint security posture declines.

Yes, tracking security remediation requires structured Markdown input for accurate comparison and reporting. The Markdown audit files must contain properly formatted findings so the tool can correctly analyze severity, calculate remediation rates, and identify regressions.

To verify resolved critical vulnerabilities, compare your previous and current security audit reports. This remediation verification process confirms whether previously identified critical issues are fixed, calculates the overall remediation rate, and highlights remaining open findings.

The main limitation of comparing security audit reports with structured Markdown is that accurate analysis strictly depends on structured Markdown input. Unstructured or inconsistently formatted audit findings will prevent accurate severity analysis, remediation rate calculation, and regression detection.