Read 2026-11-03
mercurjs/mercur: technical due diligence, read from its repository
What Borehole read in mercurjs/mercur's code and history at 47bacd0: 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 | strong |
| Security & Reliability Posture | strong |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongpackages/admin/src/get-route-map.tsx is 2,503 lines, 73× this codebase's median file
adequateThe median source file here is 34 lines. 11 files exceed 1,000 lines, the largest being 2,503. 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.
packages/admin/src/get-route-map.tsx:1 — 2,503 lines (73× median) |
apps/storefront/src/icons/index.tsx:1 — 2,041 lines (60× median) |
packages/admin/src/lib/data/countries.ts:1 — 1,768 lines (52× median) |
packages/dashboard-shared/src/lib/data/countries.ts:1 — 1,768 lines (52× median) |
packages/admin/src/pages/orders/order-detail/components/order-summary-section/order-summary-section.tsx:1 — 1,374 lines (40× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate212 test files against 4,213 source files (5.0%). 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.
| 212 test files / 4,213 source files |
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (e2e-tests/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.
e2e-tests/playwright.config.ts:11 — test retry |
7% of recent commits change more than 2,000 lines
adequate52 of 746 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.
| 52 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
strong371 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.
apps/admin-test/package.json:12 — * |
apps/admin-test/package.json:13 — ^18.3.1 |
apps/admin-test/package.json:14 — ^18.3.1 |
apps/admin-test/package.json:18 — * |
apps/admin-test/package.json:19 — * |
7 places insert HTML from a variable without sanitising it
adequate7 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.
apps/storefront/src/app/[locale]/(main)/categories/[category]/page.tsx:130 — HTML from a variable |
apps/storefront/src/app/[locale]/(main)/categories/[category]/page.tsx:148 — HTML from a variable |
apps/storefront/src/app/[locale]/(main)/categories/page.tsx:90 — HTML from a variable |
102 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
apps/docs/images/user-guides/vendor/stores — 14 tracked files, no licence file |
apps/docs/references/api/vendor/members — 3 tracked files, no licence file |
apps/docs/references/api/vendor/orders — 11 tracked files, no licence file |
apps/docs/references/api/vendor/payout-accounts — 4 tracked files, no licence file |
apps/docs/references/api/vendor/payouts — 2 tracked files, no licence file |
apps/docs/references/api/vendor/product-attributes — 2 tracked files, no licence file |
7 advisories against this project in the last 24 months, 4 high or critical
adequateThe newest was published on 2026-11-04. 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 2 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 2.4.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 16 records name mercur with nothing tying them to this repository (CVE-2000-0198, CVE-2000-0239, CVE-2000-0318, …).
| 2026-11-04: GHSA-r7gm-rgf8-5q8m (moderate), fixed in 2.4.1: Vendor service-zone GET route missing seller ownership check |
| 2026-11-04: GHSA-rcjg-5cvg-wwvj (high), fixed in 2.3.7: Cross-vendor inventory-level write/delete via the top-level `location-levels/batch` route (no seller-ownership check) |
| 2026-11-04: GHSA-mhch-gq7f-v5p7 (critical), fixed in 2.4.1: Mercur 2.3.6 vendor API — cross-seller authorization: field traversal to invite-token takeover + bank details (Critical); unscoped /vendor/products/:id reads an |
| 2026-10-12: GHSA-w4vq-6jvh-cfpg (high), fixed in 2.3.7: Seller promotions lose their seller scope on cart refresh, discounting other sellers' items |
| 2026-09-17: GHSA-qc6m-3g2c-xv4v (moderate), fixed in 2.2.0: Vendor variant media route missing seller ownership check allows cross-seller image tampering |
Observability & Operations
adequateSends usage data to telemetry.mercurjs.com by default
adequatepackages/cli/src/telemetry/index.ts sends to telemetry.mercurjs.com, and packages/cli/src/telemetry/store.ts leaves reporting on as shipped. Every installation reports to the vendor unless its operator turns this off. For a buyer running it inside their own product, that is an outbound data flow to a third party: ask what is sent, how often, and whether the buyer's customers were told.
packages/cli/src/telemetry/index.ts:10 — reports to telemetry.mercurjs.com |
packages/cli/src/telemetry/store.ts:13 — the reporting setting is on by default |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on mercurjs/mercur: 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.