Read 2026-11-03
lifeforge-app/lifeforge: technical due diligence, read from its repository
What Borehole read in lifeforge-app/lifeforge's code and history at 6a82dbf: 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 |
What the repository says
LICENSE:1: The licence is CC-BY-NC-SA-4.0: source available, not open sourceLICENSE: Relicensed: MIT → CC-BY-NC-SA-4.0 (2024-06-12)
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate39% of commit subjects are exact repeats of another subject, and subject length varies by only 39.3 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.
| 100× '25w30' |
| 90× '25w29' |
| 75× '25w31' |
packages/ui/src/components/inputs/ColorInput/ColorPickerModal/components/modals/ChineseTraditionalColorsModal/constants/chinese_colors.ts is 2,180 lines, 36× this codebase's median file
adequateThe median source file here is 59 lines. 2 files exceed 1,000 lines, the largest being 2,180. 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.
packages/ui/src/components/inputs/ColorInput/ColorPickerModal/components/modals/ChineseTraditionalColorsModal/constants/chinese_colors.ts:1 — 2,180 lines (36× median) |
packages/api/src/contract.ts:1 — 1,297 lines (21× median) |
Engineering Process & SDLC Maturity
adequateLittle of the recent change carries a trace of review
adequateIn the last 24 months, 214 of 2,902 commits (7.4%) carry any trace of review: a merge, a pull-request reference, a Reviewed-by or Reviewed-on trailer, a Closes/Fixes reference, a maintainer's sign-off on someone else's change, or a change applied by someone other than its author. That is low but not absent. Review may happen in a workflow this history does not record; a buyer should ask how change is approved before it ships.
| 214 of 2,902 commits in the last 24 months carry review evidence; 7.2% across all 3,286 |
36% of commit subjects say nothing about the change
adequate1,131 of 3,120 subjects are either under twelve characters or one of the standard placeholders — wip, fix, update. The history is therefore not usable for reconstructing why a decision was taken, which is the main thing an inheriting engineer needs it for. It says nothing about code quality and a great deal about how much context transfers with the asset.
| 1,131/3,120 low-content subjects (36.2%) |
| 'hmm' |
| 'hmm' |
| 'hmm' |
| 'hmm' |
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 1,222 tracked files |
Product & Engineering Maturity
adequate4% of bug fixes add or change a test
adequateOf 731 fixes in the last 24 months, 26 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.
| 26 of 731 |
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 1,222 tracked files; 0 present |
2 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.
docker/client/Dockerfile — runs as root |
docker/server/Dockerfile — runs as root |
55 locked dependencies have published vulnerabilities, 72 high or critical in what ships
adequate55 of 2,224 locked dependencies match 167 published advisories in OSV, 88 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.
pnpm-lock.yaml — dompurify 3.4.12: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
pnpm-lock.yaml — form-data 2.3.3: GHSA-fjxv-7rqg-78g4 (critical), fixed in 2.5.4 |
pnpm-lock.yaml — jspdf 3.0.4: GHSA-f8cm-6447-x5h2 (critical), fixed in 4.0.0 |
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
packages/configs/vite.config.ts:23 — source maps in a production build |
The licence is CC-BY-NC-SA-4.0: source available, not open source
adequateLICENSE grants CC-BY-NC-SA-4.0: source available, not open source; commercial use not allowed. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
LICENSE:1 — 438 lines, CC-BY-NC-SA-4.0 |
Relicensed: MIT → CC-BY-NC-SA-4.0 (2024-06-12)
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
adequateOne 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 |
The code branches on the environment's name at 18 places
adequate18 places outside configuration test whether they are running in production or staging. Staging then does not exercise production's code, and each deploy is the first run of those branches. Differences belong in configuration the code reads, not in the code.
apps/api/src/core/routes/index.ts:66 — branch on the environment name |
packages/module-runtime/src/loader/createModuleLoader.ts:10 — branch on the environment name |
packages/module-runtime/src/loader/createModuleLoader.ts:19 — branch on the environment name |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on lifeforge-app/lifeforge: 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.