Read 2026-11-03
esm-dev/esm.sh: technical due diligence, read from its repository
What Borehole read in esm-dev/esm.sh's code and history at ce5eb02: 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 | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
adequateserver/router.go is 2,085 lines, 189× this codebase's median file
adequateThe median source file here is 11 lines. 4 files exceed 1,000 lines, the largest being 2,085. 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.
server/router.go:1 — 2,085 lines (189× median) |
server/build.go:1 — 2,026 lines (184× median) |
server/build_resolver.go:1 — 1,614 lines (146× median) |
server/npmrc.go:1 — 1,117 lines (101× median) |
1 base image floats: no version, or `latest`
adequate1 of 2 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
Dockerfile:26 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.42 to 0.98 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.42, second half 0.98 (split 2023-10-05) |
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 509 tracked files; 0 present |
8 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.
cli/npm/package.json:3 — * |
cli/npm/package.json:17 — * |
cli/npm/package.json:18 — * |
cli/npm/package.json:19 — * |
cli/npm/package.json:20 — * |
The build runs third-party code it does not pin
adequate6 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. 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/release-cli.yml:142 — action pinned by tag |
.github/workflows/release-server.yml:23 — action pinned by tag |
1 locked dependency has published vulnerabilities
adequate1 of 12 locked dependencies match 2 published advisories in OSV. 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.
go.mod — golang.org/x/net v0.60.0: GO-2026-6860 (unrated), fixed in 0.62.0 |
17 advisories against this project in the last 24 months, 13 high or critical
adequateThe newest was published on 2026-10-19. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries.
| 2026-10-19: GHSA-vmp2-ffm6-jv5f (moderate): O(n²) + unbounded recursion in hasExternalExportStar |
| 2026-10-19: GHSA-85fc-q6w7-vwx4 (moderate): Recurring path-traversal pattern across storage/module/web-path handling suggests no centralized, mandatory validation choke point (follow-up to CVE-2026-44593 |
| 2026-10-19: GHSA-29qg-6q7w-cmm8 (critical), fixed in v138: Unauthenticated package takeover, credential disclosure, and server-side code execution via unvalidated package names and trusted loader paths |
| 2026-10-19: GHSA-xmrp-677j-v37h (high): Dependency Name Path Traversal in installDependencies Leading to NPM Cache Poisoning and Loader Hijack |
| 2026-07-26: GHSA-575c-jj3w-hqjp (critical): The request origin (X-Real-Origin, or the Host header) is returned verbatim and interpolated into a double-quoted JS string in the served ?worker module, while |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 500 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 500 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 500 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 esm-dev/esm.sh: 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.