Read 2026-11-03
paradevai/paradev: technical due diligence, read from its repository
What Borehole read in paradevai/paradev's code and history at 142df44: 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.md:1: The licence is Elastic-2.0: source available, not open sourceLICENSE.md: Relicensed: Apache-2.0 → Elastic-2.0 (2026-02-04)
Architecture & Codebase — including AI provenance
strongpackages/host-service/src/terminal/terminal.ts is 3,923 lines, 130× this codebase's median file
adequateThe median source file here is 30 lines. 47 files exceed 1,000 lines, the largest being 3,923. 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/host-service/src/terminal/terminal.ts:1 — 3,923 lines (130× median) |
apps/desktop/src/renderer/routes/_authenticated/_dashboard/hooks/useProjectIcons/icons.ts:1 — 3,032 lines (101× median) |
packages/db/drizzle/0174_authz_cloud_workspace_functions.sql:1 — 2,873 lines (95× median) |
packages/chat-runtime/src/harness/acp/acpAdapter.ts:1 — 2,731 lines (91× median) |
packages/db/src/schema/schema.ts:1 — 2,607 lines (86× median) |
Engineering Process & SDLC Maturity
adequate9% of recent commits change more than 2,000 lines
adequate437 of 4653 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.
| 437 commits over 2,000 lines |
Product & Engineering Maturity
adequate211 direct dependencies in a single manifest
adequateapps/desktop/package.json declares 211 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
apps/desktop/package.json — 211 declared |
apps/mobile/package.json — 124 declared |
packages/ui/package.json — 64 declared |
apps/marketing/package.json — 43 declared |
Security & Reliability Posture
adequate25 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
The build runs third-party code it does not pin
adequate1 step pipes a download straight into a shell. 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.
apps/marketing/public/cli/install.sh:5 — download piped into a shell |
1 SQL statement built from strings
adequate1 places in product code build SQL by formatting or joining strings rather than passing parameters. 1 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.
packages/cli/src/lib/settings/test-helpers.ts:48 — SQL built from a string |
24 shell commands built from strings
adequate24 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.
packages/sandbox/src/boot-twice.ts:141 — command run through a shell |
packages/sandbox/src/boot-twice.ts:149 — command run through a shell |
packages/sandbox/src/boot-twice.ts:173 — command run through a shell |
5 places insert HTML from a variable without sanitising it
adequate5 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
apps/mobile/plans/acp-vs-claude-sdk.html:2509 — HTML from a variable |
design/automation-create-review/index.html:40 — HTML from a variable |
packages/chat-ui/src/components/MermaidDiagram/MermaidDiagram.tsx:24 — HTML from a variable |
The licence is Elastic-2.0: source available, not open source
adequateLICENSE.md grants Elastic-2.0: source available, not open source; offering it as a managed service is 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.md:1 — 57 lines, Elastic-2.0 |
Relicensed: Apache-2.0 → Elastic-2.0 (2026-02-04)
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.
LICENSE.md — Apache-2.0 from 2025-10-21 |
LICENSE.md — Elastic-2.0 from 2026-02-04 |
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 11,457 files for 10 structured logging libraries; 0 matched |
1 of 4 deployed images carry no version, or `latest`
adequate1 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
docker-compose.yml:44 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on paradevai/paradev: 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.