Read 2026-10-04
go-gitea/gitea: technical due diligence, read from its repository
What Borehole read in go-gitea/gitea's code and history at 9e7b302: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
AGENTS.md:7: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongrouters/api/v1/repo/action.go is 2,197 lines, 25× this codebase's median file
adequateThe median source file here is 87 lines. 23 files exceed 1,000 lines, the largest being 2,197. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
routers/api/v1/repo/action.go:1 — 2,197 lines (25× median) |
routers/api/v1/shared/project.go:1 — 2,114 lines (24× median) |
routers/api/v1/api.go:1 — 1,949 lines (22× median) |
routers/web/web.go:1 — 1,824 lines (20× median) |
services/gitdiff/gitdiff.go:1 — 1,722 lines (19× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate105 direct dependencies in a single manifest
adequatego.mod declares 105 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
go.mod — 105 declared |
package.json — 59 declared |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v1.27.3, is not on the branch this survey read; the newest release on it is v1.10.5. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.27.3 |
Security & Reliability Posture
adequate1 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
Dockerfile — runs as root |
54 SQL statements built from strings
adequate54 places in product code build SQL by formatting or joining strings rather than passing parameters. 2 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.
models/actions/run_job_summary.go:154 — SQL built from a string |
models/actions/run_job_summary.go:163 — SQL built from a string |
modelmigration/base/db.go:92 — SQL built from a string |
13 locked dependencies have published vulnerabilities, 6 high or critical in what ships
adequate13 of 1,279 locked dependencies match 33 published advisories in OSV, 24 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version.
pnpm-lock.yaml — braces 3.0.3: GHSA-vfj7-8cjw-p6xm (high) |
pnpm-lock.yaml — form-data 4.0.5: GHSA-hmw2-7cc7-3qxx (high), fixed in 4.0.6 |
pnpm-lock.yaml — js-yaml 4.2.0: GHSA-2883-xcg3-v3hh (high), fixed in 4.3.2 |
35 places insert HTML from a variable without sanitising it
adequate35 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
web_src/js/components/ContextPopup.vue:43 — HTML from a variable |
web_src/js/components/DiffFileTreeItem.vue:33 — HTML from a variable |
web_src/js/components/DiffFileTreeItem.vue:48 — HTML from a variable |
144 advisories against this project in the last 24 months, 57 high or critical, 1 on CISA's known-exploited list
adequate1 of them is on CISA's known-exploited list: check first whether the release you run has the fix. The newest was published on 2026-09-29. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. GO-2026-6433 (critical), GHSA-qg66-h68v-5x2h (low), GHSA-m78w-jjjx-gp8r (high) and 38 more are fixed in the surveyed commit; which release carries them cannot be told from this history, which does not place the release users run. Answer lives in: the version you run. The record is incomplete: NVD: 5 records name gitea with nothing tying them to this repository (CVE-2019-10330, CVE-2022-46685, CVE-2026-58053, …).
| 2026-07-28: GO-2026-6433 (critical; on CISA's Known Exploited list), fixed in 1.27.1: Gitea: Remote Code Execution via diffpatch Git Hook Installation in gitea.dev |
| 2026-09-29: GHSA-qg66-h68v-5x2h (low), fixed in 1.27.0: Arbitrary File Read via Path Traversal in gitea restore-repo |
| 2026-09-22: GHSA-m78w-jjjx-gp8r (high), fixed in 1.27.3: Public-only tokens can read private head repositories via compare and pull request creation (incomplete fix of CVE-2026-58443) |
| 2026-09-22: GHSA-m984-2424-x6vw (low), fixed in 1.27.0: Generic attachment downloads bypass draft-release visibility checks |
| 2026-08-29: GHSA-frpv-2xgv-wxpq (moderate), fixed in 1.27.3: Attachments created before the January 2026 cutoff skip the cross repository check entirely, and permission is then evaluated against the repository named in th |
Observability & Operations
strongNo error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on go-gitea/gitea: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.