Read 2026-11-03
eclipse-openvsx/openvsx: technical due diligence, read from its repository
What Borehole read in eclipse-openvsx/openvsx's code and history at 47489e6: 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 |
What the repository says
- Releases are cut from another branch than the one surveyed
CONTRIBUTING.md:24: names Eclipse FoundationREADME.md:17: names OpenSSF
Architecture & Codebase — including AI provenance
adequateserver/src/main/java/org/eclipse/openvsx/RegistryAPI.java is 1,994 lines, 21× this codebase's median file
adequateThe median source file here is 91 lines. 8 files exceed 1,000 lines, the largest being 1,994. 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/src/main/java/org/eclipse/openvsx/RegistryAPI.java:1 — 1,994 lines (21× median) |
server/src/main/java/org/eclipse/openvsx/repositories/ExtensionVersionJooqRepository.java:1 — 1,857 lines (20× median) |
webui/src/extension-registry-service.ts:1 — 1,662 lines (18× median) |
server/src/main/java/org/eclipse/openvsx/admin/AdminAPI.java:1 — 1,605 lines (17× median) |
server/src/main/java/org/eclipse/openvsx/LocalRegistryService.java:1 — 1,572 lines (17× median) |
2 base images float: no version, or `latest`
adequate2 of 7 `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.
.gitpod.dockerfile:1 — base image without a version |
deploy/docker/Dockerfile:4 — base image without a version |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (webui/configs/playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
webui/configs/playwright.config.ts:49 — test retry |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v1.3.2, is not on the branch this survey read; the newest release on it is v1.3.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.3.2 |
Security & Reliability Posture
adequate2 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| GitHub token, where fakes are usual |
| Stripe live key, where fakes are usual |
2 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.
deploy/docker/Dockerfile — runs as root |
webui/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate2 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.
deploy/docker/Dockerfile:17 — download piped into a shell |
10 locked dependencies have published vulnerabilities, 1 high or critical
adequate10 of 915 locked dependencies match 10 published advisories in OSV, 1 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
webui/yarn.lock — body-parser 2.3.0: GHSA-27r3-jxmh-p828 (high), fixed in 2.4.0 |
webui/yarn.lock — ajv 6.12.6: GHSA-2g4f-4pwh-qvx6 (moderate), fixed in 6.14.0 |
cli/yarn.lock — glob 13.0.0: GHSA-3g3m-2fjr-6pw4 (moderate), fixed in 14.0.2 |
1 workload setting give a container the host
adequate1 places in the deployment configuration run a container privileged or in the host's network, process or IPC namespace. A compromise of that container is a compromise of the machine, and most acquirers' security reviews block it. Node agents (network, storage, monitoring) are excluded.
deploy/kubernetes/elasticsearch.yaml:30 — privileged or host namespace |
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
webui/vite.config.mts:50 — source maps in a production build |
7 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-09-21. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 5 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 1.3.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names openvsx with nothing tying it to this repository (CVE-2026-28353).
| 2026-09-21: GHSA-f55q-5m46-rmxc (critical), fixed in 1.2.0: Marketplace Takeover via Forwarded-host cache poisoning of /vscode/gallery/{namespace}/{extension}/latest |
| 2026-09-20: GHSA-h685-gqw7-fqw7 (moderate), fixed in 1.2.0: Extracting VSIX entries can fill the server's temporary storage |
| 2026-06-25: GHSA-fpg6-3vrq-mxw8 (moderate): Pre-Publish Secret & Blocklist Scanners Bypass via Zip Entry Name Starting With ".." |
| 2026-05-08: GHSA-h7f3-4pcx-gv9w (moderate), fixed in 0.34.4: Supply Chain Identity Spoofing via Parser Differential in ExtensionProcessor.java |
| 2026-03-23: GHSA-vwx5-w7c3-rjq8 (moderate): Vulnerable GitHub Actions leading to leakage of GITHUB_TOKEN and SONAR_TOKEN |
Observability & Operations
adequateNo 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 1,605 files for 10 structured logging libraries; 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 |
2 of 10 deployed images carry no version, or `latest`
adequate2 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.
deploy/kubernetes/openvsx-server.yaml:40 — image without a version |
deploy/kubernetes/openvsx-webui.yaml:25 — image without a version |
Readiness and liveness probes are identical in 4 of 6 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
deploy/kubernetes/elasticsearch.yaml — same probe endpoint twice |
deploy/kubernetes/openvsx-webui.yaml — same probe endpoint twice |
deploy/openshift/openvsx-deployment-no-es.yml — same probe endpoint twice |
5 of 5 deployments run a single replica
adequate5 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
deploy/kubernetes/elasticsearch.yaml — replicas: 1 |
deploy/kubernetes/openvsx-server.yaml — replicas: 1 |
deploy/kubernetes/openvsx-webui.yaml — replicas: 1 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on eclipse-openvsx/openvsx: 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.