shipapis
StarSubmit an APISubmit API

ItsThisForThat vs npm Registry

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

APIItsThisForThatNEW—npm RegistryNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree (public registry)
Rate limitUnpublished (docs ask you not to hammer it)Unpublished (bulk scraping discouraged)
In directory since2026-07-052026-07-05
operationalpartialdownno data

ItsThisForThat vs npm Registry: common questions

Which is more reliable, ItsThisForThat or npm Registry?

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

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

Can I call ItsThisForThat and npm Registry from the browser?

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

Are ItsThisForThat and npm Registry free for commercial use?

ItsThisForThat 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.