Read 2026-10-23
getpaseo/paseo: technical due diligence, read from its repository
What Borehole read in getpaseo/paseo's code and history at ca894d4: 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 | adequate |
| Engineering Process & SDLC Maturity | adequate |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:58: The project does not take pull requestsLICENSE: Relicensed: MIT → AGPL-3.0 (2026-02-25) → Apache-2.0 (2026-08-27)
Architecture & Codebase — including AI provenance
adequatepackages/server/src/server/session.ts is 8,821 lines, 90× this codebase's median file
adequateThe median source file here is 98 lines. 87 files exceed 1,000 lines, the largest being 8,821. 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.
packages/server/src/server/session.ts:1 — 8,821 lines (90× median) |
packages/protocol/src/messages.ts:1 — 7,741 lines (78× median) |
packages/server/src/server/agent/providers/codex-app-server-agent.ts:1 — 7,643 lines (77× median) |
packages/client/src/daemon-client.ts:1 — 7,408 lines (75× median) |
packages/server/src/server/agent/providers/claude/agent.ts:1 — 6,802 lines (69× median) |
1 model weight file committed directly to git
adequate1 model weight files are stored in git itself, not in LFS, DVC or a model hub. Every clone carries them, the history keeps every version for good, and nothing records which run or data produced them.
packages/server/src/server/speech/providers/local/sherpa/assets/silero_vad.onnx — weights in git |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/app/e2e/browser/branch-switcher.spec.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
packages/app/e2e/browser/branch-switcher.spec.ts:47 — test retry |
6% of recent commits change more than 2,000 lines
adequate298 of 4659 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.
| 298 commits over 2,000 lines |
Product & Engineering Maturity
adequate98 direct dependencies in a single manifest
adequatepackages/app/package.json declares 98 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
packages/app/package.json — 98 declared |
packages/server/package.json — 42 declared |
packages/website/package.json — 21 declared |
packages/highlight/package.json — 19 declared |
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.
packages/expo-two-way-audio/.nvmrc — Node.js 20, end of life 2026-04-30 |
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.
docker/base/Dockerfile — runs as root |
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/android-apk-release.yml:96 — action pinned by tag |
.github/workflows/docker.yml:122 — action pinned by tag |
58 locked dependencies have published vulnerabilities, 30 high or critical in what ships
adequate58 of 2,055 locked dependencies match 179 published advisories in OSV, 95 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.
package-lock.json — dompurify 3.4.12: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
packages/expo-two-way-audio/package-lock.json — form-data 3.0.2: GHSA-fjxv-7rqg-78g4 (critical), fixed in 3.0.4; reached only by the build |
packages/expo-two-way-audio/package-lock.json — tar 6.2.1: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19; reached only by the build |
Relicensed: MIT → AGPL-3.0 (2026-02-25) → Apache-2.0 (2026-08-27)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-08-23. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version.
| 2026-08-23: GHSA-2xhx-c69r-qj4j (critical), fixed in >= 0.5.0: Relay E2EE authentication bypass via low-order Curve25519 public key permits remote daemon control |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 5,489 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 5,489 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 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 |
1 of 1 deployed images carry no version, or `latest`
adequate1 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
docker/docker-compose.example.yml:7 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on getpaseo/paseo: 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.