Borehole · Project · free tier
openhealthforall/open-health
Free reading: not for reliance
095fdc7 · 275 commits · 157 files
Read 2026-11-07

openhealthforall/open-health: technical due diligence, read from its repository

What Borehole read in openhealthforall/open-health's code and history at 095fdc7: 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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturityadequate
Product & Engineering Maturitystrong
Security & Reliability Postureadequate
Observability & Operationsadequate
Fit with the Acquirernot assessable

Architecture & Codebase — including AI provenance

strong
01.6

src/lib/health-data/parser/schema.ts is 2,515 lines, 61× this codebase's median file

adequate

The median source file here is 41 lines. 2 files exceed 1,000 lines, the largest being 2,515. 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.

Evidence
src/lib/health-data/parser/schema.ts:1 — 2,515 lines (61× median)
src/components/source/source-add-screen.tsx:1 — 1,424 lines (34× median)

Engineering Process & SDLC Maturity

adequate
02.3

Tests are absent or token

adequate

0 test files against 102 source files (0.0%). 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.

Evidence
0 test files / 102 source files

Product & Engineering Maturity

strong

No finding.

Security & Reliability Posture

adequate
05.2

None of the standard security guard rails are configured

adequate

There 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.

Evidence
checked 5 kinds of guard rail across 157 tracked files; 0 present
05.65

1 advisory against this project in the last 24 months, 1 high or critical

adequate

The newest was published on 2026-10-15. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 0.2.0. Answer lives in: the release you run, set against each fixed version.

Evidence
2026-10-15: CVE-2026-111312 (critical): OpenHealth through 0.2.0 contains a missing authentication and authorization vulnerability in the /api/health-data/[id] GET, PATCH and DELETE handlers that quer

Observability & Operations

adequate
06.2

No structured logging library is in use

adequate

Nothing 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.

Evidence
searched 137 files for 10 structured logging libraries; 0 matched
06.8

One request cannot be followed through the logs

adequate

Nothing 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.

Evidence
no request id, correlation id or tracing found
06.9

No error reporter is wired in

adequate

Nothing 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.

Evidence
no error reporter initialised

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on openhealthforall/open-health: 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.