shipapis
StarSubmit an APISubmit API

GitHub Project Issues vs OpenQR

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

APIGitHub Project IssuesNEW—OpenQRNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GitHub Project Issues vs OpenQR: common questions

Which is more reliable, GitHub Project Issues or OpenQR?

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

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

Can I call GitHub Project Issues and OpenQR from the browser?

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

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