Read 2026-11-07
wandb/openui: technical due diligence, read from its repository
What Borehole read in wandb/openui's code and history at 42d7ab4: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongfrontend/src/lib/anysphere.ts is 2,029 lines, 27× this codebase's median file
adequateThe median source file here is 75 lines. 1 file exceed 1,000 lines, the largest being 2,029. 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.
frontend/src/lib/anysphere.ts:1 — 2,029 lines (27× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate9 test files against 104 source files (8.7%). 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.
| 9 test files / 104 source files |
Nothing in the history is tagged as a release
adequateAcross 2.3 years of history there is not one tag. There may still be a deployment process, but this repository holds no record of what shipped when — which is the record a buyer needs to reconstruct an incident or a regression after the fact.
| 0 tags across 209 commits and 835 days |
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (frontend/playwright.config.ts). 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.
frontend/playwright.config.ts:20 — test retry |
Product & Engineering Maturity
adequate101 unresolved debt markers, 6.0 per thousand lines
adequateThe codebase carries 101 TODO, FIXME, HACK or XXX markers across 16,970 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.
backend/openui/__main__.py:41 — # TODO: only render in interactive mode? |
backend/openui/__main__.py:109 — # TODO: hot reload wasn't working with the server approach, and ctrl-C doesn't |
backend/openui/eval/dataset.py:10 — # TODO: Maybe use this for finetuning |
backend/openui/eval/evaluate_weave.py:105 — # TODO: share with scoring model |
backend/openui/eval/evaluate_weave.py:167 — # TODO: lame |
Effort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.17 to 0.98 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.17, second half 0.98 (split 2025-05-09) |
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.
backend/Dockerfile — runs as root |
1 environment file is committed
adequate.env is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
.env — committed environment file |
53 locked dependencies have published vulnerabilities, 25 high or critical in what ships
adequate53 of 1,494 locked dependencies match 132 published advisories in OSV, 68 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.
backend/uv.lock — gitpython 3.1.44: GHSA-284h-m62q-gf8w (critical), fixed in 3.1.59 |
backend/uv.lock — litellm 1.63.11: GHSA-4xpc-pv4p-pm3w (critical), fixed in 1.84.0; an optional extra |
backend/uv.lock — pillow 11.2.1: GHSA-332p-7hrc-92wf (critical), fixed in 13.0.0; an optional extra |
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 149 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 2 deployed images carry no version, or `latest`
adequate1 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
docker-compose.yaml:4 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on wandb/openui: 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.