Reimagine your git contribution graph
There are 8,760 hours in 2026—how many of them have you spent coding?
394 users racked up 14,139 hours of code across 173,159 commits. Browse a few of them below.
Please welcome our newest member, johnd-creator
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:
How it works
gitbox used the GitHub API to read your commit history across all the repositories you granted it access to. It then estimated—very loosely—how many hours you'd spent coding based on the commits you'd 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
gitbox no longer has access to GitHub. Its tokens are revoked, and it can’t read repository contents any more—which is what commit history needed.
Because gitbox had to ask for a set of permissions which included read-only access to code as well as commit history, you needed to know I wasn’t going to abuse that access. Ideally, GitHub would have let me request commit history without code (it doesn’t), or let you verify that gitbox only accessed commit history (it doesn’t—GitHub’s security logs are pretty thin on the ground).
So it came 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 had access to anything other than commit history, but the GitHub API didn’t let me have one without the other. gitbox never accessed anyone’s code.