Godot, the open-source game engine beloved by indie developers, is under siege—not by bugs or security flaws, but by an overwhelming flood of AI-generated code submissions. Maintainers now spend hours daily sifting through pull requests that are often written by large language models rather than human contributors. The problem isn’t just volume; it’s the erosion of trust in the very foundation of open-source collaboration.
At the heart of the issue is a single, staggering statistic: maintainers estimate that more than 90% of new pull requests now require manual scrutiny to determine whether they’re AI-generated or written by a human. The challenge isn’t just identifying AI contributions—it’s determining whether the code is even functional. Many submissions lack proper testing, contain placeholder test results, or include verbose descriptions that read like LLM output rather than thoughtful contributions.
The strain is taking a toll. One of Godot’s lead maintainers has openly questioned whether the project can sustain this level of manual review indefinitely. The core team prides itself on being welcoming to newcomers, but the influx of low-quality, untested code has created a paradox: the more accessible the project becomes, the harder it is to maintain its integrity.
Why AI Slop Is a Crisis for Open-Source Projects
The problem extends beyond Godot. GitHub itself has acknowledged the rising tide of AI-generated pull requests as a major operational challenge. While the platform has introduced tools to help maintainers filter or disable pull requests entirely, the solutions feel reactive rather than preventive. For projects like Godot, which rely on community-driven development, the issue is deeper: how do you distinguish between a well-intentioned but inexperienced and an AI-generated submission that may introduce critical bugs?
Some maintainers have explored automated detection tools—only to face a Catch-22. Using AI to detect AI-generated code feels counterintuitive, especially when the goal is to reduce reliance on machine-generated contributions in the first place. Others have considered migrating to alternative platforms, but such a move risks alienating the very community that keeps the project alive.
The Only Viable Solution? Money
With no technical fix on the horizon, the most practical solution may be financial support. Maintainers argue that hiring more reviewers—even part-time—could alleviate the bottleneck. However, funding open-source projects has always been a challenge, and Godot’s reliance on donations and sponsorships means progress is slow. Without additional resources, the team may soon reach a breaking point where the volume of AI-generated submissions becomes unsustainable.
The irony is stark: Godot thrives because it’s free and open, yet its survival now depends on paying maintainers to do the work that volunteers once handled. The question remains: in an era where AI is reshaping software development, can open-source projects adapt—or will they drown in the very technology they once championed?
