Read 2026-10-23
rudderlabs/rudder-server: technical due diligence, read from its repository
What Borehole read in rudderlabs/rudder-server's code and history at 83db4d6: 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 | strong |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
LICENSE:1: The licence is Elastic-2.0: source available, not open sourceLICENSE: Relicensed: SSPL-1.0 with additional terms → AGPL-3.0 (2020-03-20) → Elastic-2.0 (2023-09-01)enterprise/LICENSE: Part of the code is under a separate licence: enterprise/
Architecture & Codebase — including AI provenance
strongprocessor/processor.go is 4,656 lines, 35× this codebase's median file
adequateThe median source file here is 131 lines. 7 files exceed 1,310 lines, the largest being 4,656. 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.
processor/processor.go:1 — 4,656 lines (35× median) |
warehouse/utils/reservedkeywords.go:1 — 2,251 lines (17× median) |
warehouse/integrations/snowflake/snowflake.go:1 — 1,646 lines (12× median) |
warehouse/integrations/redshift/redshift.go:1 — 1,543 lines (11× median) |
warehouse/internal/repo/upload.go:1 — 1,542 lines (11× median) |
Engineering Process & SDLC Maturity
adequate5% of recent commits change more than 2,000 lines
adequate34 of 648 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.
| 34 commits over 2,000 lines |
Product & Engineering Maturity
adequate111 direct dependencies in a single manifest
adequatego.mod declares 111 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 — 111 declared |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v1.91.1, is not on the branch this survey read; the newest release on it is v1.91.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.91.1 |
Security & Reliability Posture
adequate2 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.
Dockerfile — runs as root |
suppression-backup-service/Dockerfile — runs as root |
1 environment file is committed
adequatetesthelper/.env is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
testhelper/.env — committed environment file |
11 outbound calls can wait forever
adequate11 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.
cmd/devtool/commands/event.go:63 — outbound call without a timeout |
enterprise/suppress-user/factory.go:237 — outbound call without a timeout |
enterprise/suppress-user/syncer.go:84 — outbound call without a timeout |
66 SQL statements built from strings
adequate66 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.
enterprise/reporting/error_reporting.go:646 — SQL built from a string |
enterprise/reporting/reporting.go:557 — SQL built from a string |
jobsdb/admin.go:71 — SQL built from a string |
2 locked dependencies have published vulnerabilities, 1 high or critical in what ships
adequate2 of 385 locked dependencies match 3 published advisories in OSV, 1 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.
The licence is Elastic-2.0: source available, not open source
adequateLICENSE grants Elastic-2.0: source available, not open source; offering it as a managed service is 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:1 — 44 lines, Elastic-2.0 |
Relicensed: SSPL-1.0 with additional terms → AGPL-3.0 (2020-03-20) → Elastic-2.0 (2023-09-01)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
Part of the code is under a separate licence: enterprise/
adequateA directory named for a paid edition carries its own licence. That code is usually not open source even where the rest is; what the buyer may do with each part differs.
enterprise/LICENSE — licence: Elastic-2.0 |
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 |
2 of 4 deployed images carry no version, or `latest`
adequate2 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.
docker-compose.yml:29 — image without a version |
docker-compose.yml:33 — 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 rudderlabs/rudder-server: 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.