What expires after 14 days
GitHub's page-view and clone endpoints return totals plus daily or weekly points for the previous 14 days. The top referral sources and popular paths endpoints cover the same 14-day period and return only the leading ten entries.
Full clones and visitor information update hourly in GitHub's traffic graph. Referrers and popular content update daily. GitHub aligns this traffic data to UTC, so a reporting system should keep the original day boundary instead of shifting values into a viewer's local timezone.
How ongoing collection creates a longer record
RepoLogbook requests the current traffic window each day for repositories you explicitly track. It stores consolidated repository-day observations, retries missed work within the available window, and builds weekly and monthly rollups from those saved facts.
History begins when tracking begins. Daily collection protects future continuity; it is not historical backfill. A missing observation remains a limitation, and star trends likewise begin with the first successful collection.
- Free beta: two selected public repositories
- 180 days of visible history
- Daily traffic and star trend collection
- Repository-level aggregates only
Setup and repository access
Traffic endpoints are owner-oriented: GitHub says a person needs push access to view repository traffic, and GitHub App calls use read-only Administration permission for this data. Metadata access identifies the repositories made available to the installation.
During installation, choose only the public repositories you want the app to see. RepoLogbook uses short-lived installation tokens, never asks for a personal access token, and does not write repository contents.
- Install the GitHub App
- Choose repository access in GitHub
- Select which authorized repositories to track
- Review collection freshness in the Collection workspace
Security, deletion, and limitations
Uninstalling the GitHub App revokes future repository access. Account deletion stops collection, revokes sessions and public assets, and queues removal of tenant-attributable stored data. A minimal irreversible email suppression record may remain to honor unsubscribe, bounce, and complaint requirements.
RepoLogbook is independent and is not produced or endorsed by GitHub. Reports cannot identify people, distinguish every bot or automated request, or prove why a traffic change occurred.
Frequently asked questions
How long does GitHub keep repository traffic data?
GitHub's traffic views and clone endpoints return a daily or weekly breakdown for the previous 14 days. Referrers and popular content also describe the previous 14 days.
Can an app recover traffic that already expired?
No. Ongoing collection can preserve future observations, but it cannot recreate traffic days that disappeared before collection began.
Does RepoLogbook identify individual visitors?
No. GitHub supplies repository-level counts and aggregate unique estimates, not visitor identities.
Which repositories can be tracked during beta?
The current Free beta supports two public repositories selected through the GitHub App. Private repositories remain disabled.