Repo-rter
A local-first app to keep your GitHub traffic history.
Start new thread

Repo-rter - A local-first app to keep your GitHub traffic history.

by•
GitHub deletes your repository traffic data after 14 days. Repo-rter solves this by caching your data locally. Track views, clones, and release downloads forever with a privacy-first, lightweight Tauri app.

Add a comment

Replies

Best
Maker
📌
Hi Product Hunt community! 👋 I'm the maker of Repo-rter. As an open-source maintainer, I always wanted to keep my repository's traffic stats, but GitHub's native 14-day limit was incredibly frustrating. I didn't want to pay for a SaaS subscription just for basic traffic storage, so I spent the last few weeks building a local-first alternative. Repo-rter stores your views, clones, and release downloads permanently on your machine. Everything runs locally, so your GitHub token is 100% private. I'd love to hear your feedback, thoughts, or feature requests. Thank you so much for checking it out! ⭐️
💡 Bright idea

One thing that would make this way more useful for me is the ability to set a custom retention period for the cached data, or maybe an auto-purge option after X days. Some folks might want to keep everything forever for trend analysis, while others probably care more about keeping their local storage lean. Either way, giving users control over that would be a nice touch.

Maker

 
Thanks for the feedback, Kamile!
That's a very reasonable suggestion.
Now that we've migrated the database to local physical JSON files in our latest v0.4.0 release, we have much more control over the cache.
Adding a "Retention Policy" setting (e.g., Keep Forever, 3 Months, 1 Year) with auto-purge logic is a fantastic idea to keep local storage lean.
I've added this to our official roadmap and will work on it in the next update!
Thank you!

💡 Bright idea

Keeping the data locally is great, but what about syncing it across machines when devs work from a laptop and a desktop. Could you add an optional encrypted sync through something like a personal S3 bucket or WebDAV. That way the history stays truly portable without sending it through your own servers.

Maker

 

Thanks for the great idea, Cuma!

Syncing across multiple machines is indeed a common requirement.

In our latest v0.4.0 update, we just released a manual JSON Backup Import/Export feature so you can easily move your history.

However, having an automated, encrypted sync option using personal WebDAV or S3 is an excellent next step to keep it completely decentralized and private.

I'll research this and add it to our roadmap!

Thank you!!

💡 Bright idea

Lost my GitHub traffic data once after waiting too long to check, so this immediately feels useful. Love that it runs locally with Tauri, no sketchy cloud sync involved.

Maker

 

Thank you so much, Muharrem!

I built this exactly because I was in your shoes and got tired of losing my stats.

Keeping everything local was the top priority to ensure absolute privacy and lightweight performance (thanks to Tauri!).

If you have any feature ideas or feedback as you use it, feel free to let me know!!