Hunter vs npm Registry

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree (public registry)
Rate limitUnpublishedUnpublished (bulk scraping discouraged)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Hunter vs npm Registry: common questions

Which is more reliable, Hunter or npm Registry?

On our scheduled checks, npm Registry leads on measured uptime — Hunter at —% versus npm Registry at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Hunter and npm Registry need an API key?

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

Can I call Hunter and npm Registry from the browser?

Only npm Registry is browser-friendly — it returns CORS headers over HTTPS. Hunter needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Hunter and npm Registry free for commercial use?

Hunter has unclear commercial terms, and npm Registry 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.