Read 2026-10-28
superlinked/sie: technical due diligence, read from its repository
What Borehole read in superlinked/sie's code and history at fbc6055: 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
strongpackages/sie_server_sidecar/src/dispatcher.rs is 10,552 lines, 55× this codebase's median file
adequateThe median source file here is 190 lines. 36 files exceed 1,900 lines, the largest being 10,552. 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.
packages/sie_server_sidecar/src/dispatcher.rs:1 — 10,552 lines (55× median) |
packages/sie_gateway/src/queue/publisher.rs:1 — 10,446 lines (54× median) |
packages/sie_gateway/src/state/model_registry.rs:1 — 7,858 lines (41× median) |
packages/sie_server_rust/src/candle_backend.rs:1 — 7,341 lines (38× median) |
packages/sie_gateway/src/handlers/serving_disclosure.rs:1 — 5,781 lines (30× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/sie_ts_sdk/playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
packages/sie_ts_sdk/playwright.config.ts:22 — test retry |
9% of recent commits change more than 2,000 lines
adequate59 of 649 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.
| 59 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate1 deserialiser that can run code
adequate1 places read data with a deserialiser that executes what it reads (`yaml.load` without a safe loader). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
packages/sie_server/src/sie_server/config/upstreams.py:431 — code-executing deserialiser |
36 locked dependencies have published vulnerabilities, 37 high or critical in what ships
adequate36 of 1,878 locked dependencies match 128 published advisories in OSV, 62 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.
Observability & Operations
adequateNo structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 3,041 files for 10 structured logging libraries; 0 matched |
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 |
Readiness and liveness probes are identical in 2 of 7 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
deploy/helm/sie-cluster/templates/mcp-edge-deployment.yaml — same probe endpoint twice |
deploy/helm/sie-cluster/templates/otel-collector.yaml — same probe endpoint twice |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on superlinked/sie: 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.