Read 2026-11-03
wukongim/wukongim: technical due diligence, read from its repository
What Borehole read in wukongim/wukongim's code and history at e753f52: 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 | strong |
| Security & Reliability Posture | strong |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongpkg/db/message/compat.go is 3,951 lines, 27× this codebase's median file
adequateThe median source file here is 146 lines. 18 files exceed 1,460 lines, the largest being 3,951. 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.
pkg/db/message/compat.go:1 — 3,951 lines (27× median) |
internal/app/observability.go:1 — 2,844 lines (19× median) |
pkg/slot/multiraft/slot.go:1 — 2,656 lines (18× median) |
web/src/i18n/messages/en.ts:1 — 2,564 lines (17× median) |
web/src/i18n/messages/zh-CN.ts:1 — 2,562 lines (17× median) |
Engineering Process & SDLC Maturity
adequate6% of recent commits change more than 2,000 lines
adequate299 of 4693 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.
| 299 commits over 2,000 lines |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v1.2.6, is not on the branch this survey read; the newest pre-release on it is v3.0.0-beta.25. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.2.6 |
Security & Reliability Posture
strong1 credential-shaped string added in the history sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| GitHub token, where fakes are usual |
Observability & Operations
strongNo 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 wukongim/wukongim: 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.