FOSS runs on three social inputs — review labour, trust, and reciprocity. LLMs put strain on all three at once.
Boundary: Low-quality PRs and burnout predate LLMs. AI changes speed, volume, and plausibility; the underlying commons problem is still under-compensated maintainer labour.
Review labour
AI volume overwhelms the people who turn patches into shared infrastructure.
The flood in numbers
17MAI-generated PRs per month (March 2026)
325%increase in six months — up from 4M in September 2025
~4.5%of all public GitHub commits from Claude Code alone
Flatnumber of people taking on maintainer or ownership roles
AI PR quality is still a review burden.CodeRabbit reports AI-generated PRs carry 1.7x more issues than human-written ones.
Public example, February 2026 Matplotlib maintainer Scott Shambaugh rejected an AI-authored change. Hours later, an AI persona published a personal attack piece about him.
Before: Anyone could join, triage issues, and merge PRs across 80+ packages. Shared trust scaled maintenance without centralised control.
After: AI spam made open membership a liability. Django projects have Django Commons; non-Django packages must find new homes or risk going unmaintained.
Not all bans: A scan of 1,000 popular repositories found 118 AI contribution policies — 78% allow GenAI but require disclosure and human review. The emerging norm is accountability, not prohibition.
Who pays
Entry path narrowsJunior developerslose first reviews, apprenticeship, and a low-friction route into FOSS.
Attention fragmentsMaintainerscarry suspicion, context switching, and unpaid incident response.
Contribution base shrinksProjectslose diverse small contributions and become more closed and fragile.
Renewal slowsThe movementloses the renewal mechanism that kept FOSS broad and resilient.
XZ Utils changed the baseline The lesson was not “review newcomers less kindly.” It was that trust itself can be weaponized.
AI flood changes the front door When maintainers see more bot-shaped PRs, every unsolicited submission becomes costlier to parse and easier to distrust.
Trend vs. floor: Newer models hallucinate fewer packages, but Kalai (OpenAI, 2024) proved that calibrated language models have an irreducible hallucination rate — the floor is above zero by design, not just by current limitation.
Security Exploitation
Noise became part of the incident.
March 2026 LiteLLM issue #24512 warned that the package on PyPI was compromised.
Nearly 500 comments The thread was submerged in repetitive bot-shaped replies. Briefly closed as not_planned, then reopened; a separate status thread stayed open.
Broader trend:ReversingLabs reports a 73% increase in malicious OSS package detections in 2025, with npm accounting for nearly 90% of detected open-source malware.
Reciprocity
AI breaks the implicit exchange that funds and sustains open-source work.
The docs-led business-model shock
Free framework
->
Docs traffic
->
Paid wrappers and sponsors
January 2026Usage still risingDocs traffic about 40% below early 2023Revenue close to 80% lower75% of engineers laid off
Adoption rose. The docs-led business model cracked.
Causation vs. correlation:Tailwind’s traffic drop could also stem from AI-powered search, market saturation, or competitors. AI isn’t necessarily the sole driver.
Open source as a liability
Actual move: Cal.com In April 2026 the scheduling SaaS went closed source after five years in public.
Security rationale The company said AI can scan public code for vulnerabilities and turn transparency into customer-data exposure.