Definitions

Distinct developers with at least one qualifying contribution in the period. A quarter counts distinct developers active in at least one of its months; it is never the sum of its months. An observed minimum, not a developer count.

Observed minimum: a floor over the attributed cohort, never a totalUnit: CountSource: Public commit dataFeature F1

Distinct non-fork public repositories receiving at least one qualifying contribution from an attributed developer in the period.

Observed minimum: a floor over the attributed cohort, never a totalUnit: CountSource: Public commit dataFeature F1

Total distinct developer-dates with at least one qualifying contribution. A developer contributing on 30 separate days contributes 30 contribution days.

A total over the observed cohort, which is itself a floor for the countryUnit: DaysSource: Public commit dataFeature F1

Qualifying commits: original code commits authored by the developer, in a non-fork public repository, excluding merge commits and bots.

A total over the observed cohort, which is itself a floor for the countryUnit: CountSource: Public commit dataFeature F1

The difference between the expanding-roster series and the cohort-locked series. This is growth attributable to finding more developers rather than to developers becoming more active, published so the two cannot be confused.

A derived difference between two published seriesUnit: CountSource: Derived from published seriesFeature F2

Of the developers active in the previous quarter, the share also active in this one. A ratio within the observed cohort, so it is not an observed minimum.

A ratio within the observed cohort; not a minimum of anythingUnit: RateSource: Derived from published seriesFeature F7

The share of active developers who contributed to two or more chains in the period. A ratio within the observed cohort.

A ratio within the observed cohort; not a minimum of anythingUnit: RateSource: Public commit dataFeature F8

Of ALL active developers in the source dataset worldwide, the share placed in any country. It is not a country's coverage rate: developers with no location cannot be placed anywhere, so how many of them are in a given country cannot be observed. Every country figure therefore counts only placed developers and is an observed minimum.

A ratio within the observed cohort; not a minimum of anythingUnit: RateSource: Derived from published seriesFeature F9

Total GitHub accounts attributed to the country by the GitHub Innovation Graph. An EXTERNAL TOTAL on a different basis: it counts accounts rather than active open-source contributors, includes inactive accounts, and GitHub's own documentation is inconsistent about whether it derives from self-reported location or IP. Shown as context for scale, never as our denominator.

An external total on a different basis, shown for scale onlyUnit: CountSource: GitHub Innovation GraphFeature F10

Electric Capital's figure from Open Dev Data (CC BY 4.0), the same data developerreport.com draws. A 28-day rolling count: developers with at least one commit in the 28 days ending that day. Electric Capital's total covers every ecosystem in its crypto taxonomy.

An external total on a different basis, shown for scale onlyUnit: CountSource: Public commit data

