Adoption methodology.

What we measure

• GitHub Popularity. Star count and watcher count as a proxy for installed base. Snapshot value, not velocity.
• GitHub Growth. Rate of new stars and contributors per snapshot. The velocity signal — the strongest leading indicator of where developer attention is moving.
• GitHub Contributors. Unique active contributors. Proxy for ecosystem depth, not just popularity — a tool with a thousand contributors is harder to replace than a tool with a thousand stars and one maintainer.

The adoption sources

How the Adoption Score is calculated

1. Map tool → public repository using the maintained tool catalog. Tools without a public repo are explicitly marked "Not applicable" rather than scored low.
2. Per-source normalize stars, growth, and contributors to 0–100 within the tool's category.
3. Weighted average across the three live adoption sources. Growth carries the heaviest weight because it's the leading indicator; popularity is the trailing indicator.
4. Decay older snapshots so historical popularity can't mask current decline.

Scope and guardrails

The Adoption Score only applies to tools with a public repository. Closed-source tools render the Adoption Signal as N/A — closed source, not a low score. This is deliberate; comparing closed-source tools on GitHub metrics is misleading.

All three adoption sources are framework-only today. Until ingestion is live, Adoption Scores, adoption winners, and adoption insights render as "Signal coming online" and never contribute to Consensus Scores, FutureFounder Score™, awards, reports, or insight rankings. See /sources for the current data state.