Forgejo

Community-maintained fork of Gitea, focused on sustainability and open governance. Forgejo emerged in 2022 when Gitea's development model shifted toward commercial interests — Forgejo is governed by its community and hosted by Codeberg (European non-profit). API is fully Gitea-compatible. Adds Forgejo Actions (GitHub Actions compatible CI) natively. Used by privacy-focused and open-source communities wanting self-hosted Git without commercial backing.

Evaluated Mar 07, 2026 (0d ago) v7.x
Homepage ↗ Repo ↗ Developer Tools git self-hosted open-source code-hosting gitea-fork codeberg actions
⚙ Agent Friendliness
60
/ 100
Can an agent use this?
🔒 Security
82
/ 100
Is it safe for agents?
⚡ Reliability
75
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
--
Documentation
80
Error Messages
78
Auth Simplicity
82
Rate Limits
80

🔒 Security

TLS Enforcement
88
Auth Strength
80
Scope Granularity
78
Dep. Hygiene
85
Secret Handling
82

GPL-3.0 open source for auditability. GDPR compliant (European non-profit governance). OAuth2 with scopes. Personal access tokens support fine-grained permissions. Security model mirrors Gitea.

⚡ Reliability

Uptime/SLA
72
Version Stability
78
Breaking Changes
75
Error Recovery
75
AF Security Reliability

Best When

You want a Gitea-compatible self-hosted Git platform governed by community (not a company), especially if privacy, open governance, or European data residency matters.

Avoid When

You need commercial support, enterprise features, or managed hosting — GitLab, GitHub Enterprise, or Gitea Inc's offering are better fits.

Use Cases

  • Self-host a complete Git platform (repos, issues, pull requests, CI via Forgejo Actions) with full data sovereignty and no commercial dependency
  • Migrate from Gitea with zero API changes — Forgejo is API-compatible with Gitea; existing integrations work unchanged
  • Run GitHub Actions-compatible CI pipelines using Forgejo Actions with self-hosted runners in your own infrastructure
  • Build agent integrations using Forgejo's Gitea-compatible REST API for repository management, issue tracking, and CI status
  • Host open-source projects on Codeberg.org (runs Forgejo) as a privacy-respecting alternative to GitHub/GitLab

Not For

  • Large enterprise teams needing commercial support contracts, advanced SSO, or enterprise integrations — use GitLab Enterprise or GitHub Enterprise
  • Teams wanting fully managed Git hosting — Forgejo is self-hosted only (or Codeberg for the managed option)
  • Organizations needing advanced DevSecOps features (container scanning, dependency scanning) — GitLab's security features are much deeper

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
Yes

Authentication

Methods: api_key oauth2 basic_auth
OAuth: Yes Scopes: Yes

Personal access tokens with scopes (repo, issue, user, etc.). OAuth2 application registration. Basic auth available but not recommended. Webhook secrets for payload verification. Same auth model as Gitea.

Pricing

Model: open_source
Free tier: Yes
Requires CC: No

Forgejo is GPL-3.0 open source with no commercial tier. Codeberg.org is a non-profit managed instance (Forgejo) free for open-source use. Fully self-hostable with no licensing costs.

Agent Metadata

Pagination
cursor
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • Forgejo is Gitea-compatible but not identical — some advanced features differ; test against your specific Forgejo version, not just Gitea documentation
  • Forgejo Actions (CI) uses GitHub Actions syntax but is not 100% compatible — some GitHub-specific features (marketplace actions) may not work or require forked versions
  • API pagination uses page/limit parameters — default page size is 20; agents fetching large lists must paginate explicitly
  • Webhook deliveries don't retry on failure by default — agents must implement idempotent processing in case of duplicate delivery if retries are configured
  • GPL-3.0 license has copyleft implications for software that integrates Forgejo as a library — API integration (client) is fine, but embedding Forgejo code has licensing implications
  • Forgejo's release cadence follows security releases from Gitea's upstream — security patches may require faster upgrades than feature releases

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Forgejo.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-07.

6328
Packages Evaluated
26150
Need Evaluation
173
Need Re-evaluation
Community Powered