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!!

Maker

Update: Repo-rter—the local-first GitHub traffic logger—now has E2EE cloud sync and OS Keychain support! (v0.4.5)

Hi everyone! A few months ago, I shared Repo-rter (v0.2.0)—a local-first desktop app built with Next.js and Tauri v2 that bypasses GitHub's annoying 14-day traffic history limit by caching views and clones locally on your machine.

Since then, the community feedback has been amazing. Over the last few major releases (v0.3.0 up to v0.4.5), we have completely overhauled the architecture to make it highly secure, robust, and truly decentralized.

Here is a summary of the major updates since v0.2.0:

💾 1. Native File Storage (Migrated from localStorage)

Initially, we stored traffic logs in WebView's localStorage. However, standard WebViews are prone to OS cache sweeps (e.g. macOS cache_delete or Windows Disk Cleanup) which could silently wipe out your history.

  • Update: We rewrote the persistence layer to write files directly to the OS App Data directory using native Rust file I/O. It's much faster, holds unlimited records, and is immune to browser cache purges.

🔒 2. Zero-Knowledge Cloud Sync (WebDAV + E2EE)

If you run Repo-rter on multiple machines (like a laptop and a desktop), you need a way to merge your logs. But we didn't want to host a centralized database or touch your credentials.

  • Update: We added WebDAV synchronization (compatible with Nextcloud, Synology NAS, etc.).

  • Security: Before sending anything over the network, data is encrypted on the frontend using AES-256-GCM with a key derived from a user-supplied password via PBKDF2 (100,000 iterations). Your cloud provider only sees encrypted gibberish.

🔑 3. Hardware-Level Security (OS Native Keychain)

We migrated sensitive credentials (your GitHub PAT, WebDAV password, and E2EE passphrase) out of localStorage plaintext files.

  • Update: Using the Rust keyring crate, we now store credentials directly in the host operating system's native secure storage (macOS Keychain, Windows Credential Manager, and Linux Secret Service).

  • Migration: On first startup, the app securely migrates legacy credentials, verifies they were written correctly by reading them back, and purges the plaintext files only after confirmation.

🧹 4. Custom Data Retention Policies

For developers tracking dozens of repositories who want to keep their disk space clean, we added configurable retention periods (30 days, 90 days, 1 year, or forever). The cleanup is handled directly by a lean, zero-dependency date filtering engine in Rust.

✨ 5. UI Polishing & Refinements

  • Restructured translation modules (multi-language support is now fully modular).

  • Implemented proper prefers-reduced-motion support across all CSS transitions and Framer Motion modal popups.

  • Refreshed the landing page with a responsive Bento grid design, smooth scroll-reveal effects, and self-hosted privacy-focused fonts.

Repo-rter is 100% free, open-source, and offline-first. Binaries are compiled and published for macOS, Windows, and Linux via GitHub Actions.