GitHub Stats Forge
The cards
Section titled “The cards”Contribution stats, the languages you write most, the repositories you contribute to and WakaTime coding time describe a person; a pinned repository and a pinned gist describe one thing they own; and two organization cards describe a whole account — what it owns, and what it has been doing lately. Every one takes the same colours, borders and themes, and each has a light and a dark version.
Four ways to draw one
Section titled “Four ways to draw one”Recommended
It renders your cards on a schedule and commits the SVGs, so nothing has to be up when someone reads your profile and a failure lands in a job log rather than in a broken image.
- Runs on a schedule
- Renders your cards
- Commits the SVGs
Try a card
Asks which card you want and which options it should take, then writes the SVG next to you. It is how you settle on a card before a workflow keeps it current.
Build on it
What both of those call. It reads no environment of its own, so the same code runs in an action, on a server and in a browser.
Host it
The one way that does need something up: a container image drawing cards from your own GitHub tokens the moment someone looks at one, with this site and the card builder inside it.
Every card on this site was rendered by the CLI from a saved configuration, so what you see is what the tool produces — not a screenshot.