go-gitea/gitea
Loading…
go-gitea/giteago-gitea/gitea
Repowise · Codebase intelligence
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
Repowise ranks every file by predicted defect risk. Of the 20 files it flags as riskiest, 18 (90%) actually needed a bug fix in the last 6 months — 4.0× better than picking files at random.
cmd/main.godocker/root/etc/s6/gitea/rundocker/root/etc/s6/openssh/runmain.gomodels/actions/run.gomodels/db/index.gomodules/charset/generate/generate.gomodules/graceful/server.gomodules/lfstransfer/main.gomodules/setting/server.gorouters/api/v1/swagger/app.gorouters/api/v1/user/app.goGit 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 an auto-generated, always-fresh map of the go-gitea/gitea repository, written primarily in Go. Repowise indexes the source, 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 resulting architectural decisions into a wiki you can read or query through MCP.
The codebase has 3,743 source files, 21,138 symbols, and 11 languages. Git churn analysis flags 258 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 198 tightly-coupled module communities.
Use the panels above to open the interactive dashboards, or connect this repo to your editor via the Repowise MCP server for grounded answers inside Claude, Cursor, or VS Code.
Files, symbols, languages, packages, git intelligence
Dependency graph, layered architecture, symbol index, and third-party dependencies
Per-file health scores, hotspots, test coverage, dead code, and refactoring targets
Module-by-module documentation generated from source
Change-risk ranked history with AI-agent provenance and hotspots
Bus-factor, per-file maintainer maps, and human/agent collaboration
Architectural decisions extracted from commits and PRs
Ask grounded questions over the indexed code