Read 2026-11-03
spinframework/spin: technical due diligence, read from its repository
What Borehole read in spinframework/spin's code and history at 69902f1: 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 | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
README.md:136: names CNCF
Architecture & Codebase — including AI provenance
strongcrates/oci/src/client.rs is 1,961 lines, 18× this codebase's median file
adequateThe median source file here is 104 lines. 10 files exceed 1,040 lines, the largest being 1,961. 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/oci/src/client.rs:1 — 1,961 lines (18× median) |
crates/factor-wasi/src/wasi_2023_10_18.rs:1 — 1,860 lines (17× median) |
crates/capabilities/deny-adapter/src/lib.rs:1 — 1,786 lines (17× median) |
crates/factor-wasi/src/wasi_2023_11_10.rs:1 — 1,611 lines (15× median) |
crates/outbound-networking-config/src/allowed_hosts.rs:1 — 1,467 lines (14× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate18% of bug fixes add or change a test
adequateOf 87 fixes in the last 24 months, 16 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.
| 16 of 87 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v4.2.6, is not on the branch this survey read; the newest release on it is v1.3.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v4.2.6 |
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.
cross/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate19 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/build.yml:203 — action pinned by tag |
.github/workflows/build.yml:210 — action pinned by tag |
39 locked dependencies have published vulnerabilities, 6 high or critical
adequate39 of 1,173 locked dependencies match 70 published advisories in OSV, 6 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.
Cargo.lock — zip 1.1.4: GHSA-m665-v7pm-7grj (critical), fixed in 9.0.5 |
Cargo.lock — gix-fs 0.18.2: GHSA-f89h-2fjh-2r9q (high), fixed in 0.21.1 |
Cargo.lock — gix-validate 0.10.1: GHSA-p3hw-mv63-rf9w (high), fixed in 0.11.1 |
68 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
src/commands/deps/source.rs — 1 tracked files, no licence file |
wit/deps/cli-2023-10-18 — 7 tracked files, no licence file |
wit/deps/cli-2023-11-10 — 7 tracked files, no licence file |
wit/deps/cli.wit — 1 tracked files, no licence file |
wit/deps/cli@0.2.0 — 7 tracked files, no licence file |
wit/deps/cli@0.2.3 — 7 tracked files, no licence file |
1 advisory against this project in the last 24 months
adequateThe newest was published on 2026-02-26. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 1.3.0. Answer lives in: the release you run, set against each fixed version.
| 2026-02-26: GHSA-mv4f-6ffm-32wx (moderate), fixed in 3.6.1: Memory leaks in various WIT interfaces |
Observability & Operations
adequateOne request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on spinframework/spin: 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.