Packagist vs PyPI

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnoyes
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

Packagist vs PyPI: common questions

Which is more reliable, Packagist or PyPI?

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

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

Can I call Packagist and PyPI from the browser?

Only PyPI 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 Packagist and PyPI free for commercial use?

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