Working · 2024-01SecondaryAcquisitionCommunity

Do not treat GitHub stars as adoption

Stars correlate weakly with downloads, depending on ecosystem.

Claim and evidence

The claimOur results reveal a weak relationship between GitHub Stars and download numbers.

PHP/Ruby/JS registries · ndss-symposium.org · undated

What the numbers show

No published number for this tactic has passed our word-for-word check yet, so there is no chart.

Why it works

Diagram, not data
Measure open-sourceadoptionDownloads anddeploymentsStar count aloneStars as a visibilitysignal
Measure open-source adoptionDownloads anddeploymentsStar countaloneStars as a visibility signal

Authors found a weak relationship between stars and downloads; deployments correlate better.

How to run it

  1. Track downloads/deployments, not just stars
  2. Compare per ecosystem
  3. Treat stars as visibility

Ways to run it

Design options to test, not promised results.

  1. Option AAdoption dashboard

    Track registry downloads and deployments next to stars, so visibility and usage are not confused.

  2. Option BPer-ecosystem baselines

    Compare numbers within one package ecosystem, since the star-download link varies by ecosystem.

Dated examples

  1. 2024

    PHP/Ruby/JS registries

    926K data points across three ecosystems.

    “Our results reveal a weak relationship between GitHub Stars and download numbers.”
    ✓ quote checked word-for-word on the page

    ndss-symposium.org · undated

Does it still work?

Workingas of 2024-01

Workshop paper; date inferred from filename only. source

Risks

  • Ecosystem differences

Sources

  1. ndss-symposium.org · NDSS MADWeb · Simon Koch, David Klein, Martin Johns · undated
    “Our results reveal a weak relationship between GitHub Stars and download numbers.”
    ✓ quote checked word-for-word on the page

Change log

  • 2026-11-20 — harvest v0.1 (referral-loops)