Migration assurance
Re-scan comparison: prove your migration is progressing
After you fix findings and re-scan, the comparison view diffs the two reports deterministically and classifies every finding as fixed, remaining, new, regressed or moved. It flags when the ruleset changed between scans so you interpret the diff correctly.
- Input: A baseline report and a current report
- Output: Fixed / remaining / new / regressed / moved counts and entries
- Method: Deterministic layered-fingerprint diff. No AI.
What it shows
A layered fingerprint matches findings across scans even when line numbers move, so a relocated finding reads as moved, not as fixed-plus-new. Regressions are surfaced explicitly.
Ruleset awareness
If the ruleset version changed between scans, the comparison says so, because some diffs then reflect updated detection rather than code changes.
Frequently asked questions
Is the diff deterministic?
Yes. The comparison is a deterministic fingerprint diff with no AI, so the same two reports always produce the same result.
Official sources
Last reviewed: 2026-07-02.
Open the interactive scanner: /app#/compare