This release focuses on making scans more dependable in CI and day-to-day use. You will see clearer outcomes, safer handling of tricky repositories, and more accurate check results across common site setups.
Reliability and safety
Command failures now report more clearly and use consistent exit codes, so CI can tell the difference between a scan that found issues and a command that never ran due to invalid usage.
Cancellation is handled more cleanly during scans. A Ctrl-C is now reported as a cancellation (instead of a failed scan full of cancellation errors), and a second Ctrl-C can immediately stop a stuck scan.
Project file reading is now safer when scanning untrusted repositories. Preflight skips non-regular files and caps how much it reads from any single file, helping avoid hangs or runaway reads.
More accurate checks and smoother workflows
Initialization is safer when re-running setup. If a project already has an existing configuration, Preflight now asks before replacing it, and you can explicitly overwrite with preflight init --force.
Several checks are now less prone to false positives and better reflect real-world behavior. This includes improved handling for SPA catch-all routes, more accurate detection of custom 404 pages (excluding stock server defaults), and tighter matching for canonical and language signals.
Results published from scans now redact sensitive details more carefully for specific check messages, reducing the chance of leaking values in shared outputs.
Release downloads now include signed build provenance, and the documentation includes a simple verification command using gh attestation verify.