Read 2026-10-23
dream-num/univer: technical due diligence, read from its repository
What Borehole read in dream-num/univer's code and history at 8652a07: 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 | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongpackages/engine-formula/src/services/formula/function-list/statistical.ts is 3,069 lines, 31× this codebase's median file
adequateThe median source file here is 97 lines. 98 files exceed 1,000 lines, the largest being 3,069. 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/engine-formula/src/services/formula/function-list/statistical.ts:1 — 3,069 lines (31× median) |
packages/sheets/src/facade/f-range.ts:1 — 3,010 lines (31× median) |
packages/sheets/src/facade/f-worksheet.ts:1 — 2,827 lines (29× median) |
packages/engine-formula/src/engine/analysis/lexer-tree-builder.ts:1 — 2,563 lines (26× median) |
packages/sheets-drawing-ui/src/services/canvas-float-dom-manager.service.ts:1 — 2,533 lines (26× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/core/src/services/config/__tests__/config.service.spec.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.
packages/core/src/services/config/__tests__/config.service.spec.ts:39 — test retry |
6% of recent commits change more than 2,000 lines
adequate133 of 2339 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 133 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate5 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/ci-quality-checks.yml:54 — action pinned by tag |
.github/workflows/dispatch-sync-univer-pro.yml:15 — action pinned by tag |
29 locked dependencies have published vulnerabilities, 40 high or critical in what ships
adequate29 of 1,552 locked dependencies match 111 published advisories in OSV, 63 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 — storybook 10.4.6: GHSA-f2ph-cmg5-wxc8 (critical), fixed in 10.6.2 |
pnpm-lock.yaml — tinypool 2.1.0: GHSA-5gmw-xhrv-c9v3 (critical), fixed in 2.1.1; a development dependency |
pnpm-lock.yaml — @grpc/grpc-js 1.14.4: GHSA-m9gg-hp2v-232j (high), fixed in 1.14.5 |
Observability & Operations
not assessableNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on dream-num/univer: 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.