Codeberg Bans LLM-Generated Code and Cryptocurrency Projects: What Developers Need to Know

Codeberg bans projects that are largely or fully LLM-generated and previously banned cryptocurrency repos — a community-led policy change for open source hosting.

Codeberg, the community-led open source hosting platform, has announced a policy change: projects whose code is largely or fully machine-generated by LLMs and other AI tools will no longer be welcome. This follows an earlier community decision to prohibit cryptocurrency-related projects. The move highlights how community governance is shaping the rules for open source hosting.

The decision emerged from a community vote addressing two separate issues: cryptocurrency projects and machine-generated code. While the crypto ban focused on past concerns about scams and regulatory risk, the LLM-generated code restriction centers on maintainability, code quality, licensing and attribution challenges. Codeberg’s choice underscores growing debates across developer communities about how to integrate AI-generated contributions into open source ecosystems.

Why ban LLM-generated code? Advocates of the policy argue that large amounts of machine-generated code can introduce low-quality or unreviewed code, obscure authorship, and complicate license compliance. Automated outputs may also be used to flood public hosting sites with low-value repositories, increasing moderation burden. By restricting projects that are "largely or fully machine-generated," Codeberg aims to protect repository quality and preserve clear human accountability.

What counts as "largely or fully machine-generated" remains a practical question for maintainers and contributors. Developers who use AI assistants for small snippets, code suggestions, or to speed up routine tasks are unlikely to be impacted if human authorship, review and maintenance remain central. The policy is primarily aimed at repositories whose primary codebase is produced by LLMs without substantial human oversight.

For developers, the policy change offers clear guidance: document code provenance, ensure thorough human review, and comply with license and attribution requirements when AI tools are used. Projects relying heavily on automated generation should consider self-hosting or alternative platforms if they want to continue sharing machine-produced code publicly.

Codeberg’s ban is a reminder that open source hosting is not platform-neutral: community standards, governance models and moderation priorities vary. Developers should follow Codeberg’s official announcements for details and consider how to balance AI tooling with transparency, maintainability and community trust when publishing code.

Back