i had the same problem and built something similar but with a different approach. greens (https://github.com/yuvrajangadsingh/greens) is a CLI that runs locally on your machine. it mirrors commit activity from your private/work repos to a personal repo via a cron job. no tokens shared with any third party, no web app, no account.

the tradeoff vs your approach is it only works going forward (can't backfill years of history), but nothing ever leaves your machine.

to answer your honest question #1: yes, this is a real problem. i posted about it on linkedin and the response was way bigger than i expected. lots of devs working at companies where all their output is invisible on their public profile.

GitHub allows you to show private contributions in its activity graph: https://docs.github.com/en/account-and-profile/how-tos/contr...

How does this site's home page not have a "what this looks like" anywhere?

Seven years... Where's yours?

// If there is an example and I can't find it, might as well not be there.

// If you won't show yours, why would I show mine?

undefined

3. How does anyone else know it hasn't been faked?

(e.g. someone could have written a cron-job or script to resubmit other people's work)

A finished product making money is better than a contribution graph that can be so easily faked that lots of GitHub users just do it for the fun of it.

In 2026, contribution graphs offer a very little representation of the current skills of a developer.