Read 2026-11-03
orchestratorinc/agent-orchestrator: technical due diligence, read from its repository
What Borehole read in orchestratorinc/agent-orchestrator's code and history at b325d24: 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 | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:75: The project does not take pull requests- Releases are cut from another branch than the one surveyed
.gitmodules:1: 1 submodule(s) this survey does not read: private/ao-cloud
Architecture & Codebase — including AI provenance
strongfrontend/src/api/schema.ts is 24,382 lines, 227× this codebase's median file
adequateThe median source file here is 107 lines. 88 files exceed 1,070 lines, the largest being 24,382. 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.
frontend/src/api/schema.ts:1 — 24,382 lines (227× median) |
packages/cloud-client/src/schema.ts:1 — 8,764 lines (81× median) |
backend/internal/session_manager/manager.go:1 — 7,415 lines (69× median) |
frontend/src/main/browser-view-host.ts:1 — 6,617 lines (61× median) |
frontend/src/renderer/components/chat/ChatWorkspace.tsx:1 — 5,847 lines (54× median) |
Engineering Process & SDLC Maturity
adequate8% of recent commits change more than 2,000 lines
adequate276 of 3320 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.
| 276 commits over 2,000 lines |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v0.14.8, is not on the branch this survey read; the newest release on it is v0.14.4. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.14.8 |
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.
experiments/remote-browser-poc/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate1 third-party CI action is referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 1 step pipes a download straight into a shell. 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/go.yml:252 — action pinned by tag |
scripts/bootstrap-self-hosted.sh:6 — download piped into a shell |
2 outbound calls can wait forever
adequate2 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/internal/cli/remote_host_link.go:180 — outbound call without a timeout |
backend/internal/daemon/usage_pricing.go:43 — outbound call without a timeout |
1 SQL statement built from strings
adequate1 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
backend/internal/storage/sqlite/store/telemetry_store.go:86 — SQL built from a string |
28 locked dependencies have published vulnerabilities, 28 high or critical in what ships
adequate28 of 1,308 locked dependencies match 78 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.
frontend/package-lock.json — dompurify 3.4.14: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
frontend/package-lock.json — seroval 1.5.4: GHSA-p6vx-979v-rg4c (critical), fixed in 1.6.2 |
packages/mobile/package-lock.json — shell-quote 1.10.0: GHSA-pqg4-j6r4-53mv (critical), fixed in 1.11.0 |
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 orchestratorinc/agent-orchestrator: 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.