npm Registry vs WakaTime

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree (public registry)Free public endpoints; personal data needs API key/OAuth
Rate limitUnpublished (bulk scraping discouraged)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

npm Registry vs WakaTime: common questions

Which is more reliable, npm Registry or WakaTime?

On our scheduled checks, WakaTime leads on measured uptime — npm Registry at —% versus WakaTime 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 npm Registry and WakaTime need an API key?

Neither needs a paid key — npm Registry is callable with no signup, and WakaTime is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call npm Registry and WakaTime from the browser?

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

Are npm Registry and WakaTime free for commercial use?

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