Read 2026-10-23
svix/svix-webhooks: technical due diligence, read from its repository
What Borehole read in svix/svix-webhooks's code and history at c07c464: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongserver/svix-server/src/core/types/mod.rs is 1,666 lines, 16× this codebase's median file
adequateThe median source file here is 100 lines. 7 files exceed 1,000 lines, the largest being 1,666. 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.
server/svix-server/src/core/types/mod.rs:1 — 1,666 lines (16× median) |
csharp/Svix/Endpoint.cs:1 — 1,491 lines (14× median) |
server/svix-server/src/worker.rs:1 — 1,323 lines (13× median) |
server/svix-server/src/v1/endpoints/attempt.rs:1 — 1,200 lines (12× median) |
server/svix-server/src/core/webhook_http_client.rs:1 — 1,135 lines (11× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate123 test files against 3,206 source files (3.8%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 123 test files / 3,206 source files |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate1 credential-shaped string 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.
| JWT, where fakes are usual |
The build runs third-party code it does not pin
adequate1 third-party CI action is 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/python-release.yml:35 — action pinned by tag |
.github/workflows/sdks-release.yml:71 — download piped into a shell |
7 locked dependencies have published vulnerabilities
adequate7 of 982 locked dependencies match 10 published advisories in OSV. 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.
server/Cargo.lock — rsa 0.7.2: GHSA-4grx-2x9w-596c (moderate) |
server/Cargo.lock — rsa 0.9.10: RUSTSEC-2023-0071 (moderate) |
bridge/Cargo.lock — bincode 1.3.3: RUSTSEC-2025-0141 (unrated) |
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 svix/svix-webhooks: 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.