Read 2026-11-03
labring/laf: technical due diligence, read from its repository
What Borehole read in labring/laf's code and history at 16aa482: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: BSD-3-Clause → SSPL-1.0 with additional terms (2021-08-27) → Apache-2.0 (2022-05-01)
Architecture & Codebase — including AI provenance
strongweb/src/apis/v1/api-auto.d.ts is 1,726 lines, 29× this codebase's median file
adequateThe median source file here is 59 lines. 5 files exceed 1,000 lines, the largest being 1,726. 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.
web/src/apis/v1/api-auto.d.ts:1 — 1,726 lines (29× median) |
server/src/function-template/function-template.service.ts:1 — 1,715 lines (29× median) |
cli/template/global.d.ts:1 — 1,218 lines (20× median) |
cli/src/api/v1/data-contracts.ts:1 — 1,111 lines (18× median) |
web/src/apis/v1/apps.ts:1 — 1,073 lines (18× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate83 test files against 944 source files (8.8%). 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.
| 83 test files / 944 source files |
Product & Engineering Maturity
strongNode.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.
runtimes/nodejs/Dockerfile — Node.js 20, end of life 2026-04-30 |
16 files still carry code deprecated more than two years ago
adequate16 files were marked deprecated over two years ago and still are, the oldest since Sep 2021. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
packages/database-proxy/src/proxy.ts — deprecated since Sep 2021 |
packages/database-ql/src/regexp/index.ts — deprecated since Oct 2021 |
packages/database-ql/src/serverDate/index.ts — deprecated since Oct 2021 |
packages/database-ql/src/query.ts — deprecated since Oct 2021 |
packages/database-proxy/src/types.ts — deprecated since Oct 2021 |
Security & Reliability Posture
adequate2 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.
server/Dockerfile — runs as root |
web/Dockerfile — runs as root |
2 environment files are committed
adequateweb/.env, web/.env.production are 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.
web/.env — committed environment file |
web/.env.production — committed environment file |
The build runs third-party code it does not pin
adequate9 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/build-sealos-cluster-image.yml:118 — action pinned by tag |
.github/workflows/dockerize-runtime-exporter.yml:75 — action pinned by tag |
5 shell commands built from strings
adequate5 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
runtimes/nodejs/src/init.ts:39 — command run through a shell |
runtimes/nodejs/src/support/module-hot-reload.ts:94 — command run through a shell |
runtimes/nodejs/src/support/module-hot-reload.ts:108 — command run through a shell |
91 locked dependencies have published vulnerabilities, 82 high or critical in what ships
adequate91 of 2,327 locked dependencies match 255 published advisories in OSV, 127 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.
packages/cloud-sdk/package-lock.json — mysql2 2.3.3: GHSA-4rch-2fh8-94vw (critical), fixed in 3.9.7 |
server/package-lock.json — tar 6.1.12: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19 |
runtimes/nodejs/package-lock.json — tar 6.2.0: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19 |
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/client-sdk/webpack.config.js:10 — source maps in a production build |
web/vite.config.ts:64 — source maps in a production build |
Relicensed: BSD-3-Clause → SSPL-1.0 with additional terms (2021-08-27) → Apache-2.0 (2022-05-01)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
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 1,138 files for 10 structured logging libraries; 0 matched |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on labring/laf: 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.