Open Source Contribution Statistics 2026: 35+ Data Points on Contributors, PRs, Maintainers, and Growth

If you want one stat that captures the scale of modern open source, start here: GitHub reported 395 million public and open source repositories in Octoverse 2025, up 19% year over year. That is not niche activity. That is an industrial-scale software ecosystem.

GitHub also reported 1.12 billion public and open source contributions in 2025, up 13% year over year. Contributions here include the visible activity that makes the ecosystem move: commits, pull requests, issues, discussions, reviews, and other collaborative actions tied to public development.

The platform growth behind those contributions is still absurdly strong. GitHub said a new developer joins every second. That is one of those stats that sounds made up until you remember how much of the world now learns, ships, experiments, and collaborates in public by default.

The growth rate of repository creation reinforces the same trend. GitHub's 2025 reporting said developers created more than 230 new repositories every minute. That means open source is not just large. It is still expanding at a pace that most industries would kill for.

That scale matters for your career. A decade ago, open source contribution was a strong signal. Today, it is one of the clearest public records of how software gets built. If you want to see where demand, experimentation, and technical momentum are heading, this is where the evidence lives.

The most useful contribution stat for working developers is pull request volume, because merged pull requests are where interest turns into actual shipped work. In 2025, developers merged 518.7 million pull requests in public repositories on GitHub, up 29% year over year according to Octoverse.

That works out to an average of roughly 43.2 million merged pull requests per month. In plain English, open source is not slowing down. It is processing a staggering amount of real collaboration every single month.

GitHub's Octoverse coverage also noted nearly 1 billion code pushes over the year. That matters because not every meaningful contribution ends in a public PR right away. The ecosystem is seeing both more visible review-based collaboration and more raw development activity.

Why is this happening? Part of it is simple global growth. More developers, more teams, and more companies build in the open than ever before. But another part is workflow maturity. Open source used to be associated with heroic maintainers and chaotic contribution paths. Today, the workflow is standardized. Fork, branch, commit, PR, review, merge. That lowers the barrier to entry.

It also means contribution history is more legible to hiring managers. A merged PR is not a vague claim on a resume. It is timestamped proof. That is one reason open source keeps punching above its weight in career discussions. It creates public evidence of how you work.

Source: GitHub Octoverse 2025

If you want the clearest trend line in open source right now, it is AI. GitHub reported that AI-related repositories now exceed 4.3 million, nearly doubling in less than two years. That is not just hype. It is one of the fastest shifts in project concentration the platform has ever seen.

More than 1.1 million public repositories now use an LLM SDK, and 693,867 of those projects were created in just the prior 12 months, up 178% year over year according to GitHub's 2025 reporting. In other words, the tooling layer around AI is not settling down. It is still in a land rush phase.

Contributor growth in generative AI projects tells the same story. GitHub said monthly contributors averaged about 151,000 across the measurement year, with a median around 160,000. Activity rose from about 86,000 contributors in January 2025 to a peak of 206,830 in May 2025, a 132% increase versus May 2024.

Looking just at January through August, GitHub reported average monthly contributors of roughly 175,000, up 108% year over year versus the same stretch in 2024. Those are ridiculous growth numbers in a mature software ecosystem.

Open source project rankings are shifting too. GitHub reported that 60% of the top 10 open source projects by contributors are AI-focused. When the fastest-growing contributor magnets on the largest code collaboration platform in the world are mostly AI tools, libraries, and runtimes, that tells you where experimentation budget is going.

This does not mean every developer needs to become an ML engineer. It does mean the surface area of open source contribution is changing. If you build tooling, wrappers, eval frameworks, vector infrastructure, developer experience around AI apps, or safety and governance layers, you are standing in the busiest traffic lane in the ecosystem.

For all the growth, some of the oldest problems have barely improved. The GitHub Open Source Survey found that 93% of respondents encountered incomplete or outdated documentation. That is close to universal agreement. Almost everyone who uses open source has hit this wall.

Here is the brutal part: 60% of contributors said they rarely or never contribute to documentation. This gap between what everyone complains about and what most people actually help fix is one of the clearest recurring patterns in open source.

The same survey found that licensing documentation matters a lot more than many contributors think. 64% of users said an open source license is very important when deciding whether to use a project, and 67% said it is very important when deciding whether to contribute. People talk endlessly about code quality, but uncertainty around legal terms is often what stops companies and contributors from moving.

GitHub's refreshed ecosystem research in 2024 added another uncomfortable data point. Only 1 in 50 repositories ships with a code of conduct, according to Octoverse 2025. That means governance and community standards are lagging far behind raw growth.

Tidelift's maintainer survey shows maintainers understand the issue. 92% of maintainers said they have already documented or plan to document their open source license clearly. 85% have already published or plan to publish a contributor guide. 78% have already documented or plan to document release notes or upgrade considerations, and another 78% said the same for a code of conduct.

Read that carefully. The maintainers know what healthy projects need. The problem is not awareness. The problem is bandwidth.

That has a practical career implication. If you contribute great documentation, release notes, onboarding guides, or contributor pathways, you are not doing lesser work. You are often doing work the project badly needs and most people avoid. In a crowded contribution landscape, that can actually make you more valuable, not less.

The biggest contradiction in open source right now is this: contribution volume is exploding while maintainer sustainability is still shaky. That is not a healthy long-term setup.

Current reporting built on the Tidelift maintainer survey says 60% of open source maintainers work without getting paid. That alone should make you uncomfortable if your company depends on open source for revenue-critical systems.

