Read 2026-10-04
getsentry/relay: technical due diligence, read from its repository
What Borehole read in getsentry/relay's code and history at 0001524: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE.md:1: The licence is FSL-1.1-ALv2: source available, not open sourceLICENSE: Relicensed: BUSL-1.1 → FSL-1.0-ALv2 (2023-11-17) → FSL-1.1-ALv2 (2024-02-27).gitmodules:1: 2 submodule(s) this survey does not read: relay-ua/uap-core, relay-conventions/sentry-conventions
Architecture & Codebase — including AI provenance
strongrelay-event-normalization/src/event.rs is 6,068 lines, 37× this codebase's median file
adequateThe median source file here is 160 lines. 14 files exceed 1,600 lines, the largest being 6,068. 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.
relay-event-normalization/src/event.rs:1 — 6,068 lines (37× median) |
relay-event-normalization/src/normalize/span/tag_extraction.rs:1 — 3,407 lines (21× median) |
relay-event-normalization/src/eap/mod.rs:1 — 3,210 lines (20× median) |
relay-config/src/config.rs:1 — 3,055 lines (19× median) |
relay-server/src/utils/rate_limits.rs:1 — 2,623 lines (16× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate2 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key. 2 other matchs set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
| 2 cited: private key block, where fakes are usual |
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.
py/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate10 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; 2 steps pipe 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/ci.yml:53 — action pinned by tag |
.github/workflows/ci.yml:62 — action pinned by tag |
.github/workflows/build_binary.yml:38 — download piped into a shell |
11 locked dependencies have published vulnerabilities, 12 high or critical
adequate11 of 777 locked dependencies match 28 published advisories in OSV, 12 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. None of the high or critical ones is in what the product ships: they are development dependencies. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
uv.lock — pyjwt 2.13.0: GHSA-ffc3-869f-jxw9 (critical), fixed in 2.14.0; a development dependency |
uv.lock — cryptography 49.0.0: GHSA-g6cj-pr64-35w5 (high), fixed in 50.0.0; a development dependency |
uv.lock — urllib3 2.7.0: GHSA-8988-9cw3-xx77 (high), fixed in 2.8.0; a development dependency |
The licence is FSL-1.1-ALv2: source available, not open source
adequateLICENSE.md grants FSL-1.1-ALv2: source available, not open source; a competing commercial product or service is not allowed; each version becomes Apache-2.0 two years after its release. 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.md:1 — 105 lines, FSL-1.1-ALv2 |
Relicensed: BUSL-1.1 → FSL-1.0-ALv2 (2023-11-17) → FSL-1.1-ALv2 (2024-02-27)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
LICENSE — BUSL-1.1 from 2020-07-21 |
LICENSE — FSL-1.0-ALv2 from 2023-11-17 |
LICENSE.md — FSL-1.1-ALv2 from 2024-02-27 |
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 |
An error reporter is installed but never initialised
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 getsentry/relay: 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.