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
github.com/go-gitea/giteaIndexed at 8a3daefUp to date with upstream
About this codebase
`repo` is a Go-based code hosting and repository services backend that ingests repository content (via filesystem/Git/LFS workflows), transforms it through indexing, routing, and background service pipelines, and produces served HTTP/API responses plus persisted state (database models) and web UI assets.
Written by gpt-5.4-nano from the index
3,783 files and 21,638 symbols in 12 modules, led by Go (2,978 files) and TypeScript (223).
Code health
This codebase scores 7.4 out of 10 for code health, which we rate good. It also scores maintainability 8.3 and static performance 9.8 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 218 of 3,783 files are git hotspots, and they average 4.5 — which is where the fixes pay off most.
On the leaderboards:#3 of 19 Go repos
Do next
4 things worth doing this quarter.
Worth planning
Break up buildUpdateInfo (CCN 16, 65 lines)
services/packages/rpm/repository.go:641
buildUpdateInfo nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy; changed 1 time in 90 days.
- gain
- up to +2.2 health on this file(inferred)
- finding
- Nested complexity
- size
- CCN 16, 65 lines, nests 8 deep
- severity
- critical
Medium effort, worth a checkBreak up UploadErrata (CCN 33, 128 lines)
routers/api/packages/rpm/rpm.go:443
UploadErrata nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy; changed 1 time in 90 days.
- gain
- up to +2.2 health on this file(inferred)
- finding
- Nested complexity
- size
- CCN 33, 128 lines, nests 9 deep
- severity
- critical
Medium effort, worth a checkDelete 181 unused symbols and files (2,793 lines)
Nothing in the graph reaches them, across 128 files; every reader and agent pays to skip them.
- symbols
- 181
- lines
- 2,793
- safe to delete
- Yes(inferred)
Medium effort
Use go-gitea/gitea in your agent
Point Claude Code, Cursor, Codex or VS Code at this repository. Your agent gets the index this page is built from: cited answers, callers, history and health for any file.
https://api.repowise.dev/mcp/go-gitea/giteaOne command, run anywhere. Adds the server to your local Claude Code config.
Docsclaude mcp add --transport http repowise https://api.repowise.dev/mcp/go-gitea/gitea \ --header "Authorization: Bearer rw_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
This repo is public, so anyone with a Repowise account and an API key can connect.
Try asking
- get_overview()
- get_answer("how is gitea put together?")
- get_why("why is gitea structured this way?")
Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed.
Go deeper
- OverviewEverything the index found, what changed this week, commits and decisions.
- DocumentationModule-by-module documentation, 3,134 pages, 710 written by a model.
- ArchitectureDependency graph, layers and third-party dependencies.
- Code healthEvery file's score, the findings behind it, tests and refactoring plans.
- CommitsEach commit's effect on code health, with agent provenance.
- ContributorsWho owns what, and where one person holds most of the knowledge.
- DecisionsArchitectural decisions mined from commits and pull requests.
- Ask this codebaseSign inGrounded answers over the indexed code.
Maintain this repo? Claim the page
Sign in with GitHub and we check that you are an admin or maintainer of go-gitea/gitea. Then add a badge to the README that links readers here.
Use this repo from Claude or ChatGPT
Add this URL as a custom connector and sign in with repowise when asked. No API key to copy.
https://api.repowise.dev/mcp/go-gitea/giteaFor maintainers
Add a badge to your README
Every badge is public, cached, and updates on its own after every index. Nothing to install.
Repowise badge
Links to this page, with no score on it. Adding it also re-indexes the repo every week.
[](https://repowise.dev/repo/go-gitea/gitea?src=badge_wiki)Code health badge
The repo's health score out of 10, from the latest index.
[](https://repowise.dev/repo/go-gitea/gitea?src=badge_health)Code health card
A larger card with the score, its change since the last index, and when it was measured. The HTML version follows the reader's light or dark theme.
[](https://repowise.dev/repo/go-gitea/gitea?src=badge_card)How go-gitea/gitea works
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 This page is a map of the go-gitea/gitea repository, written primarily in Go, rebuilt from the source each time it is indexed. Repowise parses every symbol, computes a dependency graph, scores per-file code health from complexity, duplication, test coverage and churn, mines git history for hotspots and ownership, and lifts the architectural decisions into documentation you can read here or query through MCP.
The codebase has 3,783 files and 21,638 symbols in 12 modules, led by Go, TypeScript and Shell. Code health is 7.4 out of 10, rated good.
Use the links above to open each view, or connect this repository to your agent for grounded answers inside Claude, Cursor, Codex or VS Code.