This release focuses on making scan results easier to interpret, while tightening what gets shared when you publish results to the dashboard.
Clearer scan results
Checks can now explicitly report when they were skipped or inconclusive, instead of looking like a normal pass. This helps you quickly tell what was actually verified versus what could not be confirmed.
When you publish a scan, the summary now includes skipped and inconclusive counts so your dashboard history matches what the CLI saw.
Safer publishing and more reliable verification
Publishing applies stricter redaction boundaries so sensitive details stay local. Website URLs are reduced to their origin, and published data avoids including raw findings, subprocess output, paths, query strings, or secret values.
Several SEO-related checks now prioritize verifying deployed pages when production or staging URLs are configured, rather than relying on static hints. This includes checks like canonical URLs, language attributes, viewport metadata, structured data, and core SEO tags.
Email authentication checking is now based on an explicitly configured email-sending domain, instead of inferring it from website URLs. If that domain is not set, the check reports an inconclusive warning to avoid giving a false sense of coverage.