The Problem
`total === expected` looks harmless until binary rounding turns equal numbers into near-equal failures or false matches.
Safe floating point comparison validator
float-comparison-checker scans your codebase for unsafe equality checks, recommends epsilon-safe replacements, and enforces precision discipline directly in CI.
`total === expected` looks harmless until binary rounding turns equal numbers into near-equal failures or false matches.
AST-based analyzers identify risky comparisons and output safe Math.abs(a - b) < EPSILON or math.isclose(...) fixes.
Fintech and data-heavy backends avoid flaky tests, reconciliation bugs, and costly postmortems with a lightweight guardrail.
Protect CI pipelines against silent float precision regressions.
Cancel anytime. Teams can scale to yearly plans through support after onboarding.
It detects direct float equality and inequality checks like ==, ===, !=, and !== when values look derived from decimals or math operations.
Yes. The CLI returns a non-zero exit code by default when issues are found, so GitHub Actions, CircleCI, and Buildkite can fail fast.
The analyzer uses AST context and float heuristics. You can scope extensions, adjust epsilon recommendations, and suppress expected exceptions in code review.
Teams with monetary calculations, experiment analytics, geospatial math, and scientific transforms where one rounding mismatch can produce bad decisions.