AI is making open source more valuable than ever, but it is also quietly increasing the pressure on the communities that maintain it.
That shift has been on my mind recently after being quoted in two different LeadDev articles discussing the intersection of AI and open source. One article explored what the Tailwind situation tells us about the economics of open source companies in an AI-driven world, while the other examined the growing problem of “AI slop” appearing in open source repositories as maintainers increasingly encounter AI-generated pull requests that do not fully reflect an understanding of the issue being addressed.
At first glance those might seem like unrelated conversations. One focuses on sustainability and business models, while the other looks at contributor behavior and code quality. But they are both signals of a deeper change in how developers discover, learn from, and contribute to open source projects.
Having spent years working in open source communities, particularly in the WordPress ecosystem, the patterns maintainers are seeing right now feel meaningfully different. Open source has always been foundational infrastructure for the web for better or worse, but AI is amplifying that role in ways that are both exciting and challenging for the communities that sustain it for better or worse.
Many modern AI systems are built on open source frameworks, and large language models have been trained on enormous bodies of publicly available code. At the same time, developers are increasingly using AI-powered tools to generate code, debug problems, and explore unfamiliar technologies, and the answers those tools produce often rely heavily on open source libraries, patterns, and documentation.
In other words, open source is not becoming less important in the age of AI. If anything, it is becoming even more central to how software gets built.
What is changing is how developers engage with the projects behind that infrastructure. Traditionally, developers discovered and learned about open source projects through documentation, issue discussions, conference talks, blog posts, and direct interaction with maintainers and contributors. Over time they built a mental model of how a project worked, what problems it was designed to solve, and how to contribute effectively.
AI tools reshape that feedback loop. Instead of reading documentation or exploring issues, developers can increasingly ask an AI assistant for an answer and receive working code or configuration suggestions almost immediately. The AI draws from documentation, source code, and examples to generate a solution, often without requiring the developer to interact directly with the project itself.
That shift is incredibly powerful and can dramatically accelerate development, but it also creates a more indirect relationship between developers and the communities behind the tools they rely on. Developers can benefit from open source projects without ever encountering the maintainers, reading the roadmap, or participating in the conversations that shape how those projects evolve. But… is that a good thing, that separation?
Maintainers are also beginning to feel the effects of AI from another direction. Across many open source projects, maintainers are seeing a noticeable increase in AI-assisted contributions. Some of these contributions are thoughtful and well considered, and AI can absolutely help people get started with open source or explore parts of a codebase that might otherwise feel intimidating.
But there is also a growing pattern of pull requests that appear to have been largely generated by AI without a clear understanding of the issue they attempt to address. In those cases the code might compile or appear plausible, but the proposed changes often do not reflect the architectural decisions or design constraints of the project.
Maintainers then spend significant time reviewing, explaining, or rejecting contributions that ultimately add more overhead than value. When multiplied across dozens or hundreds of submissions, that review burden can quickly become a real source of strain for projects that are already maintained by small teams or volunteers.
None of this means AI is bad for open source. In many ways it has the potential to strengthen the ecosystem by helping developers ramp up more quickly, improve documentation, and lower the barrier to entry for contributors who want to participate but do not yet feel comfortable navigating a large codebase.
At the same time, open source communities will likely need to develop new norms around how AI is used within contribution workflows. That might mean encouraging contributors to submit smaller and more focused pull requests, ensuring they understand the problems they are trying to solve before generating code, and being transparent about when AI tools were involved in producing a proposed change. It may also mean thinking more intentionally about how maintainers can manage increasing contribution volume without burning out.
These are conversations already happening in several open source communities, including WordPress. With more than 40% of the web running on WordPress, the ecosystem offers an interesting lens into how large open source projects may adapt to AI-assisted development. The WordPress AI team and initiatives like the AI Experiments plugin are exploring how AI capabilities can be integrated into the platform while still maintaining healthy contributor workflows and sustainable community practices.
The two LeadDev articles that sparked this reflection looked at different problems, but both point toward the same broader transformation. AI is making open source more widely used, more visible, and more deeply embedded in the development process than ever before, while at the same time reshaping the relationship between developers and the projects they depend on.
In many ways, AI is increasing the demand for open source while simultaneously increasing the maintenance burden on the people who sustain it. The tools that make it easier to generate code, build applications, and experiment with new technologies are often powered by the very projects that maintainers are now struggling to keep up with.
Open source communities have adapted to major shifts before. Package managers, centralized collaboration platforms like GitHub, and the rise of cloud infrastructure all reshaped how developers build and collaborate. AI feels like another one of those moments where new tools dramatically expand what developers can do while also forcing communities to rethink how they sustain the projects that make that innovation possible.
AI will continue to make it easier to generate code, explore new tools, and build software faster than ever before. But the infrastructure that makes that possible still depends on maintainers, contributors, and communities that invest their time and expertise into open source projects.
If AI is going to accelerate development, it should also raise the bar for how thoughtfully we engage with the projects we depend on. That means understanding the problems we’re solving, contributing responsibly, and recognizing that open source doesn’t sustain itself.
The featured image comes from Openverse in searching for “developers coding collaboration” and is “The Beauty of a New Day” by Thomas Hawk and licensed under CC BY-NC 2.0.
