How is this different from ESLint rules?
Most lint rules only flag obvious equality checks. Floating Point Validator analyzes expression context, variable origins, and math operations to rank true risk and provide practical epsilon suggestions.
Stop silent precision bugs before release
Visual floating-point comparison safety checker for production codebases
Scan TypeScript and JavaScript files for risky float equality checks, see severity-ranked findings, and get safe epsilon-based replacements with context-aware tolerance guidance.
Problem
Direct equality checks silently fail
`total === expected` can break when both values are mathematically equal but differ by a tiny binary rounding error.
Cost
Financial loss and flaky tests
Fintech reconciliation mismatches, ranking glitches in games, and scientific drift usually appear only after deployment.
Outcome
Safe refactors before merge
Engineers get concrete replacements using `Math.abs(a - b) <= epsilon` with explanations and severity scores.
Built for backend, data, and simulation teams
AST-powered detection across uploaded files and public GitHub repos
Severity model that prioritizes likely precision failures
Instant suggestions for safer epsilon-based comparisons
Configurable tolerance level per scan
Snippet viewer for pinpoint remediation
Cookie-based paid access for internal team rollout
Pricing
Simple plan for teams that cannot afford floating-point regressions.
Pro
$12/mo
- Unlimited scans
- File upload and repository analysis
- Severity-ranked remediation list
- Tolerance presets for finance and scientific code
FAQ
Can I scan private repositories?
The built-in GitHub scanner supports public repositories out of the box. Teams usually run the analyzer on uploaded files from CI artifacts for private code.
What epsilon should we use?
Start with 1e-8 for general engineering, 1e-6 for money-sensitive code, and 1e-10 for scientific workloads. You can tune this per analysis run.
How does access work after payment?
After Stripe checkout completes, the webhook records your purchase email. Use that email on the dashboard unlock form and we issue an access cookie for your browser.