shipapis
StarSubmit an APISubmit API

GitHub Contribution Chart Generator vs Shields

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

APIGitHub Contribution Chart GeneratorNEW—ShieldsNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (derived from public GitHub profile data)Unverified
Free tierFree — no keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GitHub Contribution Chart Generator vs Shields: common questions

Which is more reliable, GitHub Contribution Chart Generator or Shields?

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

Neither needs a paid key — GitHub Contribution Chart Generator is callable with no signup, and Shields is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call GitHub Contribution Chart Generator and Shields from the browser?

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

Are GitHub Contribution Chart Generator and Shields free for commercial use?

GitHub Contribution Chart Generator has unclear commercial terms, and Shields 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.