OpenQR vs Packagist

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms112561
P95 · ms2851939
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenQR vs Packagist: common questions

Which is more reliable, OpenQR or Packagist?

Both are neck-and-neck — OpenQR and Packagist each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, OpenQR or Packagist?

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

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

Can I call OpenQR and Packagist from the browser?

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

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