Stop Flooding Open Source Projects With AI Slop Just to Pad Your CV

In a frustrated blog post published on neilalexander.dev, developer Neil Alexander is calling out the growing practice of submitting AI-generated pull requests and contributions to open source projects purely to embellish one's resume or CV. What was once an occasional annoyance has grown into a systemic problem that is draining the time and energy of project maintainers across the ecosystem.

The core issue is that AI-generated contributions are often shallow, incorrect, or simply misaligned with a project's architecture, coding style, and actual needs. Despite their low quality, maintainers are still obligated to review these submissions, provide feedback, and ultimately reject them — a process that consumes valuable time that could be spent on meaningful development work and genuine community building.

The Hacker News discussion around the article quickly gained momentum, with many maintainers sharing their own experiences of being overwhelmed by a flood of meaningless AI-assisted contributions. Several commenters suggested that projects should adopt clearer contribution guidelines, stricter review processes, and potentially automated tooling to detect and filter AI-generated submissions before they ever reach a maintainer's queue.

Ultimately, this trend reflects a broader tension in the age of AI-assisted development: when powerful tools make it trivially easy to generate plausible-looking code without genuine understanding, it creates perverse incentives to exploit open source communities for personal gain. The open source world now faces the challenge of protecting its collaborative spirit and maintainer bandwidth while remaining welcoming to sincere contributors of all skill levels.