Numverify vs Packagist

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms44961
P95 · ms1488939
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Numverify vs Packagist: common questions

Which is more reliable, Numverify or Packagist?

Both are neck-and-neck — Numverify and Packagist each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Numverify or Packagist?

Packagist has the lower median latency in our checks — Numverify responds in 449 ms versus Packagist at 61 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Numverify and Packagist need an API key?

Packagist needs no key, while Numverify requires a free API key. If you want to start calling without signup, reach for Packagist first.

Can I call Numverify and Packagist from the browser?

Neither sends browser-friendly CORS headers reliably, so call Numverify and Packagist from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Numverify and Packagist free for commercial use?

Numverify has unclear commercial terms, and Packagist has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.