go-gitea/gitea

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package...

View on GitHub ↗Jump to charts ↓Open shareable report →

go-gitea/gitea has 58k+ stars and 7k+ forks on GitHub, is written in Go, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 60 minutes ago
Added to GitGenius on August 31st, 2026
Created on November 1st, 2016
Open Issues & Pull Requests: 2,190 (+1)
GitHub issues: Enabled
Number of forks: 7,286
Total Stargazers: 58,550 (+2)
Total Subscribers: 491 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.9 hours
Mean response time: 116.2 days
90th percentile: 301.3 days
Tracked items: 4,214

Maintainer activity

32 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 10% of issues opened in the past year have never received a reply. 89% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "issue/not-a-bug" is answered fastest, typically in about 2 hours, while "type/feature" waits about 10 days. 56% of tracked open issues have had no activity in three months. 75% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1,053
New in 7 days: 28
Closed in 7 days: 150
Avg open age: 892 days
Stale 30+ days: 957
Stale 90+ days: 798

Recent activity

Opened in 7 days: 24
Closed in 7 days: 147
Comments in 7 days: 182
Events in 7 days: 446

Top labels

  • type/bug (2,053)
  • type/proposal (1,644)
  • issue/needs-feedback (537)
  • topic/ui (361)
  • topic/gitea-actions (292)
  • issue/confirmed (285)
  • type/feature (284)
  • topic/api (225)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Gitea is a self-hosted all-in-one software development service that provides Git hosting, code review, team collaboration, package registry, and CI/CD capabilities.

Gitea addresses the need for organizations to run a complete development platform on their own infrastructure without relying on external services. It consolidates multiple tools—Git hosting, issue tracking, code review, project management, wikis, and continuous integration—into a single application. The tool is written in Go, enabling it to run across diverse platforms and architectures including Linux, macOS, FreeBSD, OpenBSD, and Windows on x86, ARM, RISC-V, and PowerPC systems. Its CI/CD system can reuse GitHub Actions workflows, reducing friction for teams migrating from or working alongside GitHub.

Teams should choose Gitea when they need a lightweight, self-contained alternative to larger platforms like GitLab or when they want to avoid the operational complexity of managing separate services for version control, code review, and CI/CD. It suits organizations of any size that prefer to control their infrastructure and data, from small teams running a single instance to larger deployments. The project provides container images for straightforward deployment and maintains official SDKs and CLI tools for integration and automation.

The project sustains active development with regular contributions across its codebase. The maintainers enforce a structured contribution process requiring contributors to read the contributors guide before submitting pull requests. Documentation is comprehensive and actively maintained in a separate repository, with community involvement encouraged through translation efforts coordinated via a dedicated platform. The project maintains official companion tools and curates a list of third-party extensions, indicating ongoing ecosystem stewardship.