Read 2026-10-23
asyncfuncai/deepwiki-open: technical due diligence, read from its repository
What Borehole read in asyncfuncai/deepwiki-open's code and history at 3e0f503: 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 |
Architecture & Codebase — including AI provenance
strongsrc/components/Ask.tsx is 1,428 lines, 16× this codebase's median file
adequateThe median source file here is 85 lines. 4 files exceed 1,000 lines, the largest being 1,428. 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.
src/components/Ask.tsx:1 — 1,428 lines (16× median) |
src/app/[owner]/[repo]/slides/page.tsx:1 — 1,300 lines (15× median) |
src/app/[owner]/[repo]/page.tsx:1 — 1,219 lines (14× median) |
api/clients/dashscope.py:1 — 1,028 lines (12× median) |
Engineering Process & SDLC Maturity
adequateNothing in the history is tagged as a release
adequateAcross 1.5 years of history there is not one tag. There may still be a deployment process, but this repository holds no record of what shipped when — which is the record a buyer needs to reconstruct an incident or a regression after the fact.
| 0 tags across 250 commits and 541 days |
Product & Engineering Maturity
adequateEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.30 to 0.89 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.30, second half 0.89 (split 2026-01-25) |
Node.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.
Dockerfile — Node.js 20, end of life 2026-04-30 |
3% of bug fixes add or change a test
adequateOf 70 fixes in the last 24 months, 2 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 2 of 70 |
Security & Reliability Posture
adequate1 Dockerfile runs 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.
Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate4 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/docker-build-push.yml:47 — action pinned by tag |
.github/workflows/docker-build-push.yml:51 — action pinned by tag |
1 deserialiser that can run code
adequate1 places read data with a deserialiser that executes what it reads (pickle). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
api/clients/dashscope.py:831 — code-executing deserialiser |
19 locked dependencies have published vulnerabilities, 36 high or critical in what ships
adequate19 of 837 locked dependencies match 101 published advisories in OSV, 37 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
uv.lock — anyio 4.9.0: GHSA-82r6-8w77-94w6 (critical), fixed in 4.14.2 |
uv.lock — certifi 2025.4.26: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.19 |
api/poetry.lock — certifi 2026.7.22: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.19 |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 158 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 158 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No 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 158 files for 10 structured logging libraries; 0 matched |
One request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
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 asyncfuncai/deepwiki-open: 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.