Verified
Telixon measures conformance with Google libphonenumber, performance, and payload size on every push. Each section names the method and the command that reproduces it.
Conformance
Section titled “Conformance”Thirteen of the fourteen PhoneNumber methods have a Google
libphonenumber counterpart; every one of them is compared against it. The oracle is version-matched, running Google’s own JavaScript source at
the exact commit the engine’s metadata was built from. Every mismatch it reports is a real
behavioral difference.
The gate’s full corpus compares the thirteen methods on 14,355 inputs each,
across all 245 regions, extension spellings included, while case coverage compares one number from
every distinct case the library can produce. Together they stand at 367,766 comparisons with zero
divergences. isValidForRegion is set-compared per case, with 692,513 region checks in the
case-coverage sweep alone. A 9,050-pair sweep grades matchPhoneNumbers against
Google’s isNumberMatch alongside them. The allowlist of accepted divergences is empty.
On top of the gate, every push runs a one-million-input parity sample. Weekly, the airtight proof enumerates the complete geographic input domain of 1,838,775,900 inputs, split across ten shards.
pnpm conformanceThe parity dashboard publishes every run.
Performance
Section titled “Performance”The benchmark measures parsing and query throughput, cold and warm, plus per-keystroke controller latency. Every library runs its built package, the same code a consumer installs. The reference baseline is the google-libphonenumber npm package, a third-party wrapper of Google’s port. Wall-time numbers depend on hardware, while the medians across the query surface land around an order of magnitude in Telixon’s favor; the dashboard publishes the per-method ratios. CodSpeed tracks the instrumented regressions.
pnpm benchThe benchmark dashboard publishes each run.
size-limit gates the entry sizes.
| Artifact | Measured | Budget |
|---|---|---|
@telixon/core Node entry |
23.69 kB brotli | 25 kB |
@telixon/core browser entry |
26.29 kB brotli | 28 kB |
@telixon/web-sdk |
3.92 kB brotli | 5 kB |
pnpm sizeThe engine tables ship outside these entries, loaded on demand by the async builds and embedded by the sync entry. The bundle report measures them from a real production build, chunk by chunk.