Open source maintainers across many major repositories have issued public warnings about a. Sharp rise in low-quality, AI-generated pull requests, code patches. And documentation contributions, and they say these are flooding their issue trackers and. Wasting thousands of hours of volunteer time. According to posts on GitHub, the Linux kernel mailing list. And several popular npm and PyPI projects, contributors are increasingly using large language. Models to mass-generate submissions. That look plausible on the surface but contain made-up fixes, fake APIs, and copied code snippets. This guide covers "Please stop flooding our projects with AI slop to furnish. Your CV" in detail.
The frustration boiled over in a widely shared blog post titled "Please stop. Flooding our projects with AI slop to furnish your CV,". Which veteran open source maintainers published earlier this month and. Which circulated through Hacker News and developer communities. The post argued that contributors are using generative AI tools to mass-produce patches, typo fixes, and minor dependency bumps, and then list these contributions on résumés and LinkedIn profiles as evidence of "open source experience." The maintainers wrote that such submissions use up a disproportionate amount of. Review time and erode trust in good-faith contributors.
How Bad Is the AI Slop Problem in Open Source?
Hard data on the trend remains limited, but maintainers report clear increases, and according to the Node.js project triage logs reviewed by multiple outlets, about 20% of new pull. Requests in late 2025 were flagged as low-quality or AI-assisted spam. The Python Package Index (PyPI) said in October 2025. That it had removed thousands of auto-generated packages. Which uploaded empty or fake code. And PyPI now automates this removal through a new malware-detection tool it got from. The package security firm Snyk.
Senior maintainers describe the same patterns. And Linux kernel contributor Greg Kroah-Hartman, who maintains the stable branch and the USB subsystem, posted on the Linux Kernel Mailing List (LKML) in November 2025. That he had personally rejected hundreds of patches generated by automated tools. Which did not compile or referenced non-existent kernel functions. "I don't have time to babysit your chatbot," he wrote in a message archived at lkml.org. "If a patch is obviously machine-generated, it goes in the bin."
Why Maintainers Say This Matters Beyond Their Repositories
Open source software underpins an estimated 70% to 90% of modern applications. And this figure comes from repeated analyses by Synopsys in its annual Open Source Security and Risk Analysis report. Which means that. When maintainer burnout speeds up, downstream companies face real security and stability risks. Critical projects get fewer updates, slower vulnerability patches, and less attentive code review. And the XZ Utils backdoor attempt of 2024. Which was traced to a single maintainer working under social engineering pressure, showed. How thin staffing in core libraries can become an attack surface.
The volunteer nature of most open source work makes it especially open to this problem. Because projects like curl. Which is maintained mainly by Daniel Stenberg. And ImageMagick rely on a handful of dedicated contributors who review thousands of submissions. And adding AI-generated noise to that queue lowers the signal-to-noise ratio for everyone. Which includes legitimate newcomers trying to make their first contribution. Stenberg has publicly asked contributors to "think before you submit" and has warned. That automated tools cannot replace understanding the codebase.
What This Means for Companies and Developers
For engineering managers, the practical takeaway is clear: counting GitHub contributions as a. Hiring signal without checking their substance is now clearly unreliable. And résumé screening processes that treat raw contribution counts or green-square density as. Evidence of skill will increasingly filter in. Candidates who have outsourced their thinking to a chatbot. Hiring teams should instead review specific pull requests, ask candidates to walk through their reasoning. And weight depth over volume.
For contributors, the advice from seasoned maintainers is consistent: read the project's contribution. Guidelines, understand the existing code, run the test suite yourself. And submit changes you can defend in a code review. Because AI assistants can help you understand unfamiliar APIs or draft boilerplate. But the human contributor must own the correctness of the result. According to a November 2025 statement from the Open Source Initiative, "AI tools are acceptable aids, not acceptable authors."
What's Next for Open Source Triage Tools
Expect repository platforms to add more automated defenses. Because GitHub has already tested AI-based duplicate detection and several community projects have released bots. That flag suspicious commits by measuring how similar their text is to known LLM outputs. SPDX-style metadata proposals are also moving through the TODO Group. Which is a consortium of open source program offices, to label commits as AI-assisted or human-authored. But no standard has shipped yet. And whatever the tooling, the underlying message from maintainers is unchanged: respect the. Work, understand the code. And stop treating open source as a free résumé-padding service.
Key Points
Maintainers report a sharp rise in low-quality, AI-generated pull requests and dependency updates. Across major open source projects.
Greg Kroah-Hartman publicly rejected hundreds of machine-generated kernel patches on the LKML in November 2025.
PyPI removed thousands of auto-generated packages using new malware-detection tooling in late 2025.
Open source code underpins an estimated 70% to 90% of modern applications, per Synopsys analyses.
Hiring teams are being urged to verify the substance of candidate contributions rather than count them.
The Bottom Line
Open source runs on trust and attention, and AI slop is draining both. Which is why the projects. That keep the internet running deserve contributions from people who actually understand what they are submitting.
Related Resources
For more context, check our related articles on open source maintainer burnout, AI code review tools. And hiring practices in software engineering.
