Read 2026-11-03
metersphere/metersphere: technical due diligence, read from its repository
What Borehole read in metersphere/metersphere's code and history at f1565d9: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE:1: The licence is GPL-3.0 with additional termsLICENSE: Relicensed: GPL-2.0 → GPL-3.0 (2022-02-07) → GPL-3.0 with additional terms (2026-03-24)
Architecture & Codebase — including AI provenance
adequatebackend/framework/domain/src/main/java/io/metersphere/api/domain/ApiScenarioReportExample.java is 2,430 lines, 43× this codebase's median file
adequateThe median source file here is 56 lines. 54 files exceed 1,000 lines, the largest being 2,430. 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.
backend/framework/domain/src/main/java/io/metersphere/api/domain/ApiScenarioReportExample.java:1 — 2,430 lines (43× median) |
backend/framework/domain/src/main/java/io/metersphere/api/domain/ApiReportExample.java:1 — 2,370 lines (42× median) |
backend/services/bug-management/src/main/java/io/metersphere/bug/service/BugService.java:1 — 2,159 lines (38× median) |
frontend/src/views/case-management/caseManagementFeature/components/caseTable.vue:1 — 1,986 lines (35× median) |
backend/framework/domain/src/main/java/io/metersphere/api/domain/ApiScenarioExample.java:1 — 1,964 lines (35× 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:1 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequateAPI v1 and v3 have been served together for 41 months
adequatev3 first appeared in Jun 2023, and v1 is still in the code 41 months later. Two versions mean two surfaces to secure, document and support. Ask who still calls the old one, and whether retiring it is planned.
backend/src/main/java/io/metersphere/consul/CatalogApiController.java — v1 since Apr 2021 |
backend/framework/sdk/src/main/java/io/metersphere/sdk/util/FilterChainUtils.java — v3 since Jun 2023 |
Security & Reliability Posture
adequate124 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.
frontend/package.json:40 — ^2.56.3 |
frontend/package.json:41 — ^0.0.2 |
frontend/package.json:42 — ^3.1.29 |
frontend/package.json:44 — ^5.49.1 |
frontend/package.json:45 — ^2.4.0 |
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.
Dockerfile — runs as root |
frontend/Dockerfile — runs as root |
1 environment file is committed
adequatefrontend/.env.production is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
frontend/.env.production — committed environment file |
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/add-labels-for-pr.yml:14 — action pinned by tag |
.github/workflows/codecov.yml:40 — action pinned by tag |
11 places insert HTML from a variable without sanitising it
adequate11 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
frontend/src/assets/icon-font/iconfont.js:28 — HTML from a variable |
frontend/src/assets/js/jsonpath-picker-vanilla/jsonpath-picker-vanilla.js:267 — HTML from a variable |
frontend/src/assets/js/jsonpath-picker-vanilla/jsonpath-picker-vanilla.js:435 — HTML from a variable |
The licence is GPL-3.0 with additional terms
adequateLICENSE grants GPL-3.0 with additional terms: open source; distributing a combined work can oblige publishing its source. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
LICENSE:1 — 18 lines, GPL-3.0 AND LicenseRef-Terms-Additional |
Relicensed: GPL-2.0 → GPL-3.0 (2022-02-07) → GPL-3.0 with additional terms (2026-03-24)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
2 advisories against this project in the last 24 months
adequateThe newest was published on 2025-10-22. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. The record is incomplete: NVD: 1 record names metersphere with nothing tying it to this repository (CVE-2026-109189).
| 2025-10-22: GHSA-vj5x-7374-rf96 (moderate), fixed in >= v2.10.25-lts: MeterSphere logic flaw allows retrieval of arbitrary user information |
| 2025-07-14: GHSA-vcm3-5w3f-9f45 (moderate), fixed in >= v3.6.5-lts: SQL Injection Vulnerability in Sorting Field |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 4,208 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 4,208 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 4,208 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 metersphere/metersphere: 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.