Read 2026-11-03
structuredlabs/preswald: technical due diligence, read from its repository
What Borehole read in structuredlabs/preswald's code and history at cb1a89b: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongfrontend/src/utils/websocket.js is 3,629 lines, 59× this codebase's median file
adequateThe median source file here is 61 lines. 3 files exceed 1,000 lines, the largest being 3,629. 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.
frontend/src/utils/websocket.js:1 — 3,629 lines (59× median) |
preswald/engine/transformers/reactive_runtime.py:1 — 2,801 lines (45× median) |
preswald/interfaces/components.py:1 — 1,139 lines (18× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate1 test files against 108 source files (0.9%). 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.
| 1 test files / 108 source files |
Pinned dependencies have not moved in 12 months
adequateThe lockfile last changed 386 days before the newest commit, and 50 commits have landed since. Every security fix published upstream in that time is absent until someone updates it, and the longer the gap the larger and riskier that update becomes.
| frontend/package-lock.json last changed 2025-05-21 |
6% of recent commits change more than 2,000 lines
adequate32 of 502 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.
| 32 commits over 2,000 lines |
Product & Engineering Maturity
adequate1% of bug fixes add or change a test
adequateOf 89 fixes in the last 24 months, 1 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 1 of 89 |
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate4 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/deployment_autotests.yaml:21 — action pinned by tag |
.github/workflows/pre-release.yml:34 — action pinned by tag |
.github/workflows/deployment_autotests.yaml:24 — download piped into a shell |
6 SQL statements built from strings
adequate6 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.
preswald/engine/managers/data.py:135 — SQL built from a string |
preswald/engine/managers/data.py:166 — SQL built from a string |
preswald/engine/managers/data.py:182 — SQL built from a string |
28 locked dependencies have published vulnerabilities, 11 high or critical in what ships
adequate28 of 806 locked dependencies match 67 published advisories in OSV, 33 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.
frontend/package-lock.json — maplibre-gl 4.7.1: GHSA-jrc7-96c5-q579 (critical), fixed in 6.4.1 |
frontend/package-lock.json — @remix-run/router 1.21.0: GHSA-2w69-qvjg-hvjx (high), fixed in 1.23.2 |
frontend/package-lock.json — lodash 4.17.21: GHSA-r5fr-rjxr-66jc (high), fixed in 4.18.0 |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 158 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 158 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 158 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 structuredlabs/preswald: 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.