DragonMinded's libdragon project has opened an issue proposing an explicit ban on AI-generated contributions, joining a growing number of open source maintainers drawing hard lines against large language model output in their codebases. The Nintendo 64 development library, which has accumulated 176 forks on GitHub, would reject any pull request, issue, documentation update, or code review created wholly or partially by AI. Prior contributions discovered to be AI-generated would be removed retroactively.
Libdragon maintainer proposes CONTRIBUTING.md policy
The proposal comes from a maintainer who has already added similar language to other repositories they oversee. The suggested blurb makes the policy unambiguous: contributors must understand and take responsibility for everything they submit. Honesty is the enforcement mechanism — the maintainer acknowledges vetting every submission for AI usage is impractical and explicitly rejects witch-hunt tactics against pull requests.
Instead of relying on detection tools, the policy directs contributors who are unsure or stuck to open an issue describing their goal, or a draft pull request explaining what they want to accomplish and where they are blocked. The maintainer frames this as a collaborative alternative: community members will work through the problem together rather than outsourcing the thinking to a model.
Open source projects grapple with AI contribution flood
Libdragon is not alone. Maintainers across the ecosystem report a surge in low-effort pull requests and issues that bear the hallmarks of LLM generation — verbose but shallow explanations, invented APIs, and hallucinated dependencies. Some projects have resorted to requiring contributors to explain their reasoning in their own words or to pass simple verification steps before a human review begins.
The libdragon stance goes further than most by declaring an outright ban rather than a disclosure requirement. The policy covers not just code but issues, documentation, and code reviews — any artifact that shapes the project's direction or knowledge base.
Retroactive removal clause sets a stricter tone
The provision to remove prior contributions found to be AI-generated is unusual. Most policies apply only going forward. This clause signals that the maintainer views AI output as fundamentally incompatible with the project's integrity, not merely a quality-control nuisance. It also places the burden on contributors to self-audit their own history.
Enforcement will rely on community vigilance and contributor honesty. The maintainer has offered to step in directly if a submitter becomes combative when pointed to the policy, shielding other maintainers from confrontation.
What this means for contributors and downstream users
For developers targeting the Nintendo 64 platform, the policy means libdragon's codebase will remain entirely human-authored. Contributors who previously leaned on coding assistants for boilerplate, documentation drafts, or algorithm suggestions will need to produce that work themselves or discuss it in the open with the community.
Downstream projects that depend on libdragon gain a signal about provenance: every line in the library passed through a human mind that understood it and took responsibility for it. In a supply chain where AI-generated vulnerabilities and licensing ambiguities are emerging concerns, that signal carries weight.
A broader shift in maintainer expectations
The libdragon issue reflects a wider recalibration. As AI tools lower the friction of producing plausible-looking code, maintainers are reasserting that open source collaboration rests on human judgment, shared context, and accountability — qualities that do not transfer from a model prompt. Whether outright bans become common or projects settle on lighter disclosure rules, the era of implicit acceptance is ending.