v0.0.189
Release notes
A new rule, reliability/js-errors, reports JavaScript errors and failed runtime requests on rendered pages, and says plainly when a page has no runtime data instead of counting it as a pass. The CLI now checks a site with the same user agent its crawl uses, and when a site resets connections from browser-like clients it falls back to squirrelscan's own user agent and tells you. squirrel feedback --json returns a receipt, and the agent setup prompt keeps the first audit free and asks before anything that spends credits or publishes.
Added
squirrel feedback --json(and the MCPsend_feedbacktool) now returns areceiptid once the API accepts the feedback, and stores it with the entry so the team can find it. The agent setup prompt also gets a failure-report step (#4951).- New cloud-only rule
reliability/js-errors: reports uncaught JavaScript exceptions, framework hydration mismatches, first-partyconsole.errormessages and runtime requests that fail after load (5xx or 404), as seen by the cloud render. Findings are grouped across the site by message and source file with the page count. 401 and 403 from the site's own API, requests the renderer blocks or aborts,ResizeObserver loopmessages, CSP violations and WAF challenge pages are not reported. A local or--httpaudit lists it among the cloud checks that did not run. It reads a new optionalruntimeblock on a render result, which the cloud renderer does not record yet. A page with no runtime data is a coded gap,runtime-not-recorded, listed under Not checked: until the renderer records it the rule is skipped, and once it does, a pass needs runtime data from every page judged. (#704)
Fixed
- The audit no longer dies on sites that reset browser-like clients. The reachability probe now sends
[crawler] user_agent(and drops Chrome client hints for non-Chrome agents), and when a connection reset hits the default browser agent it retries once as the honestSquirrelScan/...agent and crawls as that agent, saying so in one line and in the report (userAgentFallback, JSON schema 1.29). A site that resets every client now reports "connection reset by the site: it may block browser-like clients" with the fix. (#2140)
Docs
- The agent setup prompt now runs the first audit with
--offline --level quickwhatever the sign-in state, checkssquirrel auth statusfirst, asks for consent before credit spend, publishing or recurring audits, never passes--yes, preserves an existing setup, and ends with a sanitized failure report and the exact next step (#4949, #4950, #4951).
Update to this version
squirrelscan will auto-update, or run this command to update now.