The same body of reporting found that 44% of maintainers who considered quitting cited burnout-related pressure. Another frequently cited reason was that other parts of life took priority. That is not because maintainers are lazy. It is because too much critical infrastructure still runs on volunteer labor done after work.

Recent reporting around major infrastructure projects has made the risk feel less abstract. When heavily used components stop receiving security support because maintainers are stretched too thin, the entire software supply chain feels it.

This is why the conversation around open source has shifted from pure contribution volume to sustainability. It is no longer enough to say open source is winning. The useful question is whether the people carrying the ecosystem can keep carrying it.

If you are an individual contributor, the takeaway is simple. Respect maintainer time. Open good issues. Submit clean pull requests. Improve docs. Follow templates. Do not dump vague bug reports and then wonder why no one is excited to help you.

If you run a company, the takeaway is even simpler. If your product depends on open source, you should be funding, sponsoring, contributing to, or otherwise supporting the projects that keep you alive.

For years, a lot of companies treated open source as a free buffet. Download it, deploy it, maybe complain about it on social media, but do not invest much back into the ecosystem. That attitude is changing.

The Linux Foundation's 2025 global open source research found that 44% of organizations rank sponsoring critical open source dependencies as a top investment priority. 41% prioritize funding developer training so teams can participate effectively in open source. And 39% prioritize increasing upstream collaboration and code contributions.

The research also tied active participation to outcomes. Organizations that move from passive consumption to active contribution report a 20% competitive advantage. That is the kind of stat executives understand fast.

Why would contributing upstream create advantage? Because it changes your position in the ecosystem. You get influence over the roadmap. You reduce long-term maintenance pain from carrying giant internal forks. You build credibility with the communities you depend on. And your developers get better because they are working in public, receiving outside review, and learning from projects beyond your company walls.

This is one reason open source contribution is becoming more respected inside traditional employers. It is no longer just a side project signal for recruiters. It is increasingly viewed as practical business leverage.

For developers, that matters. If you can show that your contributions improved upstream tooling your employer depends on, you are not just demonstrating technical skill. You are demonstrating leverage, judgment, and strategic thinking.

One of the better pieces of news in the current data is that at least some project hygiene metrics are moving in the right direction. GitHub reported that average fix times for critical severity vulnerabilities improved by 30% over the past year. That does not mean the ecosystem is suddenly secure by default. It does mean more projects are responding faster.

Tidelift's maintainer survey also shows maintainers trying to professionalize their projects even when resources are limited. 70% said they have already implemented or plan to implement reproducible and verifiable build processes. 69% said the same for two-factor authentication. Another 69% reported having or planning a security disclosure process.

Those are meaningful signals. Mature open source is no longer just about elegant code. It is about release discipline, security process, contributor experience, and operational sanity.

Still, the gap between best practice and default practice remains wide. When only a tiny share of repositories have formal governance docs, and too many maintainers are working unpaid, improvements are likely to stay uneven. The best-run projects will get better faster than the long tail.

That means developers who learn how to work in mature open source projects are learning skills with real market value: release management, review quality, contributor onboarding, secure defaults, and sustainable maintenance habits. Those skills transfer directly into senior engineering work.

So what should you actually do with all this?

First, stop thinking of open source as optional career garnish. When there are 395 million public repositories, more than a billion annual public contributions, and half a billion merged pull requests, open source is not extracurricular anymore. It is part of how the industry works.

Second, contribution depth matters more than contribution theater. The ecosystem is large enough now that nobody cares about random green squares by themselves. What matters is whether your public work shows useful judgment. Can you improve docs? Can you fix bugs cleanly? Can you work with maintainers instead of creating more work for them? Can you stick with a project long enough to become trusted?

Third, docs and maintenance work are underrated leverage. The data is screaming this at you. Ninety-three percent of people run into bad documentation. Most contributors do not help fix it. That means the opportunity is sitting right there. Everyone wants glamorous code changes. Fewer people want to make a project usable, readable, and safe. Be one of the people who does.

Fourth, AI-heavy open source is where the crowds are moving. If you want the hottest contribution zones, look at AI tooling, infrastructure, packaging, deployment, evals, developer workflows, and safety layers. The contributor growth is obvious. That does not mean you should chase hype blindly, but it does mean you should not ignore where the traffic is going.

Fifth, maintainers are the bottleneck. If you want to build a strong reputation, make life easier for maintainers. That is the shortest path to getting noticed. Open high-quality issues. Follow contribution guides. Keep pull requests tight. Write tests. Improve contributor docs. Respect review feedback. The developers maintainers like working with become known fast.

Sixth, companies increasingly care about upstream influence. Linux Foundation data shows more organizations investing in sponsorship, training, and code contributions because they see business upside. That means open source work is increasingly legible not just to recruiters, but to engineering leadership.

In plain English, the developers who win with open source are not necessarily the loudest ones. They are the ones who become useful in public.

Every statistic in this resource is cited from the following primary sources:

• GitHub Octoverse 2025 - repository counts, contribution volume, pull request volume, AI repository and contributor growth, governance and security trend data
• GitHub Open Source Survey - documentation, licensing, contribution behavior, and community experience survey results
• GitHub: Seven Years of Open Source - updated ecosystem survey data and trend comparisons
• Linux Foundation 2025 Global Open Source Research - organizational investment priorities, upstream contribution strategy, and business impact data
• Tidelift State of the Open Source Maintainer Survey 2023 - maintainer documentation, security practice, compensation, and burnout signals that continue to be cited in 2025 reporting