Can open source afford AI’s help?

Slop hasn’t gone anywhere. Maintainers are still wading through AI bug reports that are confidently wrong. Now a second flood is arriving on top of it: reports that are right, by the hundred, and each one can cost a maintainer a day to confirm and fix. Some projects are closing their doors rather than keep up. This week we look at who pays for the good reports, and what happens to the people who can’t.

• THE COST · Alex Band
  Maintaining the love for coding in the time of AI (opens in a new tab) · the reports got accurate, and that turned out worse: they come hundreds at a time, each one can eat a whole day, and there have been no major new features this year
• TRIAGE · Jonathan Corbet
  The 2026 Maintainers Summit (opens in a new tab) · the tools are still wrong about half the time, so the kernel is pushing pre-existing bugs into a separate database, arguing over whether to deprioritize unknown submitters, and Torvalds is floating a 24-hour delay on bot reports
• THE CASE FOR · Daniel Stenberg
  A curl audit by Aisle (opens in a new tab) · after all the AI noise, 35 real CVEs and “nothing but positive experiences”, because the company that found them backed its findings with skilled humans and has written dozens of commits to curl
• EXODUS · James Ross
  Open Source as We Know It Is Dead (opens in a new tab) · “AI made contributing cheap. It didn’t make maintaining any cheaper,” and the projects closing to outside contributions are the evidence
• LIGHTS OUT · encounter
  Sunsetting decomp.dev (opens in a new tab) · a solo maintainer shuts the project down rather than police AI contributions, because there isn’t the energy to enforce a rule consistently