Skip to main content
ReleasesBeta

v0.0.190-beta.1

Release notes

This release is signed with the squirrelscan release key, key id 3d10cf3775665622, instead of a GitHub attestation. If you are logged in to gh and on 0.0.189 or older, run the install one-liner once (curl -fsSL https://install.squirrelscan.com | bash), or run env -u GH_TOKEN -u GITHUB_TOKEN GH_CONFIG_DIR=$(mktemp -d) squirrel self update, because older CLIs only accept GitHub attestations. The token variables are unset because either one would still authenticate gh. Everyone else is unaffected. Signed installs on Linux need openssl or a logged-in gh; the installer adds openssl itself on Alpine when run as root. npm has no provenance attestation on this release.

Added

  • squirrel audit --target-url accepts --compare-url (repeatable): a comparison set fetched once next to the targets, so content/duplicate-description and crawl/schema-noindex-conflict run over those pages instead of skipping with targeted-run. Every other site rule is reported as not checked. (#2096)

Changed

  • A targeted audit (squirrel audit --target-url) now runs the site rules that can be judged from the listed pages alone: links/broken-links, links/broken-anchors and links/broken-external-links report broken links on the listed pages, security/leaked-secrets scans those pages and the scripts they load, and security/csp, security/hsts and security/x-frame-options judge each listed page's own response headers, each finding naming the pages it was read from. The links on the listed pages are status-checked again, each target once and nothing else: the internal link check sends its HEAD control to a listed page instead of the start URL, and external link checks follow the run's level and --external-links / --no-external-links (the note that --external-links is ignored is gone, and meta.auditLevel.settings.externalLinks is the run's real setting). Rules that need the whole site (orphan pages, sitemap coverage, duplicates across pages) still skip with targeted-run. squirrel report --diff lists a site finding that names no page as not compared, with the new reason targeted-run, instead of counting it fixed after a targeted run. The scan line now reads "rules that need the whole site were not run". (#1778)
  • Correction to an earlier release note: the rule cache adds under 3% of CPU time on a cold run for typical sites (measured at +2.2% on squirrelscan.com and +0.6% on docs.squirrelscan.com), rather than the earlier cost being gone entirely. Very large pages are still being measured in #2206. (#1971)
  • security/supabase-rls waives an intentionally public table by its bare name: [[ignore]] with items = ["posts"] waives the posts table in every project. Each finding item is now labelled with the table name alone, with the row count beside it, and the fail message no longer lists table names, so a waived table no longer appears in it (#2103)
  • security/supabase-rls now probes up to 30 tables per Supabase project and 40 per audit (was 8 and 10), picks them in a fixed name order so the same site probes the same tables on every run, and says how many tables were checked and how many were left unchecked in a not-checked result and in a fail that did not reach every table (#2104)
  • a11y/paste-inputs now reports paste blocking on password and one-time-code fields only (type="password", or autocomplete of current-password, new-password or one-time-code) and maps to WCAG 2.2 success criterion 3.3.8 Accessible Authentication (Minimum), so --wcag-level AA keeps it. Paste, copy or cut blocking on other fields, and copy or cut blocking on password fields, is no longer reported. (#2106)
  • crawl/server-errors now reports each 5xx page as its own finding, so findings store, compare and resolve per page: a page that recovers resolves while other pages still fail, and a page the crawl did not fetch keeps its open finding (#2130).
  • Team is now a flat plan: $89 a month or $890 a year for 15,000 pooled credits, with unlimited members and no seat charge. Per-seat Team subscriptions keep their price, seats and credits (#2148).

Fixed

  • A leaking current-user endpoint such as /api/me is now always reported exactly once. security/unauthenticated-api reports every endpoint it finds, and squirrel keeps one finding per endpoint after the site rules finish: the security/auth-endpoint-disclosure finding when that rule reported the endpoint, otherwise the security/unauthenticated-api one. Before, an endpoint handed to security/auth-endpoint-disclosure lost its finding when that rule threw an error or ran past its time budget. (#2082) For JSON consumers: the deferredToAuth detail on the security/unauthenticated-api clean row is replaced by reportedBy and reportedElsewhere.
  • A password, password hash or secret field that both security/json-sensitive-fields and security/auth-endpoint-disclosure find on a current-user or session endpoint such as /api/account is now reported once, by security/auth-endpoint-disclosure, and the endpoint is requested once per audit. Each rule reports on its own, and after the site rules finish squirrel drops only the overlapping field from security/json-sensitive-fields, which keeps its other fields, such as card numbers and access tokens. (#2083)
  • Console output: correct singular counts ("1 error", "1 warning"), the analyze Config line printed above the spinner instead of onto it, squirrel entities listing every entity the "no @id" count includes with unnamed entities printed once, and the --probe aggressive hint shown once in the exposed files note (#2086).
  • links/anchor-mismatch no longer flags links on translated stores: inflected anchor words ("Sadler" for "cykelsadel"), trailing counts ("Shoes (15)") and locale prefixes in the target path ("/da-dk/") are matched correctly (#2092).
  • Fixed the date column in the squirrel report list running into the Pages column. (#2095)
  • Re-audits that crawl only part of a site no longer count a check that was skipped on a carried-over page (for example perf/ttfb with no timing data) as a pass: the page row records what its last crawl could not evaluate, in the cloud and in the CLI's local store, so the carried page scores as it did in the full audit (#2099).
  • squirrel report --input now keeps meta.partialAudit from the saved report and publishes with it, so a partial audit is no longer republished as complete. (#2102)
  • a11y/color-contrast now holds large text (18pt, or 14pt bold) to the WCAG 3:1 ratio instead of 4.5:1, so large headings and buttons are no longer flagged when they pass (#2105).
  • a11y/reduced-motion counts a reduced-motion rule as handling only for the selectors it covers, or for the whole page when it is a global reset (*, html, body, :root), so a library stylesheet such as Font Awesome 6 no longer hides a page's own motion; a motion library's own reduce rule ([data-aos], .animate__animated, .animated) still handles that library. Matching is by element, not selector text, so Tailwind's motion-reduce:animate-none on an animate-spin element and animate.css infinite animations covered by the library's reduce rule no longer warn, and a reduce rule for .Spin no longer clears .spin (#2111)
  • The a11y/zoom-disabled rule page and solution now say WCAG 1.4.4 requires 200% text resize and that the maximum-scale cutoff of 5 is the Lighthouse threshold. Rules with no WCAG criterion can now list related criteria as links on their rule page. (#2115)
  • Quick crawls now fetch the start URL when the sitemap lists it past maxPages, so home-page-unreachable no longer fires falsely. (#2127)
  • Rules near-duplicate, conversion-path and commerce-readiness report a coded gap (or keep a stored finding open) for input they did not fully check (#2134)
  • squirrel entities no longer fails or bloats on sites with very large entity maps: stored references per page and edges per source are capped at 1000, and a corrupt references row is skipped with a warning instead of aborting the command (#2135).
  • An audit whose config [rules] selection plus the WCAG level leaves zero rules to run is now refused before the crawl starts, instead of crawling the site and reporting an empty audit (#2110).
  • Local incremental re-audit totals and score now count carried findings in the full audit's check units. (#2159)
  • A sourced install.sh no longer sends failure reports, and a report with no message names what failed. Test harnesses and wrappers that source the script were reporting made-up failures as real install failures. A failure with no message now says which command failed, on which line, how the script was run and which bash ran it, and a curl exit code is only blamed on curl when a request was made (repo#5020).
  • install.sh now provides openssl on Alpine/musl (as root, with apk, next to libstdc++), so signed releases install on a bare Alpine image. On other Linux systems without openssl or a logged-in gh, the signed-release error names the fix (apt-get install -y openssl, dnf install openssl or apk add openssl, the line for your distro first). It never runs a package manager for you outside Alpine.

Security

  • install.sh, install.ps1 and squirrel self update accept a release signed by a pinned squirrelscan release key (ECDSA P-256, checked with openssl, .NET and WebCrypto) as well as one with a GitHub build attestation. A signature from an unpinned or revoked key, or one that does not verify, stops the install even if an attestation would pass. From first_signed_version up, sha256 alone is never accepted: a missing .sig with no verifiable attestation is a hard failure, with or without gh. The current key, id 3d10cf3775665622, is pinned, and this release is the first one signed with it (docs) (squirrelscan/repo#5032)

Docs

  • The squirrel report help says issues are available in squirrelscan cloud, and the MCP docs state that the old issue fields rule_id, occurrences and affected_pages are kept with no removal planned, with covered_findings as their replacement (#2031)
  • The agent skills served over MCP (the io.modelcontextprotocol/skills extension of squirrel mcp and the hosted server) now point firewall and connection reset troubleshooting at the new firewall guide, and carry squirrelscan 2.3 (#2141).
  • A new guide, Firewalls, bot protection and custom headers, shows each firewall, WAF, access gateway and bot protection exception for cloud, CLI and MCP audits side by side, with header scoping and the fix for sites that reset browser-like clients (#2141).
  • Docs prices no longer render as LaTeX math on the cloud team, credits, CLI credits and FAQ pages, and make validate now fails on unescaped currency amounts (#2204)

npm: this version is published to npm without provenance. It was built off GitHub Actions, and npm provenance needs a GitHub OIDC identity. The binaries carry the squirrelscan release-key signature instead.

If you are logged in to the GitHub CLI (gh), squirrel self update fails once for this release, because older squirrel versions expect a GitHub attestation. Re-run the install one-liner once (curl -fsSL https://install.squirrelscan.com | bash, or on Windows iwr -useb https://install.squirrelscan.com/install.ps1 | iex); updates work again after that.

Signed with the squirrelscan release key 3d10cf3775665622: every asset has a .sig (DER ECDSA P-256 over SHA-256), verify with openssl dgst -sha256 -verify.

Update to this version

squirrelscan will auto-update, or run this command to update now.

Downloads

macOS

Your platform
Apple Silicon (M-series chip)
squirrel-0.0.190-beta.1-darwin-arm64, 105.4 MB
Download
Intel
squirrel-0.0.190-beta.1-darwin-x64, 114.0 MB
Download

Linux

x64 (glibc)
squirrel-0.0.190-beta.1-linux-x64, 124.3 MB
Download
ARM64 (glibc)
squirrel-0.0.190-beta.1-linux-arm64, 124.4 MB
Download
x64 (musl/Alpine)
squirrel-0.0.190-beta.1-linux-x64-musl, 118.1 MB
Download
ARM64 (musl/Alpine)
squirrel-0.0.190-beta.1-linux-arm64-musl, 117.1 MB
Download

Windows

x64 (Intel/AMD)
squirrel-0.0.190-beta.1-windows-x64.exe, 130.1 MB
Download

View this release on GitHub

Audit your site in one command

SEO, performance, security, accessibility and agent experience issues, with exact fixes for your coding agent.

Or install it yourself

No account needed for the CLI. Cloud audits include free monthly credits.