Spirolo
Static analyzer that reads JavaScript and TypeScript test suites to find tests that can pass without proving anything, without running them.
At a Glance
Spirolo core CLI static analyzer for JavaScript and TypeScript test suites, licensed under Apache 2.0; currently in advisory alpha.
Engagement
Available On
Alternatives
Listed Nov 2026
About Spirolo
Spirolo is an open-source static analyzer for JavaScript and TypeScript test suites, published under the spirolo GitHub organization and distributed on npm as an advisory alpha (version 0.1.0-alpha.1). It reads tests, source code, runner configuration, setup files and CI workflows together and reports where a passing suite may prove nothing. It never executes the tests.
What It Is
Spirolo treats a test suite as one graph: test files, the modules they import, the runner configs that collect them and the CI workflows that run them. From that graph it reports tests that would pass even if the code under test were wrong. Analysis runs locally in a Rust binary with no network access, and the project says it does not run tests, mutation engines or coverage tools, and does not rewrite source files.
What It Checks
Findings are grouped into families: weak tests, merge gate, unused tests and flaky tests, plus a provisional Health score that ranks source modules where a new test would pay off first. The default report shows four advisory rules: absence-anchor, dead-skip, duplicate-test and fail-closed-setup. Experimental and dropped rules appear only with --all, and spirolo explain <rule> describes a rule's claim and measured status.
Trust and Gating
No rule is proven yet. A rule appears by default only once at least 15 of its sampled findings were decided and at least 80% were judged true, and those measurements are published. Findings report at info with exit code 0 unless a rule's severity is raised to warn or error in .spirolorc.jsonc, or a ratchet is used so CI fails only on new findings. The project says its own sampled run across 11 open-source projects produced 748 findings; these are advisory signals, not confirmed bugs.
Setup and Scope
Install with npm install -D spirolo@alpha and run npx spirolo check from the project root, with dependencies installed so imports resolve. Node 20 or newer is required, and a native binary is selected for Linux or macOS on x64 and arm64. It reads Jest, Vitest and Playwright suites with Testing Library, MSW and nock. Output is available as human-readable reports, JSON, SARIF, Markdown summaries or GitHub annotations for CI, and through MCP for agent clients. Cypress, Vue and Windows are outside the alpha.
Community Discussions
Be the first to start a conversation about Spirolo
Share your experience with Spirolo, ask questions, or help others learn from your insights.
Pricing
Open Source (Apache 2.0)
Spirolo core CLI static analyzer for JavaScript and TypeScript test suites, licensed under Apache 2.0; currently in advisory alpha.
- Apache 2.0 licensed native binary installed from npm
- Reads test suites without running tests
- Runs locally with no network access
- MCP tools for agents
- JSON and SARIF reports
Capabilities
Key Features
- Static analysis of JavaScript and TypeScript test suites without running tests
- Reads tests, imports, runner configs, setup files and CI workflows as one graph
- Weak test detection (absence-anchor)
- Merge gate checks (fail-closed-setup, dead-skip)
- Duplicate test detection
- Experimental flaky-candidate and untested-hotspot rules
- Provisional health score
- Public per-rule precision measurements and trust tiers
- Ratchet mode so CI fails only on new findings
- Configurable rule severity via .spirolorc.jsonc
- JSON, SARIF, Markdown and GitHub annotation output
- MCP tools for agent clients
- Local analysis with no network access