Electric Capital's figure from Open Dev Data (CC BY 4.0), the same data developerreport.com draws. A 28-day rolling count: developers with at least one commit in the 28 days ending that day. Developers who, in that window, contributed only to one chain's ecosystem, or to a first-party organisation of it (Electric Capital's "exclusive").

An external total on a different basis, shown for scale onlyUnit: CountSource: Public commit data

Electric Capital's figure from Open Dev Data (CC BY 4.0), the same data developerreport.com draws. A 28-day rolling count: developers with at least one commit in the 28 days ending that day. Developers who contributed to repositories of more than one chain, or to wallets, bridges, oracles or RPC repositories. Single-chain plus multi-chain is the total.

An external total on a different basis, shown for scale onlyUnit: CountSource: Public commit data

Electric Capital's figure from Open Dev Data (CC BY 4.0), the same data developerreport.com draws. A 28-day rolling count: developers with at least one commit in the 28 days ending that day. Developers Electric Capital ranks full-time from their activity over 84 days: active on roughly 10 or more days a month.

An external total on a different basis, shown for scale onlyUnit: CountSource: Public commit data

Electric Capital's figure from Open Dev Data (CC BY 4.0), the same data developerreport.com draws. A 28-day rolling count: developers with at least one commit in the 28 days ending that day. Active on fewer days than full-time, over Electric Capital's 84-day window. Full-time, part-time and one-time make up the total.

An external total on a different basis, shown for scale onlyUnit: CountSource: Public commit data

Electric Capital's figure from Open Dev Data (CC BY 4.0), the same data developerreport.com draws. A 28-day rolling count: developers with at least one commit in the 28 days ending that day. Developers with a single contribution in Electric Capital's 84-day window.

An external total on a different basis, shown for scale onlyUnit: CountSource: Public commit data

Electric Capital's figure from Open Dev Data (CC BY 4.0), the same data developerreport.com draws. A 28-day rolling count: developers with at least one commit in the 28 days ending that day. Developers whose first crypto commit was less than 1 year earlier.

An external total on a different basis, shown for scale onlyUnit: CountSource: Public commit data

Electric Capital's figure from Open Dev Data (CC BY 4.0), the same data developerreport.com draws. A 28-day rolling count: developers with at least one commit in the 28 days ending that day. Developers whose first crypto commit was 1 to 2 years earlier.

An external total on a different basis, shown for scale onlyUnit: CountSource: Public commit data

Electric Capital's figure from Open Dev Data (CC BY 4.0), the same data developerreport.com draws. A 28-day rolling count: developers with at least one commit in the 28 days ending that day. Developers whose first crypto commit was 2 or more years earlier.

An external total on a different basis, shown for scale onlyUnit: CountSource: Public commit data

Electric Capital's figure from Open Dev Data (CC BY 4.0), the same data developerreport.com draws. Commits in the 28 days ending that day, across the ecosystem's repositories.

An external total on a different basis, shown for scale onlyUnit: CountSource: Public commit data

Electric Capital's figure from Open Dev Data (CC BY 4.0), the same data developerreport.com draws. Developers whose first commit to any repository in Electric Capital's crypto taxonomy falls in the month.

An external total on a different basis, shown for scale onlyUnit: CountSource: Public commit data

Electric Capital's figure from Open Dev Data (CC BY 4.0), the same data developerreport.com draws. Repositories in Electric Capital's crypto taxonomy, by the month they were created on GitHub.

An external total on a different basis, shown for scale onlyUnit: CountSource: Public commit data

Electric Capital's figure from Open Dev Data (CC BY 4.0), the same data developerreport.com draws. Every repository in Electric Capital's crypto taxonomy at the snapshot.

An external total on a different basis, shown for scale onlyUnit: CountSource: Public commit data

Electric Capital's figure from Open Dev Data (CC BY 4.0), the same data developerreport.com draws. Every commit Electric Capital has recorded to those repositories, up to the snapshot.

An external total on a different basis, shown for scale onlyUnit: CountSource: Public commit data

Counted over developers whose profile location Electric Capital geocodes to the country, about a third of active developers, so an observed minimum, not a developer count. Developers with at least one commit to a crypto repository in the 28 days ending that day: Electric Capital's monthly active developer definition. Split, as on the Global page, by single-chain or multi-chain, by full-time, part-time or one-time, and by tenure.

Observed minimum: a floor over the attributed cohort, never a totalUnit: CountSource: Public commit data

Counted over developers whose profile location Electric Capital geocodes to the country, about a third of active developers, so an observed minimum, not a developer count. Developers whose first commit to any repository in Electric Capital's crypto taxonomy falls in the month.

Observed minimum: a floor over the attributed cohort, never a totalUnit: CountSource: Public commit data

The country's monthly active developers over Electric Capital's world total that day. Only developers placed in a country count in the numerator, while the total counts everyone, so the share is an observed minimum: the true share is at least this.

Observed minimum: a floor over the attributed cohort, never a totalUnit: RateSource: Public commit data

GitHub Innovation Graph (CC0), quarterly, for every public GitHub account in the economy, crypto or not. Organisations GitHub attributes to the economy.

An external total on a different basis, shown for scale onlyUnit: CountSource: GitHub Innovation Graph

Active developers who contributed to the ecosystem in the period, divided by all active developers in the same scope and period. A developer counts for an ecosystem when they contribute to any project in its tree, as Electric Capital files them (a Base project counts for Ethereum). Developers contribute to several ecosystems, so the shares add up to more than 100%. Not published when fewer than 50 developers are active in the scope or fewer than 5 contribute to the ecosystem.

A ratio within the observed cohort; not a minimum of anythingUnit: RateSource: Derived from published series

A country's developers contributing to the ecosystem, divided by all developers in Nigeria, Kenya and South Africa contributing to it. A different measure from the country's participation rate: it answers how much of the region's activity in the ecosystem comes from this country.

A ratio within the observed cohort; not a minimum of anythingUnit: RateSource: Derived from published series

GitHub Innovation Graph (CC0), quarterly, for every public GitHub account in the economy, crypto or not. Repositories GitHub attributes to the economy.

An external total on a different basis, shown for scale onlyUnit: CountSource: GitHub Innovation Graph

GitHub Innovation Graph (CC0), quarterly, for every public GitHub account in the economy, crypto or not. Pushes to GitHub from the economy in the quarter.

An external total on a different basis, shown for scale onlyUnit: CountSource: GitHub Innovation Graph

Counted over developers placed in the country, so an observed minimum, not a developer count. Developers whose first-ever contribution to a tracked repository falls in the month. Recent months rise in later releases, as the source adds older projects.

Observed minimum: a floor over the attributed cohort, never a totalUnit: CountSource: Derived from published series

Counted over developers placed in the country, so an observed minimum, not a developer count. Developers who became visible in the month because the source added a project they had contributed to, when their first contribution was more than a year earlier. An approximation from the date each project was added, published from January 2020. They are not new developers.

Observed minimum: a floor over the attributed cohort, never a totalUnit: CountSource: Derived from published series

GitHub Innovation Graph (CC0), quarterly, for every public GitHub account in the economy, crypto or not. Developers in the economy who pushed code in the language in the quarter; a developer can count in several languages.

An external total on a different basis, shown for scale onlyUnit: CountSource: GitHub Innovation Graph

Counted over developers placed in the country, so an observed minimum, not a developer count. Repositories created on GitHub in the month that developers in the scope have contributed to.

Observed minimum: a floor over the attributed cohort, never a totalUnit: CountSource: Derived from published series

GitHub Innovation Graph (CC0), quarterly, for every public GitHub account in the economy, crypto or not. Developers in the economy who pushed to repositories tagged with the topic in the quarter.

An external total on a different basis, shown for scale onlyUnit: CountSource: GitHub Innovation Graph

GitHub Innovation Graph (CC0), quarterly, for every public GitHub account in the economy, crypto or not. GitHub's collaboration weight between developers in the economy and in the partner economy in the quarter.

An external total on a different basis, shown for scale onlyUnit: CountSource: GitHub Innovation Graph

Counted over developers placed in the country, so an observed minimum, not a developer count. Repositories more than 90 days old that received their first contribution from a developer in the scope in the month.

Observed minimum: a floor over the attributed cohort, never a totalUnit: CountSource: Derived from published series

Our observed crypto developers in the quarter per 100,000 GitHub accounts GitHub attributes to the country. A lower bound: the numerator is an observed minimum (about 40% of developers can be placed in a country), and GitHub places accounts by its own method, not by profile location.

A ratio within the observed cohort; not a minimum of anythingUnit: RatioSource: GitHub Innovation Graph

The relative change in observed active developers from the previous quarter. Both counts are observed minimums, so the change is between minimums.

A derived difference between two published seriesUnit: changeSource: Derived from published series

The relative change in observed active developers from the same period a year earlier.

A derived difference between two published seriesUnit: changeSource: Derived from published series

The change in an ecosystem's participation rate from the previous quarter, in percentage points.

A derived difference between two published seriesUnit: pointsSource: Derived from published series

Of the developers whose first contribution fell in the quarter, the share active again in the following quarter.

A ratio within the observed cohort; not a minimum of anythingUnit: RateSource: Derived from published series

Of the developers whose first contribution fell in the quarter, the share active in the same quarter a year later.

A ratio within the observed cohort; not a minimum of anythingUnit: RateSource: Derived from published series

Of the developers who were occasional contributors (under 10 contribution days) in the previous quarter and are still active, the share contributing on 10 or more days this quarter. Contribution days measure activity, not employment.

A ratio within the observed cohort; not a minimum of anythingUnit: RateSource: Derived from published series