go-gitea / gitea
Code health
This codebase scores 8.0 out of 10 for code health, which we rate good. It also scores maintainability 8.7 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.
Do next
1 thing worth doing this quarter.
Worth planning
Delete 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
Improve what Repowise can see
Add a test coverage report
Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.
- line coverage
- Unknown, no report
Small effortReview the 556 proposed decisions
None is accepted yet, so nothing can drift from one and agents get no enforced guidance from them.
- proposed
- 556
- accepted
- 0
Medium effort
- Lines of code
- 512.4K
Recent activity
All commitsCommits
- 8a3daef5fix(repo): stop advertising HTTP clone URLs when DISABLE_HTTP_GIT is set (#38378)2mo ago
- bca44bd7[skip ci] Updated translations via Crowdin2mo ago
- b4e60133ci: retry snap store upload on transient connection drops (#38461)2mo ago
- a49c8938fix(pull): sign the commit when updating a branch by merge (#38441)2mo ago
- 9d3f04ebfix(actions): explain why a blocked or waiting job has not started (#38476)2mo ago
- 2e0aa7ecfix(actions): make `cancelled()` work in job `if` evaluation (#38495)2mo ago
Decisions
- API route parameter optionality and pagination requirementsproposed
- API route parameter optionality rulesproposed
- API v1 documentation and compatibility modelproposed
- Accessibility approach for Fomantic-UIproposed
- Accessibility preference and testing expectationsproposed
- Adapter between internal Status and runner Resultproposed
Everything we found
10,540 open
Every detector's open count by area, each with its worst example. An inventory, not a to-do list: the actions above are the part worth doing.
- worst item is critical severity. Code health6,435Untested hotspot · services/repository/push.go26 findings · 10.4 deducted
- worst item is medium severity. Refactoring1,719BeforeProcess+1.5 health, S effort · models/unittest/fixtures.go
- worst item is medium severity. Decisions774routers/web/repo/actions/actions.go556 awaiting review · 218 hotspots ungoverned
- worst item is medium severity. Ownership1,426eslint.config.ts99% single-owner concentration, 6 commits in 90d
- worst item is low severity. Dead code186CountWrongRepoLevelVariablesUnreachable function (4 lines)
Composition
Open the graphExplore this codebase
- Docs3,134 pages across 12 modules
- ChatAsk this codebase a question and get an answer with its sources.
- Files3,783 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 67 entry points
- Code healthPer-file scores, 8,129 open findings, coverage and refactoring targets
- Knowledge graphEntities, communities, and the paths between them
- Change couplingFiles that keep changing together, mined from commit history
- CommitsChange-risk ranked history with agent provenance
- ContributorsBus factor, per-file maintainers, and the human/agent split
- StatsSize class, origin, lifetime churn, rhythm and records
- CostsWhat indexing this snapshot cost, by model and by run.