Generative AI Doubles Coding Efficiency While Open Source Communities Face Surge in Low-Quality Contributions
The widespread adoption of generative artificial intelligence across software development workflows has driven a significant increase in code contributions to open-source projects, reshaping how developers build software. According to a recent industry report, approximately 59 percent of project maintainers report that code contributions have increased since the mainstream adoption of AI coding assistants. For large-scale open-source projects, that figure climbs even higher, with 69 percent of maintainers noting an upward trend in incoming contributions.
However, this quantitative surge has not been matched by a corresponding rise in code quality. The study reveals that roughly 25 percent of all code merge requests are flagged by maintainers as low-quality content. Often referred to as “AI Slop,” these submissions consist primarily of AI-generated code or modification suggestions that lack adequate validation, testing, and quality control. Among large projects, the proportion of low-quality submissions rises to 31 percent, placing an additional burden on volunteer and professional maintainers who must review incoming code.
Despite the challenges posed by unvetted submissions, the research confirms the substantial positive impact of generative AI on raw productivity. Surveyed developers widely agree that AI tools significantly accelerate coding workflows and technical discussions. The report notes that both contributors and maintainers experience productivity gains of up to 50 percent across a wide variety of standard development tasks.
Yet, the productivity benefits are not uniform across all programming scenarios. Researchers found that generative AI can actually hinder progress in highly complex development tasks. Approximately 21 percent of respondents reported that using AI tools on complex tasks ultimately required more time rather than less. These developers noted that the additional effort required to thoroughly review, correct, and verify AI-generated content frequently cancels out any initial time savings.

When developers do manage to save time through AI assistance, they typically reinvest those hours back into the open-source ecosystem rather than logging off early. The survey indicates that 66 percent of respondents use their recovered time to address long-standing technical debt within projects. Furthermore, 63 percent channel the time into developing new software features, while 58 percent choose to study new technologies and enhance their professional skill sets.
Project governance structures are currently struggling to keep pace with the rapid proliferation of AI-assisted development. The data shows that only 35 percent of open-source projects have established formal policies governing the use of artificial intelligence. Meanwhile, 32 percent of projects have neither implemented such rules nor have any current plans to introduce them.
To counter the influx of unverified code, a significant portion of developers are taking proactive steps on their own. The survey found that 61 percent of contributors conduct detailed personal reviews and complete functional testing before submitting AI-generated code, ensuring the modifications meet project requirements before they reach maintainers.
In response to these shifting trends, the research team recommends that open-source projects establish clear management frameworks for AI contributions. These measures include formulating written policies, enhancing development transparency, clarifying AI use disclosure requirements, and standardizing contribution attribution norms. Maintainers are encouraged to require contributors to complete necessary testing and documentation before submitting AI-assisted content, thereby minimizing the risk of low-quality code infiltrating core codebases.
Mark Collier, general manager of AI and infrastructure at the Linux Foundation, emphasized that evaluating the impact of generative AI on the open-source ecosystem requires looking beyond raw productivity metrics. Collier stated that stakeholders must pay equal attention to contribution quality and overall community health, arguing that future investments in AI tools must be matched by ongoing investments in project maintainers, community mentors, and collaborative frameworks to ensure long-term sustainability.
