Freshness is explicit
Data refreshes once a day. Every report shows the exact time it was generated.
Definitions, freshness, transformations, and known limits for repository analytics. No invented precision and no visitor-level claims.
Bundled methodologyData refreshes once a day. Every report shows the exact time it was generated.
A missing day means no trustworthy observation was stored. Missing values are not silently converted into zero activity.
Reports contain repository-level aggregates only. They cannot identify individual visitors, cloners, or README viewers.
Metrics retain the vocabulary of their upstream source. Derived values are labeled as derived.
Repository page views reported by GitHub for each UTC day.
GitHub's daily estimate of distinct repository viewers.
Repository clone events reported by GitHub for each UTC day.
GitHub's daily estimate of distinct cloners.
Net star gains derived from daily repository snapshots. Trends begin when you start tracking a repository, because GitHub no longer shares historical star dates with apps.
Net fork gains derived from cumulative repository snapshots.
The repository watcher count from GitHub, excluding stars and social followers.
Downloads reported for release assets during the selected interval.
Downloads reported by the supported package registry during the selected interval.
Shows the value recorded in each reporting interval.
Adds each interval to the running total.
Rebases each selected repository to 100 at the beginning of the window for relative comparison.
Shows a trailing average across the selected number of days.
Unique counts are upstream estimates and should not be summed into a person-level total. A README view cannot be identified. Correlation between a release and a traffic change is context, not proof of conversion. Anomaly flags are deterministic observations, not forecasts.