Repohistory

About Repohistory

Repohistory exists because of a single GitHub limitation: the traffic insights GitHub shows for a repository — views, unique visitors, clones, referring sites and popular content — are retained for only fourteen days and then discarded permanently. For an open-source maintainer that makes it impossible to answer the questions that actually matter, such as whether a release drove sustained traffic, whether a Hacker News mention had any tail, or whether clone volume has grown year over year. Repohistory connects to a repository and stores that traffic data continuously so the history keeps accumulating past the fourteen-day window, then presents it as charted analytics with data export. Because it is retention rather than measurement, the value compounds the earlier you start — data not captured during the GitHub window is gone and cannot be backfilled, which is an unusual property for an analytics tool and the strongest argument for adopting it before you need it. The paid tier adds a user or organization level traffic overview across every repository rather than one at a time, which is the view a maintainer with a portfolio of projects actually wants. The free tier tracks a single repository with the full feature set, including the extended history and export, so the paid upgrade is purely about repository count.

Key Features

Tags