Read 2026-10-28
deepstreamio/deepstream.io: technical due diligence, read from its repository
What Borehole read in deepstreamio/deepstream.io's code and history at d7b2410: 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 | adequate |
| Engineering Process & SDLC Maturity | adequate |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: MIT → Apache-2.0 (2016-06-30) → AGPL-3.0 (2016-07-09) → MIT (2019-10-26).gitmodules:1: 12 submodule(s) this survey does not read: test-e2e/features, connectors/cache/redis, connectors/cache/memcached
Architecture & Codebase — including AI provenance
adequateNo finding.
Engineering Process & SDLC Maturity
adequateChange lands on the trunk with no trace of review
adequateIn the last 24 months, 1 of 51 commits (2.0%) carry any trace of review: a merge, a pull-request reference, a Reviewed-by or Reviewed-on trailer, a Closes/Fixes reference, a maintainer's sign-off on someone else's change, or a change applied by someone other than its author. Every common review workflow leaves at least one of those, so either review happens somewhere this history cannot see, or it is not happening. A buyer should establish which before relying on the review story they are told.
| 1 of 51 commits in the last 24 months carry review evidence; 23.9% across all 1,858 |
Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 271 tracked files |
32 tests are switched off
adequate32 skip markers across 15 of 114 test files. Each is a failure somebody chose to stop seeing; the question is whether anyone is tracking them.
src/config/js-yaml-loader.spec.ts:38 — skipped test |
src/config/js-yaml-loader.spec.ts:302 — skipped test |
src/connection-endpoint/base/connection-endpoint.spec.ts:42 — skipped test |
Product & Engineering Maturity
adequateNo finding.
Security & Reliability Posture
adequate1 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.
Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate7 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/lint-test.yml:22 — action pinned by tag |
.github/workflows/release.yml:58 — action pinned by tag |
scripts/linux-package.sh:51 — download piped into a shell |
1 SQL statement built from strings
adequate1 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.
telemetry-server/telemetry-server.ts:14 — SQL built from a string |
4 shell commands built from strings
adequate4 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
src/service/service.ts:199 — command run through a shell |
src/service/service.ts:214 — command run through a shell |
src/service/service.ts:229 — command run through a shell |
12 locked dependencies have published vulnerabilities, 8 high or critical in what ships
adequate12 of 194 locked dependencies match 23 published advisories in OSV, 8 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.
telemetry-server/package-lock.json — proxy-addr 2.0.6: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8 |
telemetry-server/package-lock.json — body-parser 1.19.0: GHSA-27r3-jxmh-p828 (high), fixed in 1.20.9 |
package-lock.json — body-parser 2.3.0: GHSA-27r3-jxmh-p828 (high), fixed in 2.4.0 |
Relicensed: MIT → Apache-2.0 (2016-06-30) → AGPL-3.0 (2016-07-09) → MIT (2019-10-26)
adequateThe root licence changed 3 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
7 advisories against this project in the last 24 months, 6 high or critical
adequateThe newest was published on 2026-10-12. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version.
| 2026-10-12: GHSA-j55p-v9rg-r9f2 (moderate), fixed in 10.2.4: LISTEN_ACCEPT/LISTEN_REJECT bypass Valve permissions allowing listen-provider hijack |
| 2026-10-12: GHSA-g4qj-f7jp-76c6 (high), fixed in 10.2.1: Incomplete prototype pollution fix: UPDATE action bypasses isValidPath key validation |
| 2026-10-11: GHSA-v448-hpx6-fm45 (high), fixed in 10.2.3: Bulk record authorization denial removes the wrong name and exposes private subscriptions |
| 2026-10-02: GHSA-9r5v-rrr7-v476 (high), fixed in 10.2.0: Unauthenticated Regular Expression Denial of Service (ReDoS) via listener patterns |
| 2026-09-11: GHSA-rv32-v8hf-rxqg (high), fixed in 10.2.2: Unauthenticated remote denial of service via sdkType in the pre-auth CHALLENGE message |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 247 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 247 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on deepstreamio/deepstream.io: 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.