shipapis
StarSubmit an APISubmit API

Crates.io vs GitHub Project Issues

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

APICrates.ioHEALTHY94GitHub Project IssuesHEALTHY95
Uptime · 30d
Uptime · 90d100%99.44%
Uptime · 30d100%100%
P50 · ms279326
P95 · ms11541539
Authnonenone
CORSyesno
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

Crates.io vs GitHub Project Issues: common questions

Which is more reliable, Crates.io or GitHub Project Issues?

On our scheduled checks, Crates.io leads on measured uptime — Crates.io at 100% versus GitHub Project Issues at 99.44% 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, Crates.io or GitHub Project Issues?

Crates.io has the lower median latency in our checks — Crates.io responds in 279 ms versus GitHub Project Issues at 326 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 Crates.io and GitHub Project Issues need an API key?

Neither needs a paid key — Crates.io is callable with no signup, and GitHub Project Issues is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Crates.io and GitHub Project Issues from the browser?

Only Crates.io is browser-friendly — it returns CORS headers over HTTPS. GitHub Project Issues needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Crates.io and GitHub Project Issues free for commercial use?

Crates.io has unclear commercial terms, and GitHub Project Issues 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.