Please Stop Flooding Open Source Projects with AI Slop
Neil Alexander, a maintainer, is fed up with AI-generated contributions aimed at padding GitHub profiles. In a post titled "Please stop flooding our projects with AI slop to furnish your CV", he describes a recent pattern: contributors with zero prior engagement suddenly submitting PRs that fix spelling and grammar in comments. Claude made the fixes, wrote the PR descriptions, and even signed off the commits—all in an attempt to build a fake contribution history.
The Problem: Gaming GitHub with LLMs
Alexander notes that open source contributions are a currency for job hunting. GitHub's activity graph, contributor avatars, and follower feeds all reinforce this. With LLMs like Claude, it's trivial to:
- Ask Claude to list interesting open source projects.
- Instruct it to find minor issues.
- Have it generate and submit PRs automatically.
This creates an illusion of involvement without any real effort or care. The contributor in question had virtually no GitHub activity since late 2018, then suddenly opened three typo-fixing PRs—all AI-authored.
Maintainer Response: Closing PRs Without Comment
Alexander closed all three PRs without comment. His reasoning: "I’m just not interested in encouraging people to take up our time with this kind of busywork. I do not want to set a precedent of accepting PRs that materially improve nothing, nor do I want our contributor list to become a reward for asking a robot to fix typos."
The same trend is hitting security reports. AI-generated vulnerability reports flood in, often with proposed fixes. CVEs are now being credited to people who didn't do real research. Alexander's team has become more selective, sometimes declining CVE notices for low-severity items.
A Call for Genuine Contribution
Alexander's message is direct: "Open source is built on trust. The metric that matters is not how many pull requests you can persuade an LLM to produce, nor how many CVEs you can accumulate, but whether you can make a project meaningfully better. If you want to contribute to open source projects, contribute because you care. If all you want is another green square or another contributor badge, please go elsewhere."
For developers using AI agents, this is a cautionary tale: use AI as a tool, not as a substitute for genuine engagement. Maintainers value real context and investment over automated busywork.
📖 Read the full source: HN AI Agents
👀 See Also

AMD Ryzen AI NPUs Gain Linux LLM Support via Lemonade 10.0 and FastFlowLM
AMD Ryzen AI NPUs now support running large language models on Linux through Lemonade 10.0 server with FastFlowLM runtime, requiring Linux 7.0 kernel or AMDXDNA driver back-ports.
AI SREs Resolve Routine Incidents, But Engineers Lose Touch With Their Systems
Sylvain Kalache argues that AI incident responders reduce practice for engineers, worsening response to complex incidents, citing the Ironies of Automation and aviation training parallels.
The Atlantic Reports Rising Anti-AI Violence and Political Backlash
Bernie Sanders and Steve Bannon both decry AI as a threat to workers. A Molotov cocktail attack on Sam Altman's home and an Indianapolis councilman's shooting show anti-data-center violence is rising.
OpenClaw v2026.9.7 — snappier under load, smoother long chats, OpenAI Agents API, and more
OpenClaw 2026.9.7 moves long-reply saving, file opening, and history prep into the background to reduce cross-chat waits. Adds OpenAI Agents API, Sign in with ChatGPT (Beta), and database rollback for eligible updates.