shipapis
StarSubmit an APISubmit API

IPLocate vs Packagist

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

APIIPLocateNEW—PackagistNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPLocate vs Packagist: common questions

Which is more reliable, IPLocate or Packagist?

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

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

Can I call IPLocate and Packagist from the browser?

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

Are IPLocate and Packagist free for commercial use?

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