Read 2026-11-03
goodrain/rainbond: technical due diligence, read from its repository
What Borehole read in goodrain/rainbond's code and history at 95970c1: 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 | strong |
| Product & Engineering Maturity | adequate |
| 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
LICENSE: Relicensed: LGPL-3.0 → Apache-2.0 (2025-05-29) → proprietary (2025-07-15)
Architecture & Codebase — including AI provenance
adequatedb/dao/dao_mock.go is 5,381 lines, 50× this codebase's median file
adequateThe median source file here is 107 lines. 19 files exceed 1,070 lines, the largest being 5,381. 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.
db/dao/dao_mock.go:1 — 5,381 lines (50× median) |
api/handler/service.go:1 — 4,528 lines (42× median) |
api/model/model.go:1 — 2,453 lines (22× median) |
worker/appm/conversion/version.go:1 — 2,402 lines (22× median) |
api/handler/gateway_action.go:1 — 2,384 lines (22× median) |
8 base images float: no version, or `latest`
adequate8 of 25 `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.
util/dockerfile/parser/testfiles-negative/env_no_value/Dockerfile:1 — base image without a version |
util/dockerfile/parser/testfiles/cpuguy83-nagios/Dockerfile:1 — base image without a version |
util/dockerfile/parser/testfiles/env/Dockerfile:1 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate97 direct dependencies in a single manifest
adequatego.mod declares 97 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.
go.mod — 97 declared |
5 files still carry code deprecated more than two years ago
adequate5 files were marked deprecated over two years ago and still are, the oldest since Sep 2020. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
worker/server/pb/app_runtime_server.pb.go — deprecated since Sep 2020 |
pkg/generated/informers/externalversions/factory.go — deprecated since Apr 2021 |
builder/sources/image.go — deprecated since Sep 2022 |
worker/server/pb/worker/server/pb/app_runtime_server.pb.go — deprecated since Feb 2023 |
mq/api/grpc/pb/message.pb.go — deprecated since Jun 2023 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v3.6.1, is not on the branch this survey read; the newest release on it is v3.6.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v3.6.1 |
Security & Reliability Posture
adequate24 Dockerfiles run 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.
util/dockerfile/parser/testfile-line/Dockerfile — runs as root |
util/dockerfile/parser/testfiles-negative/env_no_value/Dockerfile — runs as root |
util/dockerfile/parser/testfiles/ADD-COPY-with-JSON/Dockerfile — runs as root |
util/dockerfile/parser/testfiles/brimstone-consuldock/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate8 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/claude.yml:91 — action pinned by tag |
.github/workflows/commit-ci-build.yml:18 — action pinned by tag |
6 outbound calls can wait forever
adequate6 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
api/controller/kubeblocks.go:180 — outbound call without a timeout |
api/handler/helm.go:72 — outbound call without a timeout |
builder/sourceutil/remote_http_client.go:30 — outbound call without a timeout |
4 shell commands built from strings
adequate4 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
builder/exector/export_app.go:168 — command run through a shell |
builder/sources/home.go:59 — command run through a shell |
util/ansible/node.go:62 — command run through a shell |
19 locked dependencies have published vulnerabilities, 19 high or critical in what ships
adequate19 of 296 locked dependencies match 62 published advisories in OSV, 24 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.
Licence text does not match a standard licence
adequateLICENSE exists but its text does not match any standard licence. A bespoke or hand-edited licence is not wrong, but it cannot be cleared by recognising its name: counsel has to read it, and until they do neither side knows precisely what rights transfer with the code.
LICENSE:1 — 17 lines, proprietary |
Relicensed: LGPL-3.0 → Apache-2.0 (2025-05-29) → proprietary (2025-07-15)
adequateThe root licence changed 2 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.
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-08-13. 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 3.6.0. Answer lives in: the release you run, set against each fixed version.
| 2026-08-13: CVE-2026-72741 (high): Rainbond through 6.9.7 contains a broken access control vulnerability in the CheckToken function that allows authenticated attackers to access unauthorized ente |
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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on goodrain/rainbond: 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.