Read 2026-11-03
spacedriveapp/spacedrive: technical due diligence, read from its repository
What Borehole read in spacedriveapp/spacedrive's code and history at 26b57e1: 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 | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
LICENCE: Relicensed: GPL-3.0 → AGPL-3.0 (2022-07-02) → FSL-1.1-ALv2 (2026-04-14) → Apache-2.0 (2026-08-21)
Architecture & Codebase — including AI provenance
strongcore/src/ops/indexing/volume_index.rs is 5,313 lines, 50× this codebase's median file
adequateThe median source file here is 105 lines. 36 files exceed 1,050 lines, the largest being 5,313. 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.
core/src/ops/indexing/volume_index.rs:1 — 5,313 lines (50× median) |
core/src/service/sync/peer.rs:1 — 3,170 lines (30× median) |
core/src/service/network/protocol/pairing/mod.rs:1 — 2,631 lines (25× median) |
core/src/volume/manager.rs:1 — 2,555 lines (24× median) |
core/src/infra/job/manager.rs:1 — 2,480 lines (23× median) |
Engineering Process & SDLC Maturity
adequate25 tests are switched off
adequate25 skip markers across 12 of 133 test files. Each is a failure somebody chose to stop seeing; the question is whether anyone is tracking them.
core/tests/cross_device_copy_test.rs:24 — skipped test |
core/tests/cross_device_copy_test.rs:253 — skipped test |
core/tests/device_pairing_test.rs:19 — skipped test |
12% of recent commits change more than 2,000 lines
adequate206 of 1739 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.
| 206 commits over 2,000 lines |
Product & Engineering Maturity
adequateNode.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.
.node-version — Node.js 20, end of life 2026-04-30 |
10% of bug fixes add or change a test
adequateOf 242 fixes in the last 24 months, 25 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 25 of 242 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, 0.4.3, is not on the branch this survey read; the newest pre-release on it is v2.0.0-alpha.2. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 0.4.3 |
Security & Reliability Posture
adequate222 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
The build runs third-party code it does not pin
adequate14 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; 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/cache-factory.yaml:62 — action pinned by tag |
.github/workflows/ci.yml:50 — action pinned by tag |
apps/server/Dockerfile:29 — download piped into a shell |
83 locked dependencies have published vulnerabilities, 30 high or critical
adequate83 of 1,936 locked dependencies match 128 published advisories in OSV, 30 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.
core/Cargo.lock — failure 0.1.8: GHSA-jq66-xh47-j9f3 (critical) |
Cargo.lock — zip 4.6.1: GHSA-m665-v7pm-7grj (critical), fixed in 9.0.5 |
core/Cargo.lock — aws-lc-sys 0.29.0: GHSA-65p9-r9h6-22vj (high), fixed in 0.38.0 |
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.
apps/web/vite.config.ts:99 — source maps in a production build |
The app allows plain HTTP to any server
adequateThe app's manifest allows unencrypted HTTP app-wide (NSAllowsArbitraryLoads, or cleartext traffic permitted), rather than for named domains. Anything sent over plain HTTP can be read on the network, and enterprise security reviews ask about it. Some apps need it by nature (a podcast or feed reader fetches whatever URL a feed gives), so ask which case this is.
apps/mobile/android/app/src/debugOptimized/AndroidManifest.xml:6 — cleartext allowed app-wide |
Relicensed: GPL-3.0 → AGPL-3.0 (2022-07-02) → FSL-1.1-ALv2 (2026-04-14) → Apache-2.0 (2026-08-21)
adequateThe root licence changed 3 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
Observability & Operations
not assessableNo 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 spacedriveapp/spacedrive: 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.