Read 2026-10-23
nextcloud/all-in-one: technical due diligence, read from its repository
What Borehole read in nextcloud/all-in-one's code and history at 27345c7: 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 | adequate |
| Engineering Process & SDLC Maturity | adequate |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
AGENTS.md:16: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
adequateThe repository begins with most of itself already written
adequateThe first commit carries 93,939 lines — 60% of every line ever added. Whatever happened before that commit happened somewhere this repository cannot show you, so the early history is not available as evidence of how the system was designed.
| 2021-11-30T10:20:42+00:00; +93,939 across 884 files; subject: 'Initial import' |
Commit messages are templated rather than written
adequate32% of commit subjects are exact repeats of another subject, and subject length varies by only 20.5 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
| 155× 'php dependency updates' |
| 100× 'Helm Chart updates' |
| 74× 'Yaml updates' |
php/src/Auth/PasswordGenerator.php is 7,803 lines, 260× this codebase's median file
adequateThe median source file here is 30 lines. 4 files exceed 1,000 lines, the largest being 7,803. 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.
php/src/Auth/PasswordGenerator.php:1 — 7,803 lines (260× median) |
php/src/Data/ConfigurationManager.php:1 — 1,312 lines (43× median) |
php/src/Docker/DockerActionManager.php:1 — 1,217 lines (40× median) |
Containers/nextcloud/entrypoint.sh:1 — 1,151 lines (38× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate10 test files against 141 source files (7.1%). 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.
| 10 test files / 141 source files |
Product & Engineering Maturity
adequate5% of bug fixes add or change a test
adequateOf 238 fixes in the last 24 months, 11 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 11 of 238 |
Security & Reliability Posture
adequate10 Dockerfiles run 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.
Containers/alpine/Dockerfile — runs as root |
Containers/borgbackup/Dockerfile — runs as root |
Containers/collabora/Dockerfile — runs as root |
Containers/docker-socket-proxy/Dockerfile — runs as root |
15 of 15 Kubernetes workloads declare no resource limits
adequate15 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.
nextcloud-aio-helm-chart/templates/nextcloud-aio-apache-deployment.yaml — workload with no limits |
nextcloud-aio-helm-chart/templates/nextcloud-aio-clamav-deployment.yaml — workload with no limits |
nextcloud-aio-helm-chart/templates/nextcloud-aio-collabora-deployment.yaml — workload with no limits |
Observability & Operations
adequateNo structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 376 files for 10 structured logging libraries; 0 matched |
One request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
No 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 |
15 of 15 deployments run a single replica
adequate15 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on nextcloud/all-in-one: 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.