Open Source Projects · head-to-head

Creative Commons Catalog vs GitHub Contribution Chart Generator

Creative Commons Catalog

Creative Commons's search catalog was handed off to WordPress.org and relaunched as Openverse; the old `api.creativecommons.engineering` host now 301-redirects to the current `api.openverse.org`. A live unauthenticated GET against `api.openverse.org/v1/images/` returned a 200 JSON result set with `Access-Control-Allow-Origin: *`, confirming keyless anonymous search still works today (rate-limited to 200 requests/day per IP), with an optional `/v1/auth_tokens/register/` OAuth2 client-registration endpoint (confirmed live, returning a 400 validation error rather than 404) for higher limits. The catalog itself and every indexed work are free to use under their respective open licenses.

GitHub Contribution Chart Generator

This is a keyless JSON API (not an image-rendering service, despite the name) with a single route, `/api/v1/{username}`, that returns a GitHub user's daily/yearly contribution counts — confirmed by inspecting the project's own source tree, which contains only one API file (`src/pages/api/v1/[username].js`); the actual chart image is drawn client-side from that JSON by a separate canvas library. A live unauthenticated GET returned a 200 JSON payload with no `Access-Control-Allow-Origin` header at all, correcting cors from "yes" to "no" (the header only appears on Vercel's default 404 page, not on the real route). Free and open-source, self-hostable on Vercel.

Creative Commons CatalogGitHub Contribution Chart Generator
AuthenticationNoneNone
Pricingfreefree
FormatsJSONJSON
CORSyesno
HTTPSYesYes

Creative Commons Catalog supports CORS, while GitHub Contribution Chart Generator doesn't — pick Creative Commons Catalog for direct browser calls.

More comparisons