Read 2026-11-03
pump-io/pump.io: technical due diligence, read from its repository
What Borehole read in pump-io/pump.io's code and history at ba6b392: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
CONTRIBUTING.md:54: names Linux Foundation
Architecture & Codebase — including AI provenance
strongpublic/javascript/libs/jquery-2.2.4.js is 9,815 lines, 70× this codebase's median file
adequateThe median source file here is 139 lines. 11 files exceed 1,390 lines, the largest being 9,815. 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.
public/javascript/libs/jquery-2.2.4.js:1 — 9,815 lines (70× median) |
public/javascript/libs/wysihtml5-0.3.0.js:1 — 9,522 lines (68× median) |
public/javascript/pump/view.js:1 — 3,313 lines (23× median) |
public/javascript/libs/select2.js:1 — 3,138 lines (22× median) |
public/javascript/libs/jquery.fineuploader.js:1 — 2,599 lines (18× median) |
93 errors caught and discarded in product code
adequate93 places catch an error and do nothing with it, across 11 files (0.8 per thousand lines). Each is a failure the system will not report. They surface later as problems nobody can explain, and they are cheap to fix now.
public/javascript/libs/backbone-min.js:1 — error caught and discarded |
public/javascript/libs/backbone.js:26 — error caught and discarded |
public/javascript/libs/jquery-2.2.4.js:857 — error caught and discarded |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v5.1.4, is not on the branch this survey read; the newest release on it is v2.0.3. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v5.1.4 |
Security & Reliability Posture
adequateNone 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 524 tracked files; 0 present |
54 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
package.json:9 — ^3.0.0 |
package.json:10 — ^3.3.0 |
package.json:11 — ^3.0.3 |
package.json:12 — ^2.10.1 |
package.json:13 — ^1.6.2 |
45 locked dependencies have published vulnerabilities, 63 high or critical in what ships
adequate45 of 402 locked dependencies match 129 published advisories in OSV, 65 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.
npm-shrinkwrap.json — dompurify 2.3.1: GHSA-p3vf-v8qc-cwcr (critical), fixed in 2.4.2 |
npm-shrinkwrap.json — form-data 2.3.3: GHSA-fjxv-7rqg-78g4 (critical), fixed in 2.5.4 |
npm-shrinkwrap.json — form-data 4.0.0: GHSA-fjxv-7rqg-78g4 (critical), fixed in 4.0.4 |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 364 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 364 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 |
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 |
1 of 2 deployed images carry no version, or `latest`
adequate1 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-compose.yml:27 — 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 pump-io/pump.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.