Read 2026-10-23
teambit/bit: technical due diligence, read from its repository
What Borehole read in teambit/bit's code and history at c24e240: 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 | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongscopes/workspace/workspace/workspace.ts is 2,837 lines, 91× this codebase's median file
adequateThe median source file here is 31 lines. 22 files exceed 1,000 lines, the largest being 2,837. 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.
scopes/workspace/workspace/workspace.ts:1 — 2,837 lines (91× median) |
scopes/dependencies/dependency-resolver/dependency-resolver.main.runtime.ts:1 — 2,199 lines (70× median) |
scopes/workspace/install/install.main.runtime.ts:1 — 1,869 lines (60× median) |
scopes/component/isolator/isolator.main.runtime.ts:1 — 1,849 lines (59× median) |
scopes/lanes/lanes/lanes.main.runtime.ts:1 — 1,787 lines (57× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (scopes/mcp/cli-mcp-server/cli-mcp-server.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.
scopes/mcp/cli-mcp-server/cli-mcp-server.spec.ts:226 — test retry |
Product & Engineering Maturity
strongNo finding.
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 3,833 tracked files; 0 present |
3 shell commands built from strings
adequate3 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.
scopes/harmony/api-server/api-server.main.runtime.ts:420 — command run through a shell |
scopes/harmony/api-server/api-server.main.runtime.ts:427 — command run through a shell |
scopes/harmony/global-config/system.cmd.ts:49 — command run through a shell |
76 locked dependencies have published vulnerabilities, 46 high or critical in what ships
adequate76 of 3,956 locked dependencies match 175 published advisories in OSV, 85 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 — shell-quote 1.10.0: GHSA-pqg4-j6r4-53mv (critical), fixed in 1.11.0 |
pnpm-lock.yaml — tar 7.4.3: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19 |
pnpm-lock.yaml — url-parse 1.5.3: GHSA-hgjh-723h-mx2j (critical), fixed in 1.5.8 |
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 teambit/bit: 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.