Read 2026-10-28
hkuds/nanobot: technical due diligence, read from its repository
What Borehole read in hkuds/nanobot's code and history at 8f7a7d1: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongwebui/src/components/thread/ThreadComposer.tsx is 3,448 lines, 26× this codebase's median file
adequateThe median source file here is 132 lines. 28 files exceed 1,320 lines, the largest being 3,448. 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.
webui/src/components/thread/ThreadComposer.tsx:1 — 3,448 lines (26× median) |
webui/src/App.tsx:1 — 3,255 lines (24× median) |
nanobot/channels/feishu/runtime.py:1 — 2,904 lines (22× median) |
nanobot/agent/loop.py:1 — 2,761 lines (20× median) |
tui/src/app/app.ts:1 — 2,652 lines (20× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate4 credential-shaped strings in the tree 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.
| AWS access key, where fakes are usual |
| 3 cited: Slack token, where fakes are usual |
1 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 |
4 SQL statements built from strings
adequate4 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.
nanobot/session/sqlite_store.py:495 — SQL built from a string |
nanobot/session/display_history.py:127 — SQL built from a string |
nanobot/session/display_history.py:134 — SQL built from a string |
3 locked dependencies have published vulnerabilities, 1 high or critical in what ships
adequate3 of 271 locked dependencies match 3 published advisories in OSV, 1 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.
webui/package-lock.json — source-map-js 1.2.1: GHSA-68fv-2mgg-jv7q (high), fixed in 1.2.2 |
webui/package-lock.json — prismjs 1.27.0: GHSA-x7hr-w5r2-h6wg (moderate), fixed in 1.30.0 |
webui/package-lock.json — katex 0.16.45: GHSA-238p-pmpm-9mq7 (low), fixed in 0.18.2 |
16 advisories against this project in the last 24 months, 8 high or critical
adequateThe newest was published on 2026-09-16. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 10 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 0.4.0. Answer lives in: the release you run, set against each fixed version.
| 2026-09-16: CVE-2026-92576 (critical): HKUDS nanobot before 0.3.0 contains a server-side request forgery vulnerability in the WebFetchTool component where the _validate_url() function fails to block |
| 2026-09-14: CVE-2026-90808 (moderate): A vulnerability was determined in HKUDS nanobot up to 0.2.1. Impacted is the function ExecTool._guard_command/ExecTool._spawn of the file nanobot/agent/tools/sh |
| 2026-09-14: CVE-2026-90809 (moderate): A vulnerability was identified in HKUDS nanobot up to 0.2.1. The affected element is the function ExecTool._guard_command/ExecTool._spawn of the file nanobot/ag |
| 2026-09-02: GHSA-vc5v-6vwm-wf9m (critical), fixed in 0.3.0: ZDI-CAN-29369: Hong Kong University Data Intelligence Lab nanobot WebFetch Server-Side Request Forgery Information Disclosure Vulnerability |
| 2026-08-07: CVE-2026-19243 (low): A security vulnerability has been detected in HKUDS nanobot up to 0.2.1. Impacted is the function ExecTool._guard_command/ExecTool._spawn of the file nanobot/ag |
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 2,208 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 hkuds/nanobot: 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.