Read 2026-11-03
streamaserver/streama: technical due diligence, read from its repository
What Borehole read in streamaserver/streama's code and history at 9dcd79b: 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
stronggrails-app/assets/bower/lodash/lodash.js is 17,108 lines, 196× this codebase's median file
adequateThe median source file here is 87 lines. 16 files exceed 1,000 lines, the largest being 17,108. 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.
grails-app/assets/bower/lodash/lodash.js:1 — 17,108 lines (196× median) |
grails-app/assets/bower/jquery-ui/jquery-ui.js:1 — 15,009 lines (172× median) |
grails-app/assets/bower/jquery/jquery.js:1 — 9,815 lines (112× median) |
grails-app/assets/bower/angular-bootstrap/ui-bootstrap-tpls.js:1 — 7,715 lines (88× median) |
grails-app/assets/bower/angular/ui-bootstrap-tpls.js:1 — 7,079 lines (81× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate16 test files against 225 source files (7.1%). 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.
| 16 test files / 225 source files |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate2 Dockerfiles run 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.
docker/Dockerfile — runs as root |
docker/nginx/Dockerfile — runs as root |
2 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-08-13. 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-08-13: CVE-2026-73039 (moderate): streama contains an insecure direct object reference vulnerability in ViewingStatusController that allows authenticated users to read and delete other users' vi |
| 2025-12-18: CVE-2025-34452 (high): Streama versions 1.10.0 through 1.10.5 and prior to commit b7c8767 contain a combination of path traversal and server-side request forgery (SSRF) vulnerabilitie |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 268 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 268 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 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 268 files for 10 structured logging libraries; 0 matched |
One 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 streamaserver/streama: 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.