惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

N
Netflix TechBlog - Medium
G
Google Developers Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
T
The Blog of Author Tim Ferriss
Microsoft Azure Blog
Microsoft Azure Blog
GbyAI
GbyAI
L
LangChain Blog
云风的 BLOG
云风的 BLOG
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
aimingoo的专栏
aimingoo的专栏
P
Proofpoint News Feed
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
小众软件
小众软件
WordPress大学
WordPress大学
A
About on SuperTechFans
大猫的无限游戏
大猫的无限游戏
C
Check Point Blog
月光博客
月光博客
Stack Overflow Blog
Stack Overflow Blog
美团技术团队
Jina AI
Jina AI
T
Tailwind CSS Blog
Google DeepMind News
Google DeepMind News
D
Docker

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
AI is slowly destroying open source and its not even done...
Bridget Aman · 2026-05-19 · via DEV Community

With the wide adoption of AI, we have seen the positive and negative impact it has had on businesses across the board. Open source was supposed to be one of the biggest beneficiaries. The idea was that it would lower the barrier to contributing, help developers move faster, catch bugs earlier, make maintaining projects less of a grind.

What the ecosystem is actually facing looks nothing like the vision. The problems AI has introduced into open source are not small or temporary growing pains. They are hitting maintainers, contributors, projects, and the funding models that kept everything running. And it keeps getting worse.

Exhibit A: Vibecoded slop is the new foundation

One of the core benefits of open source is that you do not have to reinvent the wheel. If you need to convert units or handle dates, you pull a well-maintained package and move on. You trust the foundation so you can build something better on top of it. Except now, the foundation is being replaced by "vibecoded slop."

We’re seeing a flood of AI-generated projects hitting registries with zero oversight. It gets pushed out, it looks fine on the surface, and people install it. This vibecoded slop is now the foundation others are building on. And when the foundation is bad, everything on top of it inherits that. We have seen a wave of application leaks and breaches lately and a significant number of them trace back to projects that were never properly looked at before people trusted them with real data. It is a chain of vulnerabilities waiting to be pulled.

Exhibit B: AI agents are drowning the people keeping open source alive

Open source maintainers have always had to deal with bad pull requests. That isn't new. What is new is the volume.

AI agents are now being set up specifically to scan repositories, find open issues, generate code, and fire off pull requests automatically. They ignore the project's contribution guidelines and code style completely. The guidelines are there for a reason, they make maintenance manageable and keep the codebase consistent, but the agents do not care about any of that.

Shadcn said it plainly in a tweet on March 8: "Mass-generating PRs with your agents and clawbots isn't helping open source. It's quietly burning out the people who actually maintain it. Please stop."

The maintainers on the receiving end of all this are mostly volunteers. They are not paid. They do it because they care. And now instead of spending that energy on work that actually moves the project forward, they are stuck triaging noise. GitHub acknowledged how bad it had gotten and in February 2026 introduced two new repository settings so maintainers can disable pull requests entirely or restrict them to collaborators only. That a platform the size of GitHub had to build a feature just so maintainers could protect themselves from contributors says everything about where we are.

Exhibit C: Why would anyone bother anymore

Open source was built on a simple but powerful idea. You run into a problem, you work through it, and instead of keeping that solution to yourself you put it out there so the next person does not have to go through the same struggle. That act of sharing is the whole spirit of it. That is what built the ecosystem.

Stormy Peters, AWS Head of Open Source Strategy, put it in a way that probably resonates with a lot of developers right now "I generated it in three seconds. You could generate it in three seconds if you needed it. Why would I spend my time pushing it upstream when anyone could just generate it on demand?"

That question does not have an easy answer anymore. If any solution can be generated on demand, the motivation to package it, document it, maintain it, and share it starts to feel pointless. The whole value of putting something upstream was that it saved the next person the trouble. But if there is no trouble to save them from, why bother?

Conclusion

AI is not just introducing bugs or burning out maintainers, though it is doing all of that. It is making that choice feel irrational. Why share what anyone can generate? Why maintain what nobody values enough to contribute to properly? Why keep volunteering your time to triage noise?

Those questions do not have good answers right now. And the people who built the things you depend on are the ones sitting with them. Most will not make an announcement when they decide it is no longer worth it. They will just quietly stop.

Open source survived a lot of things. I am very sure it will survive with a lot of help from the community of course.