Read 2026-10-23
getumbrel/umbrel: technical due diligence, read from its repository
What Borehole read in getumbrel/umbrel's code and history at 11e7f5b: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE.md:1: The licence is PolyForm-Noncommercial-1.0.0: source available, not open sourceLICENSE: Relicensed: Unlicense → MIT (2020-05-29) → CC-BY-NC-ND-4.0 (2020-09-15) → PolyForm-Noncommercial-1.0.0 (2021-08-14)
Architecture & Codebase — including AI provenance
strongpackages/umbreld/source/modules/files/file-index-enrichment.ts is 3,017 lines, 31× this codebase's median file
adequateThe median source file here is 95 lines. 27 files exceed 1,000 lines, the largest being 3,017. 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/umbreld/source/modules/files/file-index-enrichment.ts:1 — 3,017 lines (31× median) |
packages/umbreld/source/modules/apps/app.ts:1 — 2,895 lines (30× median) |
packages/umbreld/source/modules/machines/machines.ts:1 — 2,861 lines (30× median) |
packages/umbreld/source/modules/hardware/raid.ts:1 — 2,539 lines (26× median) |
packages/umbreld/source/modules/files/files.ts:1 — 2,501 lines (26× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/umbreld/source/modules/apps/app-data-root.vm.test.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/umbreld/source/modules/apps/app-data-root.vm.test.ts:50 — test retry |
7% of recent commits change more than 2,000 lines
adequate49 of 719 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.
| 49 commits over 2,000 lines |
Product & Engineering Maturity
adequate91 direct dependencies in a single manifest
adequatepackages/ui/package.json declares 91 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/ui/package.json — 91 declared |
packages/umbreld/package.json — 60 declared |
clients/apple/macos/packaging/pyproject.toml — 1 declared |
Security & Reliability Posture
adequate2 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.
| 2 cited: Google OAuth client secret, where fakes are usual |
None of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 2,204 tracked files; 0 present |
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.
containers/tor/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/ci.yml:124 — action pinned by tag |
.github/workflows/ci.yml:354 — download piped into a shell |
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.
packages/umbreld/source/modules/photos/read-model.ts:116 — SQL built from a string |
32 locked dependencies have published vulnerabilities, 40 high or critical in what ships
adequate32 of 829 locked dependencies match 78 published advisories in OSV, 41 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.
packages/umbreld/package-lock.json — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8 |
packages/umbreld/package-lock.json — sha.js 2.4.11: GHSA-95m3-7q98-8xr5 (critical), fixed in 2.4.12 |
packages/umbreld/package-lock.json — @modelcontextprotocol/server 2.0.0: GHSA-46jr-4wx8-v453 (high), fixed in 2.3.0 |
The licence is PolyForm-Noncommercial-1.0.0: source available, not open source
adequateLICENSE.md grants PolyForm-Noncommercial-1.0.0: source available, not open source; commercial use not allowed. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
LICENSE.md:1 — 133 lines, PolyForm-Noncommercial-1.0.0 |
Relicensed: Unlicense → MIT (2020-05-29) → CC-BY-NC-ND-4.0 (2020-09-15) → PolyForm-Noncommercial-1.0.0 (2021-08-14)
adequateThe root licence changed 3 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
LICENSE — Unlicense from 2020-03-03 |
LICENSE — MIT from 2020-05-29 |
LICENSE — CC-BY-NC-ND-4.0 from 2020-09-15 |
LICENSE.md — PolyForm-Noncommercial-1.0.0 from 2021-08-14 |
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 1,738 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 |
1 of 2 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.
packages/umbreld/source/modules/apps/legacy-compat/docker-compose.app_gateway.yml:6 — 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 getumbrel/umbrel: 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.