# Zig enforces ban on AI-assisted code contributions > Source: > Published: 2026-05-29 19:22:39.278767+00:00 # Zig enforces ban on AI-assisted code contributions The Zig Software Foundation has enforced a strict ban on AI-assisted contributions to the **Zig** programming language codebase, prohibiting LLM-generated, paraphrased, edited, brainstormed, or debugged submissions, according to coverage by Business Insider and Neura Market. In a recorded comment reported by Business Insider, Zig president Andrew Kelley called AI-assisted contributions "invariably garbage" and said they "have no value whatsoever" and "take review time away from the team." Business Insider reported the project had about **200** open pull requests at the time of the recording. Separately, Techzine reports the project moved its primary repository off **GitHub** to **Codeberg**, citing problems with GitHub Actions and increasing AI integration on the platform. ### What happened The **Zig Software Foundation** implemented a categorical ban on contributions that were generated, paraphrased, edited, brainstormed, or debugged by large language models, as reported by Neura Market and Business Insider. In a recorded statement reported by Business Insider, Zig president **Andrew Kelley** said, "People are sending us contributions that have no value whatsoever," and added that such contributions "take review time away from the team." Business Insider also reported the project had roughly **200** open pull requests at the time of the recording. Techzine reported that the foundation migrated its canonical repository from **GitHub** to **Codeberg**, citing repeated issues with GitHub Actions and the project's desire to avoid tighter AI integration on the hosting platform. ### Technical details Per Neura Market and related project posts, Zig's policy extends beyond code to include LLM-generated comments and translations on issue trackers. Neura Market summarized a public post by community staffer **Loris Cro** outlining the project's rationale, which emphasizes reviewer bandwidth and contributor training as core concerns. Techzine documented operational problems in the project's continuous integration chain, including a historical bug in a safe_sleep.sh script and scheduling unpredictability in GitHub Actions that the foundation says contributed to the migration decision. ### Industry context Editorial analysis: Projects with small core review teams often face a pull-request-to-reviewer bottleneck; public reporting frames Zig's policy as a response to that dynamic rather than a technical indictment of generative models alone. Industry reporting also highlights tension between downstream projects - for example, the Bun runtime - and Zig: Neura Market notes Bun's maintainers decided not to upstream an AI-assisted performance patch into Zig because of the ban, and that Bun was acquired by **Anthropic** in December 2025. ### Implications for open-source governance Editorial analysis: Reporting places Zig's move in a broader pattern where maintainer decisions about permissible tooling shape contributor onboarding and forking behavior. Observers will read this as an explicit governance choice that prioritizes reviewer-mediated contributor development over accommodating AI-augmented workflows. ### What to watch - •Community reaction and contributor churn on Zig and forks, as visible in mailing lists, issue trackers, and Codeberg activity. - •Whether other mid-sized language projects adopt similar blanket bans or codify more granular AI-use rules; coverage so far is limited to Zig's public posts and reporting in Neura Market and Business Insider. - •Hosting and CI vendor responses, particularly how GitHub and alternatives like Codeberg adjust feature sets and commercial integrations in response to project-level pushback. ### Summary takeaway Editorial analysis: For practitioners, the Zig case is a concrete example of how norms around AI-assisted coding can be enforced at the project level, affecting contributor workflows, upstream/downstream relationships, and the choice of code-hosting infrastructure. The story does not assess the technical merits of specific LLM outputs beyond maintainers' reported experiences; sources cited include Business Insider, Techzine, and Neura Market. ## Scoring Rationale This is a notable governance decision with practical implications for open-source contributors and downstream projects, but it is not a sector-wide technical breakthrough. The score reflects its relevance to maintainers, contributors, and code-hosting providers. Practice interview problems based on real data 1,500+ SQL & Python problems across 15 industry datasets — the exact type of data you work with. [Try 250 free problems](/problems)