How GitHub release download counts work

GitHub exposes a download_count value for uploaded release assets. GRA Release Radar uses those public asset counters to build maintainer-facing reports. The data is useful for understanding installer, binary, checksum, archive, and package adoption across public releases.

What is counted

Uploaded release assets are counted by GitHub as release assets. Examples include installers, binaries, archives, checksums, package bundles, and platform-specific artifacts attached to a GitHub release.

What is not counted

GitHub source archive zip and tarball downloads are not exposed through release asset counters. GRA does not estimate or invent those values.

Rate limits

GRA runs in the browser, so unauthenticated GitHub API calls share the user's network quota. A user-supplied GitHub token can raise the quota, but GitHub primary and secondary limits still apply. Agents should read the error guide before retrying.

Using the report

Use the platform, architecture, file type, cadence, and anomaly views to decide whether package names are clear, whether older platforms are still used, and whether a release created unusual demand.