Gitea
@go-gitea • Git with a cup of tea. Use this route to separate flagship concentration from portfolio breadth before you treat a publisher as broadly strong.
Portfolio concentration
100%
Top three share
Shows whether the organization is driven by one breakout repo or several visible projects.
Breadth
28 repos
Visible snapshot
3 repositories updated in the last 90 days.
Leading language
Go
Portfolio mix
Go (13), HTML (4), Shell (3)
Average size
2.1K
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
Updated: 2026-08-20(6d ago)GitHub API fallback28 repositories
100%
of the visible star count comes from this organization's top three repositories.
2.1K
stars per repository in this same snapshot.
Go
is the most common language here, with 3 repositories updated in the last 90 days.
Why this rank
This organization stands out because one flagship repo drives 99% of its visible star count.
Flagship share 99%Breakout repo: gitea
Organization pages work best when you separate portfolio breadth from flagship concentration. In Gitea's case, the visible top three repositories account for about 100% of total stars in this snapshot, which helps explain whether the organization is known for one breakout project or for a broader repeatable portfolio.
The dominant language mix here is Go (13), HTML (4), Shell (3). That makes this page useful not just for popularity checks, but also for seeing what technical shape an organization's public ecosystem actually has.
Top Repositories
| # | Repository | Language | Stars |
|---|---|---|---|
| 1 | 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 registry and CI/CD | Go | 57.6K |
| 2 | go-gitea/lgtm A simple pull request approval system | Go | 106 |
| 3 | go-gitea/tea A command line tool to interact with Gitea servers, moved to https://gitea.com/gitea/tea | Go | 93 |
| 4 | go-gitea/git A Go module for Git access through shell | Go | 49 |
| 5 | go-gitea/gitea-darkmode Dark Theme for Gitea(DEPRECATED) | CSS | 33 |
| 6 | go-gitea/terraform-provider-gitea Mirror of https://gitea.com/gitea/terraform-provider-gitea | Go | 32 |
| 7 | go-gitea/go-sdk Gitea: Golang SDK, moved to https://gitea.com/gitea/go-sdk | Go | 31 |
| 8 | go-gitea/homebrew-gitea Gitea: Homebrew, moved to https://gitea.com/gitea/homebrew-gitea | Ruby | 21 |
| 9 | go-gitea/theme Gitea: Theme, moved to https://gitea.com/gitea/theme | HTML | 20 |
| 10 | go-gitea/infrastructure Deprecated due to new Gitea.com infra | HCL | 14 |
| 11 | go-gitea/docs Gitea: Docs | Shell | 14 |
| 12 | go-gitea/website Gitea: Website, moved to https://gitea.com/gitea/website | Shell | 13 |
| 13 | go-gitea/blog Gitea: Blog moved to https://gitea.com/gitea/blog | HTML | 10 |
| 14 | go-gitea/changelog Generate changelog of gitea repository, moved to https://gitea.com/gitea/changelog | Go | 8 |
| 15 | go-gitea/test-openldap Docker OpenLDAP Server for testing LDAP applications, moved to https://gitea.com/gitea/test-openldap | Shell | 6 |
| 16 | go-gitea/giteabot A bot to help gitea development | TypeScript | 5 |
| 17 | go-gitea/debian-packaging Debian-style repository for package maintenance. moved https://gitea.com/gitea/debian-packaging | Go | 5 |
| 18 | go-gitea/bolt An embedded key/value database for Go. | Go | 4 |
| 19 | go-gitea/redirects Gitea: Redirects, moved to https://gitea.com/gitea/redirects | Makefile | 4 |
| 20 | go-gitea/test_repo Test repository for testing migration from github to gitea | 3 | |
| 21 | go-gitea/u2f-api U2F API for browsers | JavaScript | 3 |
| 22 | go-gitea/giteabot-old | Go | 2 |
| 23 | go-gitea/yaml YAML support for the Go language. | Go | 1 |
| 24 | go-gitea/chardet A fork of saintfish/chardet. | HTML | 1 |
| 25 | go-gitea/test-giteabot | 0 | |
| 26 | go-gitea/lgtm-docs Documentation for lgtm [DEPRECATED] | HTML | 0 |
| 27 | go-gitea/lgtm-go Go client for lgtm [DEPRECATED] | Go | 0 |
| 28 | go-gitea/lgtm-cli Command line utility for lgtm [DEPRECATED] | Go | 0 |
Next step after the organization read
Open a flagship repository, compare a couple of portfolio leaders, or return to the organization map when you want a broader concentration read.
Learn and methodology
Keep trust-building context reachable, but behind the first data read instead of ahead of it.
How to read this organization snapshot
Total stars are useful as a discovery signal, but they do not tell you whether a team maintains every repository equally. Pair this page with release cadence, maintainer activity, and the flagship concentration shown above before making adoption decisions.
For broader background on GitStar's ranking logic and editorial guidance, see Methodology & Editorial Standards.