Reimagine your git contribution graph

There are 8,760 hours in 2025—how many of them have you spent coding?

247 users have racked up 4,053 hours of code across 55,048 commits. Join them to see your own contributions come to life.

Please welcome our newest member, adamoo00o0o

Generate your gitbox with:

Public + private commit history

Generate your gitbox from commits you've made on public and private repositories.

Requires read-only ‘Repository Contents’ permissions to read your commit history and estimate how many hours you've spent coding. Code is never accessed. Read more about trust.

Public commit history only

Generate your gitbox from commits you've made on public repositories only. No login required.

You can add private commit history to your profile page later if you want.

Don’t fancy either option? Email me your commit history and I’ll add it for you:

find . -type d -name ".git" -prune -exec sh -c 'repo=$(basename "$(dirname "{}")"); git -C "$(dirname "{}")" log --author="Jane Doe" --since="2024-01-01" --until="2024-12-31" --pretty=format:"%H %cI" | awk -v r="$repo" '\''{print r": "$1" "$2}'\''' \;

About gitbox

365 days of the year? Pah! Try 8,760 hours instead. Rectangular contribution graphs—who’s got the viewport for that? The humble and perfectly proportioned square is where it’s at. See the patterns in your coding habits: not just when you were working but on which repository:

Screenshot of the 2024 gitbox of /makeusabrew.

How it works

gitbox uses the GitHub API to access your commit history across all the repositories you grant it access to. It then estimates—very loosely—how many hours you've spent coding based on the commits you've made using a heuristic similar to git-hours, and colour-codes your contributions by repository. It looks really cool.

Disclaimer

gitbox is a bit of fun, not a timesheet. Hours are extrapolated from commit timestamps, and different habits will drastically affect accuracy. Squash merges, interactive rebases, cherry-picking, commit amending—all these things and more will skew the chronology. Please don’t take the numbers seriously.

In any case, hours do not equal output, nor does output equal outcome. Time spent doesn't correlate with value created. Do not use gitbox to judge anyone's productivity or worth—especially your own.

A note on trust

Since gitbox has to ask for set of permissions which includes read-only access to code as well as commit history, you need to know that I’m not going to abuse that access. Ideally, GitHub would let me request commit history without code (it doesn’t), or let you verify that gitbox only accesses commit history (it doesn’t—GitHub’s security logs are pretty thin on the ground).

So it comes down to trusting me. I have commit history on GitHub going back to 2009 across nearly 100 open source repositories. I’ve had the same Twitter account for 16 years and to the best of my knowledge I’ve never put anyone’s nose out of joint. I’ve run a consultancy business on and off since 2010 and most of my clients still like me.

I would much rather not have access to anything other than commit history, but the GitHub API doesn’t let me have one without the other. gitbox will not access any of your code, ever.