The problem this prevents
Most teams discover floating-point equality bugs after deployment, when they are hardest to reproduce and most expensive to patch.
Financial drift in production
A float equality check that passes in staging can silently fail in production and skew balances, payouts, or settlement totals.
Scientific and analytics instability
Comparison logic around simulation outputs, scoring systems, and thresholds becomes non-deterministic when values differ by tiny rounding artifacts.
Flaky tests and release delays
Teams waste time chasing random CI failures caused by direct equality checks between computed floating-point values.
How it works
Upload files or scan public GitHub repos, review flagged comparisons, and apply safer numerical checks with clear fix previews.
AST-powered unsafe comparison detection
The analyzer parses JS/TS syntax and flags risky `==`, `===`, `!=`, and `!==` checks where either side is likely a floating-point value.
One-click epsilon fix suggestions
Every finding includes a concrete replacement using epsilon-based comparison logic tuned for common money and ratio workflows.
Ready for IDE and CI pipelines
Run scans before merge, enforce fail-on-risk policies, and expose a webhook endpoint to sync paid access with checkout events.
Built for teams burned by precision bugs
Ideal for fintech backends, scientific tooling, analytics platforms, and data-heavy services where numeric correctness is a release blocker.
The scanner ships value immediately: run it during code review and CI to stop exact-equality float checks before they merge.
For $5/month, you get continuous access to the analyzer dashboard, recommendations, and pipeline guidance tailored for production engineering teams.
Go to dashboard$5/month
Built for engineers shipping money movement, forecasting, scoring, and numerical APIs.
- Scan local files, snippets, and public GitHub repositories
- AST-level floating-point equality detection for JS/TS code
- Actionable epsilon-based code replacements
- Webhook + CLI guidance for CI/CD enforcement
- Monthly precision-risk report inside your dashboard
FAQ
What languages are supported right now?
The scanner supports JavaScript and TypeScript files (.js, .jsx, .ts, .tsx, .mjs, .cjs) with AST parsing and syntax fallbacks for resilience.
Can I analyze a GitHub repository without cloning it locally?
Yes. Paste a public GitHub repository URL and the dashboard fetches and scans source files directly through the GitHub API.
How is access controlled after purchase?
After Stripe checkout completes, the webhook records the purchase and the dashboard issues a secure cookie so only paid users can run analyses.
Will this replace code review for numerical logic?
No. It removes a high-frequency class of precision mistakes so review time can focus on business logic and domain edge cases.