Download counter history
See how public GitHub release-asset counters change over time. These are file requests, not verified people, completed transfers or installations.
Loading observations...
The default range is the last three calendar months. Choose any UTC date range; the report shows only the history actually observed.
Observed request increases
Not yet measurable
Windows requests
Not yet measurable
Mac requests
Not yet measurable
Counter changes between observations
| Observed from | Observed through | Windows | Mac |
|---|
Latest cumulative counters
Existing counts at the first observation are a baseline, not new requests during your selected period.
| Asset | Release | Cumulative requests |
|---|
What these numbers can and cannot tell you
- Observations are scheduled every six hours. Recording starts with the first saved baseline; earlier daily or monthly totals cannot be reconstructed.
- Date-range totals use only complete intervals between saved observations inside your selected dates. Requests at uncovered start/end boundaries are not estimated.
- All recorded release asset IDs are retained in history. New versions contribute alongside older versions; missing assets, counter decreases and missing baselines are flagged rather than silently treated as zero traffic.
- Automated requests, repeat downloads and your own downloads may be included. Direct links to legacy ZIP/DMG files hosted on this website bypass GitHub counters.
- Cloudflare Web Analytics separately reports website and download-page visits. Choose this site and Exclude bots = Yes. Reports may be sampled and missed by privacy tools. Do not divide these different metrics to claim a verified conversion rate.
- No visitor identifier, cookie or desktop-app telemetry is added by this counter.
Raw dated observations (JSON) · Collection workflow · Privacy policy