Codeberg, the community-driven open source forge hosted on Gitea, has voted to ban projects generated through “vibe coding” and to block large language model companies from training on its repository data. The votes, held in late July 2026, represent one of the most aggressive stances any open source platform has taken against AI-generated code.
What the Votes Decided
The first vote was a formal statement that Codeberg e.V. should oppose LLM companies using Codeberg-hosted code for training datasets. Members voted overwhelmingly in favor. The second vote targeted vibe-coded projects, which the community defined as code primarily written by AI assistants with minimal human review or understanding.
Codeberg’s governance structure lets paying members vote on platform policy. This is not an administrative decision from the hosting team. It reflects the collective will of a community that has long positioned itself as an ethical alternative to GitHub and other corporate-controlled forges.
Why Codeberg Drew This Line
The core argument is straightforward: open source contributors created their code under licenses meant to benefit the commons, not to train commercial AI models. When LLM companies scrape public repositories, the resulting models can reproduce significant portions of that code. Contributors never consented to their work being used this way.
The vibe coding ban goes further. Codeberg members argue that AI-generated projects flood the platform with low-quality code that no one actually understands or maintains. The community sees this as a form of pollution that degrades the value of the forge for genuine developers.
The Community Reaction
The votes have split the broader open source community. Supporters argue that Codeberg is doing what GitHub refuses to do: protecting contributors from having their work harvested without consent. Critics call the vibe coding ban elitist and worry it sets a precedent for gatekeeping based on how code was produced rather than its quality.
On forums and social media, developers pointed out the practical difficulty of enforcement. How do you prove code was AI-generated? If a developer uses Copilot to suggest lines but reviews and modifies every one, does that count? Codeberg hasn’t published detailed enforcement guidelines yet.
How This Fits Into the Broader AI Code Debate
The open source world has been wrestling with AI for two years. GitHub’s Copilot sparked the initial controversy when it was found reproducing licensed code verbatim. Since then, several projects have added “no AI training” clauses to their licenses. The Linux kernel explicitly banned AI-generated patches submitted without proper attribution.
Codeberg’s move is different because it targets the platform level rather than individual projects. A hosting forge banning an entire category of code is unprecedented. It raises questions about what role forges should play in curating what gets hosted.
Other forges have not followed suit. GitLab and GitHub continue to offer enterprise AI features, and smaller platforms like Gitea and Forgejo have not adopted similar policies.
Frequently Asked Questions
What is vibe coding?
Vibe coding refers to using AI assistants like ChatGPT, Claude, or GitHub Copilot to write most or all of the code for a project, with the developer providing prompts and direction rather than writing code themselves.
Why did Codeberg ban vibe-coded projects?
Codeberg members voted to ban these projects because they believe AI-generated code without human understanding and review degrades the quality of the platform and produces unmaintainable software.
Can I still use AI coding assistants on Codeberg?
The ban targets projects that are primarily AI-generated. Using AI tools to assist your work while maintaining understanding and control over the code is not the same as fully vibe-coded projects.
What is Codeberg?
Codeberg is a community-driven, nonprofit alternative to GitHub, hosted on the open source Gitea platform. It positions itself as an ethical hosting service for open source projects.
