Read 2026-10-23
deepseek-ai/deepseek-harness: technical due diligence, read from its repository
What Borehole read in deepseek-ai/deepseek-harness's code and history at 22ddee3: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:9: The project does not take pull requests
Architecture & Codebase — including AI provenance
strongpackages/extensions/tool-cordis/src/api-catalog.ts is 9,394 lines, 94× this codebase's median file
adequateThe median source file here is 99 lines. 47 files exceed 1,000 lines, the largest being 9,394. 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/extensions/tool-cordis/src/api-catalog.ts:1 — 9,394 lines (94× median) |
packages/extensions/cordis-client-runner/src/client/slot-catalog.ts:1 — 5,181 lines (52× median) |
packages/client/ui-trajectory/src/client/TrajectoryTable.tsx:1 — 3,539 lines (35× median) |
packages/typert/generator/src/analyzer.ts:1 — 3,469 lines (35× median) |
packages/client/ui-conversation/src/client/locales.ts:1 — 3,064 lines (30× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate156 direct dependencies in a single manifest
adequatepython/sdk-runtime/package.json declares 156 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.
python/sdk-runtime/package.json — 156 declared |
packages/bundle/web-app/package.json — 138 declared |
packages/bundle/base/package.json — 97 declared |
apps/cli/package.json — 89 declared |
Security & Reliability Posture
adequate19 locked dependencies have published vulnerabilities, 3 high or critical in what ships
adequate19 of 1,659 locked dependencies match 83 published advisories in OSV, 43 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.
python/sdk/uv.lock — pillow 12.3.0: GHSA-332p-7hrc-92wf (critical), fixed in 13.0.0; a development dependency |
pnpm-lock.yaml — dompurify 3.4.16: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17; a development dependency |
pnpm-lock.yaml — @modelcontextprotocol/sdk 1.31.0: GHSA-22jm-h49p-29qw (high), fixed in 1.32.0 |
4 places insert HTML from a variable without sanitising it
adequate4 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.
packages/client/ui-primitives/src/CodeFileIcon.tsx:25 — HTML from a variable |
packages/client/ui-primitives/src/markdown/CodeBlock.tsx:184 — HTML from a variable |
packages/client/ui-sidebar-documentpreview/src/client/html/pack.ts:41 — HTML from a variable |
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.
apps/web/vite.config.ts:181 — source maps in a production build |
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 14,868 files for 10 structured logging libraries; 0 matched |
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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on deepseek-ai/deepseek-harness: 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.