GitHub only keeps 14 days of traffic data. After that it's gone. Due to this, a lot of our questions remained unanswered over a long window.
— Was there a spike in clones last month, and where did it come from?
— Which docs pages are actually being read?
— How many people came to the repo over the last 3 months?
We were flying blind. Not the best way to maintain an open source repo.
So build zingg-stats — a small daily automation that runs three Python scripts every morning and posts everything to Slack:
→ GitHub traffic (views, clones, referrers) saved to CSV before the 14-day window closes
→ Charts showing trends over the last 3 months
→ Google Analytics summary from yesterday
We built it with Claude and kept it generic enough that any open source maintainer should be able to adapt it to their own project in an afternoon.
If you run an open source project and have the same blind spots, give it a try.
sonalgoyal•3h ago
— Was there a spike in clones last month, and where did it come from? — Which docs pages are actually being read? — How many people came to the repo over the last 3 months?
We were flying blind. Not the best way to maintain an open source repo.
So build zingg-stats — a small daily automation that runs three Python scripts every morning and posts everything to Slack:
→ GitHub traffic (views, clones, referrers) saved to CSV before the 14-day window closes → Charts showing trends over the last 3 months → Google Analytics summary from yesterday
We built it with Claude and kept it generic enough that any open source maintainer should be able to adapt it to their own project in an afternoon.
If you run an open source project and have the same blind spots, give it a try.