Packagist vs UrlBae

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

Uptime · 30d
Uptime · 90d100%1.0%
Uptime · 30d100%0.0%
P50 · ms611158
P95 · ms9391158
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Packagist vs UrlBae: common questions

Which is more reliable, Packagist or UrlBae?

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

Which is faster, Packagist or UrlBae?

Packagist has the lower median latency in our checks — Packagist responds in 61 ms versus UrlBae at 1158 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 Packagist and UrlBae need an API key?

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

Can I call Packagist and UrlBae from the browser?

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

Are Packagist and UrlBae free for commercial use?

Packagist has unclear commercial terms, and UrlBae 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.