Open-source developer report
Tezos
Developers are counted in a month when they write a new commit in an included public GitHub repository. History already present in a fork is not treated as newly written code. Bots and banned organizations are excluded. Raw ingestion includes repeat crawl snapshots; report totals count each repository–commit pair once, then apply the selected scope.
All time, including repeat crawl snapshots
Distinct pull requests merged in included repositories during the selected period
Older commit records copied into GitHub forks before each fork was created
Forked repositories created in the selected period
Unique GitHub developers seen before filtering
Unique developers who wrote at least one new commit during this period
81.8% of active developers
4 organizations
Explore Tezos by category
Every number below is filtered to Tezos. Choose a category to narrow it further, or show all chains to return to the complete dataset.
Active developers over time
The gray line shows everyone found in scanned commits. The colored lines show developers with newly written commits that month, including team developers, maintainers, and leads.
Pull requests merged each month
Each point is the number of distinct pull requests merged in included repositories during that month. Months stand alone; nothing accumulates from earlier months.
Active developers by contribution frequency
Full-time developers contributed on 10 or more days that month, part-time developers on 2–9 days, and one-time developers on 1 day.
Active developers by tenure
Newcomers started contributing less than 3 months ago, emerging developers 3 months to 2 years ago, and established developers 2 or more years ago.
New developers
A developer is counted once, in the month of their first newly written commit in the report.
New repositories and GitHub forks
Repositories are counted in their creation month. GitHub forks are shown separately from repositories that began without inherited fork history.
How much of the dataset is categorized
Organizations known only from GitHub may not have a category yet. They still appear in overall totals, but not in comparisons between categories.
4 categorized · 0 not yet categorized
77 categorized · 0 not yet categorized
Organizations
Developer activity by organization
Each organization keeps the same spot as you move through since inception. Larger circles mean more active developers. Inner circles show team developers, maintainers, and leads. A green border means its latest three-month average active developer count grew versus the prior three months; pink means it shrank. Six months are required for a comparison.
Use the slider or Play button to move through time. Positions stay fixed so you can follow the same organization from month to month. Select a circle to open its profile on Ecosystem Vision.