GitHub achievements, without the guessing
Your badges.
Mapped.
GitHub hides the rules. Badge Hunt reads the public profile, counts the work behind each badge, and tells you the smallest useful next step. No account, no token required.
Reading public data
Opening the profile…
Start here
One username.
One honest read.
No sign-in, no token, no dashboard. Just the public trail: repos, stars, merged pull requests, and the badges they unlock.
- 01Enter a handle
Any public GitHub account.
- 02Read the counts
Merged PRs and owned-repo stars.
- 03Take the next step
One small, real action.
The wall
What you've earned
The counts
How close you are
Tiers are based on publicly documented thresholds. Unpublished rules are marked approximate.
The next move
One useful step
A badge is a side effect of useful work. Start with the smallest action that moves a real count.
Badge wall not detected? Paste your profile HTML
GitHub does not expose achievements through its API. If the public reader is blocked, open your profile's achievements tab, view source, and paste the HTML here. It is parsed locally and never uploaded.
The field guide
Seven badges.
Honest rules.
GitHub publishes some thresholds and keeps others close. Where a rule is approximate, this page says so instead of inventing a number.
How it works
Public data in.
A plan out.
Badge Hunt never asks for a password or stores a token. It reads your public profile, counts your public repositories, and searches public pull requests. The badge wall is the only fragile part: GitHub has no badge API, so the page tries a reader and falls back to your pasted HTML.
Read the CLI source- 01
Enter a username
No sign-in. Public profile, public repos, public PRs.
- 02
See the real counts
Merged pull requests, owned-repo stars, and the tiers they unlock.
- 03
Take one step
A short, specific next action instead of a wall of vague advice.