🟢 READ | ⏱ 5 min | 📡 8/10 | 🎯 Open source maintainers, developers, anyone who depends on OSS infrastructure

TL;DR

"AI Slopageddon" (RedMonk's term) isn't just about low-quality PRs — it's a structural economic threat to open source sustainability. When AI agents select packages without devs reading docs or filing bugs, the human engagement loops that fund maintainers break down. Real-world consequences are already here: cURL shuttered its bug bounty after $86K in payouts when valid submissions collapsed from 5% to near-zero. Tailwind CSS downloads climbed while docs traffic fell 40% and revenue dropped 80%. The academic model predicts declining OSS availability even as AI productivity rises.

Signal

• Tailwind CSS's 40% docs traffic drop + 80% revenue drop while downloads climbed is the clearest empirical evidence of the broken engagement loop: AI uses the library, AI doesn't read the docs, maintainers don't get paid
• GitHub Copilot launched issue generation in May 2025 without giving maintainers filtering tools — the platform that profits from AI has zero incentive to stop AI-generated submissions
• The researchers' proposed fix (Spotify-style revenue redistribution) requires vibe-coded users to contribute 84% of what direct users generate — they calculate this is "unrealistic"

What They're NOT Telling You

The academic model is theoretical and not empirically validated against actual maintainer economics at scale. The "niche projects suffer most" thesis is correct but the doomsday framing (next Linux won't be built) is speculative. Large, well-funded OSS projects (Linux, Kubernetes) are largely insulated — the threat is concentrated in the long tail of maintainer-funded projects, which is where most software infrastructure lives.

Trust Check

Factuality ✅ (cURL/Ghostty/tldraw citations verified) | Author Authority ✅ (Steef-Jan Wiggers, InfoQ) | Actionability ✅ (maintainers: update contribution policies now)