Read 2026-11-03
arroyosystems/arroyo: technical due diligence, read from its repository
What Borehole read in arroyosystems/arroyo's code and history at 8ee7955: 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
Architecture & Codebase — including AI provenance
strongcrates/arroyo-state-protocol/src/lib.rs is 2,098 lines, 23× this codebase's median file
adequateThe median source file here is 89 lines. 21 files exceed 1,000 lines, the largest being 2,098. 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/arroyo-state-protocol/src/lib.rs:1 — 2,098 lines (23× median) |
crates/arroyo-connectors/src/filesystem/sink/mod.rs:1 — 2,049 lines (23× median) |
crates/arroyo-operator/src/operator.rs:1 — 1,533 lines (17× median) |
crates/arroyo-rpc/src/lib.rs:1 — 1,517 lines (17× median) |
crates/arroyo-worker/src/lib.rs:1 — 1,486 lines (16× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate11% of bug fixes add or change a test
adequateOf 47 fixes in the last 24 months, 5 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.
| 5 of 47 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v0.15.0, is not on the branch this survey read; the newest release on it is v0.8.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.15.0 |
Security & Reliability Posture
adequateNone 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 663 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.
docker/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; 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/binaries.yml:42 — action pinned by tag |
.github/workflows/ci.yml:48 — action pinned by tag |
.github/workflows/ci.yml:88 — download piped into a shell |
1 of 1 Kubernetes workloads declare no resource limits
adequate1 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.
k8s/arroyo/templates/controller.yaml — workload with no limits |
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 |
Readiness and liveness probes are identical in 1 of 1 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
k8s/arroyo/templates/controller.yaml — same probe endpoint twice |
1 of 1 deployments run a single replica
adequate1 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
k8s/arroyo/templates/controller.yaml — replicas: 1 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on arroyosystems/arroyo: 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.