Codeberg alternatives
The highest-scoring alternative to Codeberg is GitHub at 55/100 on the AgentReady, against 55/100 for Codeberg.
All scored in Git & Source Control.
| Score | Alternative | Compare |
|---|---|---|
| 55 | GitHub | Codeberg vs GitHub |
| 53 | Bitbucket | Codeberg vs Bitbucket |
| 51 | Gitea | Codeberg vs Gitea |
| 50 | GitLab | Codeberg vs GitLab |
| 45 | Forgejo | Codeberg vs Forgejo |
| 29 | SourceHut | Codeberg vs SourceHut |
What GitHub does that Codeberg does not
GitHub passes clear canonical domain, llms.txt published, llms-full.txt / full agent docs, official typescript sdk, official python sdk, structured, predictable output, rate-limit behavior predictable, and Codeberg fails them. That is the whole of the gap between the two scores, so if none of those matter to your agent the ranking above overstates the difference.
Why people look for an alternative
Codeberg fails clear canonical domain, llms.txt published, llms-full.txt / full agent docs, machine-readable metadata, structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, no mandatory sales call, programmatic credential creation, official typescript sdk, official python sdk, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable. Each one is a place an unattended run stops, which is usually what sends someone looking in the first place.
Where Codeberg loses the points
| Pillar | Codeberg | What it measures |
|---|---|---|
| Discover | 73 | Can an agent find it at all: sitemap, robots, structured data. |
| Understand | 31 | Is there a spec, an llms.txt, a machine-readable description. |
| Adopt | 62 | Signup, keys, SDKs, and whether a human has to be involved. |
| Operate | 53 | Rate-limit headers, errors, status, and behaviour under load. |
Codeberg is weakest on understand at 31/100. Without a spec an agent has to guess at endpoints, and it guesses wrong. If that is the part your agent depends on, take the ranking above seriously; if it is not, Codeberg may still be the right pick.
What an agent runs into with Codeberg
These are the findings from the last audit on 2026-08-25. Each one is a place unattended software stops, which is the practical reason to look at the list above.
- Publish an OpenAPI spec so agents can generate a client.
- Flesh out the OpenAPI: paths, schemas, and descriptions.
- Document error responses as an enum in your OpenAPI.
- Let agents create API keys programmatically.
- Ship an official TypeScript/JavaScript SDK on npm.
- Ship an official Python SDK on PyPI.
- Return X-RateLimit / Retry-After headers so agents pace themselves.
- Add /llms.txt so agents can find and read your capabilities.
What this category actually supports
Across the 7 products scored in Git & Source Control, host a git repo is offered by 71%.
An agent can get this list directly: resolve("alternative to Codeberg") over the MCP server, or GET /v1/categories/git.