Read 2026-10-28
clockworklabs/spacetimedb: technical due diligence, read from its repository
What Borehole read in clockworklabs/spacetimedb's code and history at 5ce9e90: 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 | strong |
| Security & Reliability Posture | adequate |
| 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
adequatecrates/codegen/src/unrealcpp.rs is 7,086 lines, 104× this codebase's median file
adequateThe median source file here is 68 lines. 77 files exceed 1,000 lines, the largest being 7,086. 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.
crates/codegen/src/unrealcpp.rs:1 — 7,086 lines (104× median) |
crates/datastore/src/locking_tx_datastore/mut_tx.rs:1 — 4,899 lines (72× median) |
crates/core/src/subscription/module_subscription_actor.rs:1 — 4,788 lines (70× median) |
crates/core/src/host/module_host.rs:1 — 4,618 lines (67× median) |
crates/datastore/src/locking_tx_datastore/datastore.rs:1 — 4,598 lines (67× median) |
1 base image floats: no version, or `latest`
adequate1 of 8 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
crates/standalone/Dockerfile:35 — base image without a version |
Engineering Process & SDLC Maturity
adequate7% of recent commits change more than 2,000 lines
adequate126 of 1873 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.
| 126 commits over 2,000 lines |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v2.14.0, is not on the branch this survey read; the newest release on it is v2.13.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v2.14.0 |
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.
| 4 cited: JWT, 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.
crates/standalone/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate10 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; 2 steps pipe 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/benchmarks.yml:89 — action pinned by tag |
.github/workflows/check-pr-base.yml:44 — action pinned by tag |
.github/workflows/ci.yml:1716 — download piped into a shell |
104 locked dependencies have published vulnerabilities, 13 high or critical in what ships
adequate104 of 4,433 locked dependencies match 201 published advisories in OSV, 96 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.
pnpm-lock.yaml — @nuxt/devtools 2.7.0: GHSA-279x-mwfv-vcqv (critical), fixed in 3.3.1; reached only by the build |
pnpm-lock.yaml — piscina 5.1.4: GHSA-67c8-pqhq-4rmx (critical), fixed in 5.3.2; a development dependency |
pnpm-lock.yaml — tar 6.2.1: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19; a development dependency |
4 workload settings give a container the host
adequate4 places in the deployment configuration run a container privileged or in the host's network, process or IPC namespace. A compromise of that container is a compromise of the machine, and most acquirers' security reviews block it. Node agents (network, storage, monitoring) are excluded.
templates/keynote-2/cockroachdb/docker-compose-crdb-node-1.yml:14 — privileged or host namespace |
templates/keynote-2/cockroachdb/docker-compose-crdb-node-1.yml:21 — privileged or host namespace |
templates/keynote-2/cockroachdb/docker-compose-crdb-node-2.yml:19 — privileged or host namespace |
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
templates/angular-ts/angular.json:45 — source maps in a production build |
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 |
2 of 3 deployed images carry no version, or `latest`
adequate2 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.
templates/keynote-2/docker-compose.yml:21 — image without a version |
templates/keynote-2/docker-compose.yml:200 — 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 clockworklabs/spacetimedb: 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.