# Release Downloads Measure Channel Following Not Active Adoption Release-asset download counts measure activity in a distribution channel, not unique people, active installations, or retained use. Comparing several releases and accounting for how long each was current can estimate the audience following that channel, but calling that estimate “adoption” claims more than the data supports. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions This applies when software ships as attached GitHub Release assets. Automated downloads, repeat downloads, mirrors, and unequal release lifetimes remain confounders. Projects deployed directly from git produce no release-asset signal at all. ## Evidence > “These counts only cover attached release assets. … And a download is a download. It is not a unique human, not an active install, and not a heartbeat from a machine still running last month’s build.” The source recommends comparing several recent releases, adjusted for time current, as a range for people following the release channel rather than as an active-install count. ## Links - [[3. Resources/Permanent Notes/A Metric Is Vanity Only Against Your Own Outcome Data]] — extends: a release count becomes meaningful only after its relationship to the actual outcome is tested. - [[3. Resources/Permanent Notes/The Four Objectives Framework Replaces Vanity Metrics in DevRel]] — applies-in: release activity needs an explicit objective before it can support a program decision. - [[3. Resources/Permanent Notes/Default-On AI Activation Inflates Adoption Metrics at the Cost of Consent]] — contrasts: both separate an observable deployment event from evidence of chosen, retained use. - [[3. Resources/MOCs/Personal Knowledge Management MOC]] — applies-in: the MOC lists this note under Source evaluation and triage (added 2026-08-16). - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — applies-in: the MOC lists this note under Synthesis additions (2026-08-11 — consent and release evidence). ## Source - [[3. Resources/Readwise/Articles/What Visibility Do You Have When Releasing a Plugin Directly on GitHub]] — primary source and verbatim evidence.