Codeberg Bans AI Code and Crypto: The Vibe is Over
Every open-source community has that moment. You know the one — where the maintainers gather in a dimly lit room (or a very long Mastodon thread) and decide they've had ENOUGH. For Codeberg, one of the largest Git forges outside the GitHub-GitLab duopoly, that moment came on July 23, 2026, and it went straight for the jugular of two of tech's most controversial subcultures: AI-generated code and cryptocurrency projects.
The German non-profit's membership just passed two landmark motions that make it clear: Codeberg isn't here to be a dumping ground for "vibe-coded" repos or a staging area for your latest NFT marketplace. The votes passed with 358 to 144 — a decisive win that signals where the FLOSS community's heart actually lies when you ask hard questions. And the reasoning? It's way more nuanced (and spicy) than "AI bad, memes good." Let's pop the hood.
The Two Motions That Shook the Forge
Motion One: No Training on Your Data
Codeberg formally committed to never using user data — code, issues, pull requests, any of it — for training LLMs. Their privacy policy already said "we do not want to need your data," and this vote turned that sentiment into organizational bedrock. The association's official stance now reads that they believe generative AI technologies are "incompatible with responsibly creating and maintaining free and open source software." No half-measures, no "we'll revisit this later." Just a line in the sand.
Motion Two: Bye-Bye, Vibe Code
This is the one that's making waves. Codeberg will update its Terms of Use to prohibit what the blog post calls "vibe-coded projects" — repos that are mostly or entirely generated by LLMs with minimal human input. This isn't just a symbolic gesture; it means single-developer, LLM-spammed repos that churn through CI/CD resources and generate massive release binaries for zero users are getting the boot. The post specifically calls out "projects with a single developer and virtually no users consuming as much or even more resources than some of the largest community projects."
In the words of the Codeberg team: "Although often well intentioned, sharing the result of a prompt and calling it 'libre software' does not make the world a better place."
The Real Reason? Money (It's Always Money)
Let's not pretend this is purely ideological. Codeberg laid out a brutal financial reality check that connects the AI boom directly to their server bills:
- Hardware prices have gone insane. The SSDs Codeberg used to buy for 700 euros now cost 3,700 euros — a 428% increase driven largely by AI data center demand swallowing the global supply chain. Good luck budgeting around that when you're running on donations.
- Crawlers are DDoSing them for fun. AI company webcrawlers hit every single page — every issue filter variant, every Git history version, every static file — creating expensive database queries that degrade service for real humans. Codeberg's sysadmins spend more time building bot defenses than shipping cool features.
- Storage is being eaten by ghost projects. Single "vibe-coders" pushing massive LLM-generated repos with multi-GB release binaries consume the same resources as major community-maintained projects — except nobody actually uses or maintains the AI-generated ones. Donation money is literally going to host repos nobody asked for.
And it's not just Codeberg. The post connects the dots to a broader digital divide: hardware inflation from AI demand is making it harder for small NGOs, co-ops, and research projects to afford basic hosting. In Frankfurt, data centers now consume 40% of local electricity. Communities near server farms face rising water and energy costs. The externality train has left the station, and we're all on board whether we bought a ticket or not.
The Collaboration Crisis Nobody's Talking About
Codeberg's most striking argument isn't about costs — it's about trust. The post describes how LLMs are creating a "multidimensional attack on the trust between contributors":
- Review burnout: Well-meaning contributors submit AI-generated patches that maintainers have to spend hours reviewing and fixing. It looks like contribution, but it's actually a tax on human volunteers' time.
- License laundering: Copyleft code gets stripped of its GPL/AGPL requirements by being "regenerated" through an LLM, effectively laundering the license. Lawyers, start your engines.
- Gaslighting by algorithm: People who put genuine effort into analyzing issues get accused of being AI slop-peddlers, while real AI users learn to hide their traces better. The result? Everyone trusts no one.
- The vicious cycle: As collaboration gets harder and less rewarding, more developers retreat to "vibecoding" one-off tools that solve their immediate need and rot forever — which makes the commons worse for everyone left.
Codeberg's term "vicious cycle" is chillingly accurate. The more we let LLMs replace collaborative development, the less incentive there is to build together — and the open-source ecosystem is collaboration. Remove that, and you've got a graveyard of single-use scripts nobody understands, maintains, or trusts.
What This Actually Means
Before the pitchforks come out: Codeberg isn't planning a mass purge. They're not hiring a moderation army to hunt down every AI-assisted commit. The new Terms of Use are a signal — a compass, not a guillotine. They'll operationalize the rules gradually, starting with the most egregious cases.
What's safe: Using LLMs as a tool in your workflow while maintaining meaningful human oversight and community. If you're a real developer who occasionally asks ChatGPT to write a regex or refactor a function, you're fine. This is about projects where the human element is absent — the repo that exists because someone typed "build a Twitter clone in Rust" and hit deploy.
What's not: Crypto projects that drain CI/CD minutes, single-developer repos with 10GB release binaries and zero stars, and anything that looks like it was extruded from a prompt without ever being looked at by a human who understands it.
The post also gently points vibe-coders toward "other places that better fit your needs" — which is Codeberg's polite German way of saying "please go somewhere else."
The Takeaway
Codeberg's vote is a canary in the coal mine for the entire open-source ecosystem. We've spent two years celebrating AI's ability to generate code at unprecedented speed, but we've spent almost zero time asking who pays for the storage, the bandwidth, the review time, and the communal trust that holds it all together.
Codeberg's answer? Human collaboration is the product. Everything else — the git forges, the PRs, the CI/CD pipelines — is just infrastructure to support it. If AI hollows out the collaboration, the infrastructure becomes a museum of abandoned single-use projects.
358 members voted yes. 144 voted no. The rest of the open-source world is watching. What side of history will your forge be on?
Comments