What started as a tool for Go modules just became something much bigger.
The Big Idea
GoBadge started with three endpoints — stars, imports, imported-by. Useful if you write Go. Not so useful if you don't.
Today that changes.
The new dynamic endpoint lets you turn any JSON API into a badge. GitHub stars, npm downloads, Docker pulls, your own metrics API — if it speaks JSON, it gets a badge.
https://gobadge.vercel.app/api/dynamic?url=https://api.github.com/repos/gin-gonic/gin&value=stargazers_count&label=Stars
That's it. One URL pattern, infinite data sources.
What Changed
GoBadge went from three hardcoded integrations to an open-ended system. You're no longer limited to the endpoints I built — you can badge-ify anything:
- GitHub — stars, forks, issues, license, any field
- npm / PyPI / Crates.io — downloads, versions, dependents
- Docker Hub — pull counts
- Your own API — internal metrics, dashboard data, anything
What You Can Do With It
Single value from any API

Multiple values in one badge

Nested JSON with dot notation

Any color you want
?color=ff6600
Parameters
| Param | What it does |
|---|---|
url |
HTTPS JSON endpoint |
value |
Key to extract (repeat for multiple values, use dots for nested keys) |
label |
Text on the left side |
color |
Name or hex (e.g. ff6600) |
sep |
Separator between values |
Try It
Drop this in your README (replace user/repo with any GitHub repo):

Or visit gobadge.vercel.app to play with the demo.
This is GoBadge v2. One badge service. Every data source.
Top comments (0)