What at first was only being whispered about at community meetups, in private chats among project maintainers, inside OSS business-model strategy meetings and other backwaters, has now fully bloomed into mainstream social media posts, blogs and articles.
Just what exactly is the effect of AI on open source software?
Put even more bluntly: Will AI kill off the OSS market as we know it?
It’s a funny thing. Things seem invincible, until they aren’t. Sometimes the end comes swiftly. Sometimes it comes by a thousand cuts. And even when it looks sudden, it usually isn’t. The decline has been happening quietly for a while, below the radar, until one day it’s visible for everyone to see.
We’re roughly three years in since generative AI burst onto the scene. In that short span, it’s gotten very good at writing code. Good enough that today it’s hard to argue with estimates suggesting more than half of new code is written either directly by AI or with heavy AI assistance. And during that same period, something else has been happening in parallel: Fewer developers reading docs, fewer stars and forks, fewer meaningful community interactions around open source projects.
Developers are still using open source. They just aren’t showing up.
That difference is everything.
For decades, open source thrived not just because the code was free, but because the ecosystem around it was alive. People read the docs. They filed issues. They debated approaches. They contributed back. That activity wasn’t just cultural; it was economic. Attention turned into adoption, adoption turned into credibility, and credibility eventually turned into revenue through support, services, enterprise editions or hosted offerings.
AI is quietly snapping that chain.
When a developer asks an AI assistant how to do something, they don’t land on your documentation site. They don’t browse your examples. They don’t even know which project the solution came from. The AI becomes the interface, the translator, the front door. The open source project itself fades into the background.
This dynamic has been documented increasingly well over the last year. Reporting from Hackaday and 404 Media, along with analysis from engineering consultancies and OSS practitioners, has described what’s now commonly referred to as “vibe coding” — a development pattern where AI mediates most interactions with open source rather than direct engagement with the project itself.
The result is a strange paradox: Usage goes up, but engagement goes down. And when engagement goes down, the business models that sustained open source start to wobble.
We’re already seeing it. Projects are reporting sharp drops in documentation traffic. Maintainers are noticing fewer thoughtful contributions. Companies built around open source are struggling to convert popularity into revenue. Sponsorships dry up when the visible signals of community health — stars, forks, discussion — evaporate.
This is what “vibe coding” really means. The vibe is convenience. The cost is connection.
If you want to understand where this hurts the most, talk to maintainers. Open source maintenance was never glamorous work, but it was at least grounded in a sense of shared responsibility. AI changes that dynamic. As several researchers cited by 404 Media point out, AI tools can generate large volumes of pull requests that technically function but lack an understanding of project context or long-term intent.
Burnout was already a problem in open source. AI is accelerating it.
There’s also a more subtle erosion happening. Open source wasn’t just a distribution model; it was an apprenticeship model. You learned by reading other people’s code, by seeing how problems were solved, and by participating in the conversation. When developers jump straight from a problem statement to an AI-generated answer, that shared learning loop weakens. The code may work, but the collective understanding doesn’t grow.
To be fair, there’s a counter-argument — and it’s not wrong. AI is trained on open source. It depends on open source. It often recommends open source libraries. In many cases, installation numbers are still climbing. As Made With Love has argued, AI can actually increase adoption of open source components even as it disrupts the surrounding economics.
And let’s be clear: AI does not replace high-quality, well-maintained libraries. It remixes existing knowledge. It does not assume responsibility for long-term maintenance, security patches or operational stability. When something breaks at scale, nobody opens a support ticket with an LLM.
So no, AI isn’t killing open source outright.
But that’s not the real issue.
The real shift is economic and behavioral. AI makes bespoke code cheap. Historically, open source won because it spread effort across the community. Why reinvent the wheel when someone else already built it? Why maintain your own version when the shared one is better?
AI flips that math. When generating a custom solution takes seconds, the incentive to standardize drops. Teams increasingly ask the AI to write “something like” what they need instead of pulling in a dependency. Both Hackaday and 404 Media highlight this trend as a core risk: Fragmentation replacing shared foundations.
In the short term, this feels empowering. In the long term, it leads to duplicated effort, harder-to-secure systems and brittle software nobody fully understands. Security teams hate this. Operators hate this. Future maintainers really hate this.
Layer on top of that the unresolved legal and licensing mess. Enterprises are uneasy about what they’re shipping. Maintainers are uneasy about how their work is being absorbed into training data. Nobody really knows where attribution begins and ends anymore. Add in the growing fear of “AI slop” — oceans of low-quality, insecure or redundant code — and the signal-to-noise problem only gets worse, a concern echoed across all three sources.
So where does that leave us?
In the short term, it’s hard to argue that AI isn’t dampening the fervor around open source. The energy has shifted. The gravity has moved. Communities feel quieter. Business models feel shakier. Maintainers feel more isolated.
Longer term, there’s still a path where this makes open source better, not worse. Scarcity has a way of clarifying value. Projects that survive will likely be better governed, better maintained and more intentional about sustainability. AI may force open source to grow up in ways it’s long postponed.
But make no mistake: We’re in a transition, not a victory lap.
And that brings me to Shimmy’s take.
Nothing lasts forever. Not empires. Not sports dynasties. And certainly not technology models. Open source has had a remarkable, historic run as the king of the hill. For years, it felt untouchable. The default answer to almost every software question started with, “There’s an open source project for that.”
AI isn’t some scrappy David throwing stones at OSS’s Goliath. It’s a structural force rearranging the ground beneath it. It’s already disrupting the open source apple cart. Whether it topples it completely or forces it to become something different — and maybe even stronger — is still an open question.
But one thing is clear.
Things only seem invincible, right up until the moment they aren’t.
