The board never lies. Every figure below is pulled from the GitHub API.
Developer metrics, read as a career record.
How to read the scorecard — every cricket term, and the GitHub field behind it
| Cricket | Developer metric | Source |
|---|---|---|
| Runs | Commit contributions | contributionsCollection.totalCommitContributions |
| Innings | Days with at least one contribution | contribution calendar |
| Matches | Repositories contributed to | totalRepositoryContributions |
| Highest score | Busiest single day | contribution calendar |
| Average | Runs ÷ innings | derived |
| Strike rate | Runs per 100 days since debut | derived |
| Centuries | Calendar months over 100 contributions | derived |
| Fifties | Calendar months at 50–99 contributions | derived |
| Fours | Pull requests opened | pullRequests.totalCount |
| Sixes | Releases published | releases.totalCount |
| Not out | Current daily streak | contribution calendar |
| Overs | Pull requests reviewed | totalPullRequestReviewContributions |
| Wickets | Pull requests merged | pullRequests(states: MERGED) |
| Runs conceded | Issues opened | issues.totalCount |
| Catches | Issues closed | issues(states: CLOSED) |
| Five-fors | Repositories with 50+ of your commits | history(author:) |
| Pace (kph) | Commit workload for that technology, relative to your busiest | derived |
Languages, weighted by the source bytes actually in your repositories.
Backend, DevOps, AI and cloud. Wickets and overs are counted from real repositories — a declared technology with no matches stays dimmed.
The stack that travels to every match.
Featured projects. Click any card to walk out to the middle.
 |
 |
 |
 |
Gold plinths are awarded credentials. Blue plinths are milestones the API is proving right now.
Twelve months of contributions, played out on the turf.
Generated from your numbers, so it changes as they do.
Close of play.
