GitHub Dev Card

Type a GitHub username, rip open a card pack, and get a FIFA-style dev card rated out of 99 — plus a roast, archetype, commit clock, and five more shareable readings. Free, no login.

9 vibe tools · one username

Rip the pack.

Your GitHub profile, pulled fresh and turned into a player card rated out of 99 — plus eight more readings you'll want to screenshot.

try · · or your own

Reads public GitHub data in your browser. Nothing is stored or uploaded.

{ }Dev CardSeason 26── tear here ──

About This Tool

GitHub Dev Card turns any public GitHub profile into a set of shareable, screenshot-ready readings — starting with a FIFA-style player card rated out of 99. Type a username, rip open the card pack, and the tool reads the public profile, repositories, and the last ~90 days of public activity through the GitHub REST API, entirely in your browser. Nothing is uploaded, stored, or logged — close the tab and it's gone.

How the rating works. The card maps six football attributes onto real developer signals: Pace is how often you ship (public events per week), Shooting is the stars your repositories have earned, Passing is pull-request activity and follower reach, Dribbling is language range across repos, Defense is how many of your repositories you still maintain, and Physical is years on GitHub plus consistency. The overall rating blends all six on a curve where 99 is deliberately unreachable — even the legends top out in the mid-nineties. Card tiers (bronze, silver, gold, and the holographic tier at 87+) follow the overall score.

Eight more readings from the same data. Because everything derives from three lightweight API reads, one scout unlocks the whole set: a stat-based roast with zero AI involved (every line is triggered by something real in the profile), a developer archetype (Night Owl, Weekend Warrior, Serial Starter…), an hour-by-weekday commit clock, a language-DNA strand, a head-to-head battle against any other username, a transfer-market valuation with a breaking-news card, a haiku assembled from actual commit messages, and a trophy cabinet of your most-starred work. Each panel exports as a PNG sized for social posts.

About rate limits. The tool uses GitHub's free unauthenticated API, which allows 60 requests per hour per network. One scout costs three requests, so you can rate roughly twenty cards an hour — results are cached in your browser for repeat views. If the limit runs out, the tool tells you exactly when it resets.

Pair it with the Code Screenshot Generator for sharing the code behind the card, the JSON to Profile Card tool for custom cards from your own data, or the Markdown Table to Image tool when a stats table tells the story better.

How It Compares

gitfut.com popularized the GitHub-stats-as-FIFA-card idea and does one thing beautifully — but it produces exactly one artifact per username. GitHub Wrapped-style year recaps only run once a year and most require signing in with your GitHub account. Profile README stat cards (github-readme-stats and friends) are static SVG badges designed to live in a README, not shareable social artifacts. FindUtils GitHub Dev Card generates nine different readings from a single username — card, roast, archetype, commit clock, language DNA, battle, market value, commit poetry, and trophies — with no login, no account access, and everything computed in your browser from public data. Every panel downloads as a PNG.

Tips

1
The rating only reads public activity — private-repo heroes will score lower than they deserve. Wear the bronze with irony.
2
The commit clock uses your device's local timezone; scout yourself from your usual machine for an honest picture.
3
Results are cached in your browser for 30 minutes, so tab-hopping between panels never re-spends the request budget.
4
High Defense with low Pace usually means a maintainer; high Pace with low Defense means a serial starter. The archetype tab will say it to your face.

Frequently asked questions

1

Where does my data go?

Nowhere. The tool calls GitHub's public API directly from your browser, computes everything locally, and keeps a short-lived cache in your browser storage. There's no login, no server-side processing, and no tracking of which usernames you scout.
2

Why is my rating lower than I expected?

The free GitHub API only exposes public data: public repos, public events from roughly the last 90 days, stars, and followers. Private-repo work is invisible to the rating, and long-past activity beyond the event window doesn't count toward Pace. It's a vibe check, not a performance review.
3

Can anyone get a 99 rating?

No — the overall score is computed on a curve where 99 is mathematically unreachable, the same way football rating systems keep their ceiling sacred. The holographic tier starts at 87, and even the most legendary profiles land in the mid-nineties.
4

Is the roast AI-generated?

No. Every roast line is a hand-written rule that only fires when something real in the profile triggers it — commits at 3 AM, a fork-to-original ratio that says 'collector', repos named todo-app that died the week they were born. If a line appears, the data earned it.
5

What does 'rate limit reached' mean and what do I do?

GitHub's free API allows 60 requests per hour per network, and one scout costs three. On a shared network (office, university) the budget can run out faster because everyone shares it. The tool shows exactly how many minutes until the limit resets — results you've already scouted stay available from the cache.
6

Why don't the numbers match my GitHub contribution graph?

The contribution graph counts commits across all repos including private ones, while this tool reads the public events feed, which covers roughly the last 90 days of public activity. They measure different things — the card is a public-persona snapshot, not a contribution audit.
7

Can I use the card image commercially or in my portfolio?

Yes. The exported PNG is rendered from public profile data and the tool's own design — use it in portfolios, slides, posts, or profiles. The avatar image belongs to the profile owner, so if you're sharing someone else's card, common courtesy applies.
8

How is the battle winner decided?

Both usernames are scored with the identical rating engine, stat by stat. Each of the six attributes is a round; win more rounds and you take the tie. If rounds split evenly, the higher overall rating wins — and if that's level too, it's declared a draw and honor is preserved.

Related Tools

Code Screenshot Generator

Developers

Json To Profile Card

Generate

Json To Social Card

Generate

Markdown Table To Image

Developers

Rate This Tool

0/1000

Get Weekly Tools

Suggest a Tool