Read 2026-10-23
haiwen/seafile: technical due diligence, read from its repository
What Borehole read in haiwen/seafile's code and history at af6539c: 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 | adequate |
| Product & Engineering Maturity | not assessable |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
LICENCE.txt: Relicensed: GPL-3.0 → GPL-2.0 (2015-05-28)
Architecture & Codebase — including AI provenance
strongdaemon/repo-mgr.c is 8,879 lines, 63× this codebase's median file
adequateThe median source file here is 140 lines. 9 files exceed 1,400 lines, the largest being 8,879. 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.
daemon/repo-mgr.c:1 — 8,879 lines (63× median) |
daemon/http-tx-mgr.c:1 — 5,313 lines (37× median) |
daemon/sync-mgr.c:1 — 3,336 lines (23× median) |
lib/repo.c:1 — 3,076 lines (21× median) |
common/fs-mgr.c:1 — 2,946 lines (21× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate8 test files against 124 source files (6.5%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 8 test files / 124 source files |
Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 217 tracked files |
Product & Engineering Maturity
not assessableNot rated: only 8 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Security & Reliability Posture
adequateNone of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 217 tracked files; 0 present |
2 shell commands built from strings
adequate2 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
msi/strip-files.py:11 — command run through a shell |
setupwin.py:93 — command run through a shell |
Relicensed: GPL-3.0 → GPL-2.0 (2015-05-28)
adequateThe root licence changed 1 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
LICENCE.txt — GPL-3.0 from 2012-11-05 |
LICENSE.txt — GPL-2.0 from 2015-05-28 |
3 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-03-25. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. The record is incomplete: NVD: 6 records name seafile with nothing tying them to this repository (CVE-2014-5443, CVE-2021-30146, CVE-2023-28873, …).
| 2026-03-25: CVE-2026-30587 (high): Multiple Stored XSS vulnerabilities exist in Seafile Server version 13.0.15,13.0.16-pro,12.0.14 and prior and fixed in 13.0.17, 13.0.17-pro, and 12.0.20-pro, vi |
| 2025-12-04: CVE-2025-41079 (moderate): A stored Cross-Site Scripting (XSS) vulnerability has been found in Seafile v12.0.10. This vulnerability allows an attacker to execute arbitrary code in the vic |
| 2025-12-04: CVE-2025-41080 (moderate): A stored Cross-Site Scripting (XSS) vulnerability has been found in Seafile v12.0.10. This vulnerability allows an attacker to execute arbitrary code in the vic |
Observability & Operations
not assessableNot rated: only 4 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on haiwen/seafile: 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.