Read 2026-10-23
chaitin/pandawiki: technical due diligence, read from its repository
What Borehole read in chaitin/pandawiki's code and history at 0b26db7: 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 | strong |
| Fit with the Acquirer | not assessable |
What the repository says
.gitmodules:1: 1 submodule(s) this survey does not read: backend/pro
Architecture & Codebase — including AI provenance
strongweb/admin/src/request/types.ts is 2,171 lines, 44× this codebase's median file
adequateThe median source file here is 49 lines. 8 files exceed 1,000 lines, the largest being 2,171. 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.
web/admin/src/request/types.ts:1 — 2,171 lines (44× median) |
web/app/src/request/types.ts:1 — 2,161 lines (44× median) |
web/admin/src/components/System/component/ModelConfig.tsx:1 — 1,540 lines (31× median) |
backend/repo/pg/node.go:1 — 1,412 lines (28× median) |
web/app/src/components/QaModal/AiQaContent.tsx:1 — 1,239 lines (25× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate6 test files against 1,092 source files (0.5%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 6 test files / 1,092 source files |
Product & Engineering Maturity
adequate1% of bug fixes add or change a test
adequateOf 417 fixes in the last 24 months, 6 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.
| 6 of 417 |
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.
web/admin/Dockerfile — runs as root |
1 environment file is committed
adequateweb/app/.env is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
web/app/.env — committed environment file |
The build runs third-party code it does not pin
adequate6 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/backend.yml:41 — action pinned by tag |
.github/workflows/backend.yml:46 — action pinned by tag |
18 outbound calls can wait forever
adequate18 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
backend/pkg/bot/dingtalk/stream.go:476 — outbound call without a timeout |
backend/pkg/bot/wechat/wechat.go:199 — outbound call without a timeout |
backend/pkg/bot/wechat/wechat.go:235 — outbound call without a timeout |
65 locked dependencies have published vulnerabilities, 56 high or critical in what ships
adequate65 of 1,613 locked dependencies match 177 published advisories in OSV, 76 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.
backend/go.mod — golang.org/x/crypto v0.40.0: GHSA-5cgq-3rg8-m6cv (critical), fixed in 0.52.0 |
web/pnpm-lock.yaml — next 16.0.10: GHSA-2464-fhr4-w9xw (critical), fixed in 16.4.1 |
backend/go.mod — github.com/jackc/pgx/v5 v5.7.4: GHSA-9jj7-4m8r-rfcm (critical), fixed in 5.9.0 |
6 places insert HTML from a variable without sanitising it
adequate6 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.
web/app/src/app/layout.tsx:102 — HTML from a variable |
web/app/src/components/markdown2/incrementalRenderer.tsx:81 — HTML from a variable |
web/app/src/components/markdown2/incrementalRenderer.tsx:90 — HTML from a variable |
Observability & Operations
strongNo finding.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on chaitin/pandawiki: 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.