Read 2026-11-03
sequinstream/sequin: technical due diligence, read from its repository
What Borehole read in sequinstream/sequin's code and history at 46ce4e1: 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 | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
stronglib/sequin_web/live/sink_consumers/show.ex is 1,828 lines, 27× this codebase's median file
adequateThe median source file here is 66 lines. 14 files exceed 1,000 lines, the largest being 1,828. 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.
lib/sequin_web/live/sink_consumers/show.ex:1 — 1,828 lines (27× median) |
lib/sequin/consumers/consumers.ex:1 — 1,806 lines (27× median) |
assets/svelte/functions/Edit.svelte:1 — 1,661 lines (25× median) |
lib/sequin/transforms/transforms.ex:1 — 1,627 lines (24× median) |
lib/sequin_web/live/components/consumer_form.ex:1 — 1,503 lines (22× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongGo 1.24 is past end of life
adequateThe code is pinned to Go 1.24 (end of life 2026-02-10). None of these receives security fixes any more; the first stopped on 2026-02-10. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
Dockerfile — Go 1.24, end of life 2026-02-10 |
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. 8 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.
| private key block, where fakes are usual |
None 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 2,367 tracked files; 0 present |
The build runs third-party code it does not pin
adequate9 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/docker-build.yml:43 — action pinned by tag |
.github/workflows/docker-build.yml:59 — action pinned by tag |
Dockerfile:36 — download piped into a shell |
8 outbound calls can wait forever
adequate8 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.
cli/api/stream.go:30 — outbound call without a timeout |
cli/api/stream.go:74 — outbound call without a timeout |
cli/api/stream.go:128 — outbound call without a timeout |
27 locked dependencies have published vulnerabilities, 9 high or critical in what ships
adequate27 of 399 locked dependencies match 82 published advisories in OSV, 42 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.
cli/go.mod — golang.org/x/crypto v0.36.0: GHSA-89gr-r52h-f8rx (critical), fixed in 0.52.0 |
assets/package-lock.json — js-cookie 3.0.5: GHSA-qjx8-664m-686j (high), fixed in 3.0.7 |
assets/package-lock.json — lodash 4.17.21: GHSA-r5fr-rjxr-66jc (high), fixed in 4.18.0 |
Observability & Operations
not assessableNo 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 |
3 of 15 deployed images carry no version, or `latest`
adequate3 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/docker-compose.yaml:5 — image without a version |
docker/docker-compose.yaml:60 — image without a version |
docker/docker-compose.yaml:67 — 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 sequinstream/sequin: 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.