Packagist vs RSQ API
Same instrument, two spec sheets — measured, not claimed.
Packagist vs RSQ API: common questions
Which is more reliable, Packagist or RSQ API?
Both are neck-and-neck — Packagist and RSQ API 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 RSQ API?
Packagist has the lower median latency in our checks — Packagist responds in 61 ms versus RSQ API at 783 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 RSQ API need an API key?
Neither needs a paid key — Packagist is callable with no signup, and RSQ API is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call Packagist and RSQ API from the browser?
Neither sends browser-friendly CORS headers reliably, so call Packagist and RSQ API 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 RSQ API free for commercial use?
Packagist has unclear commercial terms, and RSQ API 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.