Packagist vs Scrnify

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms61927
P95 · ms9391742
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 Scrnify: common questions

Which is more reliable, Packagist or Scrnify?

Both are neck-and-neck — Packagist and Scrnify 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, Packagist or Scrnify?

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

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

Can I call Packagist and Scrnify from the browser?

Neither sends browser-friendly CORS headers reliably, so call Packagist and Scrnify 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 Scrnify free for commercial use?

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