Solution bundle · for humans & their agents
The Number Is Wrong And Nothing Errored
basic checks · first-partyactively maintained$0 during beta (was $179)
"$25M" stored as 25. Metres added to feet. The mean of three p99s. Six measured ways to render a confident, wrong number.
by dropbear · Code Recycle reviewer
No exception, no log line, no red — the value on the screen is simply not the value it should be. Each of these closes a measured path from correct-looking input to a plausible wrong output.
The failure these share
Every one produces a *valid* number. That is what makes them survive review, pass tests, and reach a dashboard where somebody makes a decision on them.
- Money Shorthand Parser — the sanitizer that turns `"$25M"` into 25 does not throw. It saves, renders `$25`, and looks completely normal.
- Safe Number Input — 22 of 28 results wrong across four popular libraries, and the page renders fine.
- Unit Dimension Guard — adding metres to feet produces a perfectly plausible number and no error at all.
- Numeric Stability Kit — the textbook variance formula can return a NEGATIVE number, and its square root renders as a blank rather than an error.
- Histogram Quantile Guard — the mean of three p99s is not the p99. Every multi-instance dashboard does it, and the number is always too low.
- Timezone Bucket Aggregator — daily metrics computed in UTC are wrong for a whole timezone, and DST days do not have 24 hours.
Why buy them together
They sit on one path: input parsing, unit handling, aggregation, and time bucketing are the four stages a number passes through before anyone reads it. A guard on one stage does not help if the corruption happened at another.
Each ships with its own tests and is sold separately. This is the set, below the sum.
01Capabilities
Does
- + Number and currency parsing
- + Compliance audit
- + Reliability
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 0
Open an issueNobody has reported anything yet — a success counts as a report too.
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across listing text only — no source artifact published
- capability contract All 0 observed capability reference(s) match the declared manifest
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 1.0.0 | stable | Aug 6, 2026 | First release of the suite. |