Read 2026-10-28
200ok-ch/organice: technical due diligence, read from its repository
What Borehole read in 200ok-ch/organice's code and history at 89e52d1: 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 | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: Unlicense → AGPL-3.0 (2019-08-23)
Architecture & Codebase — including AI provenance
adequatesrc/reducers/org.js is 2,324 lines, 22× this codebase's median file
adequateThe median source file here is 103 lines. 3 files exceed 1,030 lines, the largest being 2,324. 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.
src/reducers/org.js:1 — 2,324 lines (22× median) |
src/lib/org_utils.js:1 — 1,315 lines (12× median) |
src/components/OrgFile/index.js:1 — 1,059 lines (10× median) |
1 base image floats: no version, or `latest`
adequate1 of 8 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
contrib/organice-webdav-traefik/webdav/Dockerfile:1 — base image without a version |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (playwright.config.js). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
playwright.config.js:15 — test retry |
Product & Engineering Maturity
adequate176 unresolved debt markers, 4.4 per thousand lines
adequateThe codebase carries 176 TODO, FIXME, HACK or XXX markers across 40,222 lines. These are the team's own notes about work they knew was unfinished. A high density is not automatically bad — it can mean an honest team — but every one of them is a decision deferred, and after an acquisition they are deferred onto someone who was not in the room.
contrib/organice-webdav-post/organice_inbox.sh:19 — echo -e "* TODO $TITLE |
e2e/fixtures.js:34 — // Title of every rendered header in document order, without the TODO |
e2e/helpers/gestures.js:8 — * The header compares absolute x coordinates: a swipe right advances the TODO |
e2e/tests/authenticated/capture-target-sync.spec.js:36 — template: '* TODO %?', |
e2e/tests/authenticated/webdav-mock.spec.js:7 — ** TODO Some task |
Node.js 20 is past end of life
adequateThe code is pinned to Node.js 20 (end of life 2026-04-30). None of these receives security fixes any more; the first stopped on 2026-04-30. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
.nvmrc — Node.js 20, end of life 2026-04-30 |
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 389 tracked files; 0 present |
3 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.
contrib/organice-caddy-webdav/Dockerfile — runs as root |
contrib/organice-pinephone/Dockerfile — runs as root |
contrib/organice-webdav-traefik/webdav/Dockerfile — runs as root |
1 of 1 Kubernetes workloads declare no resource limits
adequate1 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.
contrib/organice-k8s/deployment.yml — workload with no limits |
54 locked dependencies have published vulnerabilities, 77 high or critical
adequate54 of 1,337 locked dependencies match 131 published advisories in OSV, 77 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
Relicensed: Unlicense → AGPL-3.0 (2019-08-23)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 217 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 217 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No 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 217 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 |
1 of 1 deployments run a single replica
adequate1 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.
contrib/organice-k8s/deployment.yml — replicas: 1 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on 200ok-ch/organice: 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.