Read 2026-10-23
evershopcommerce/evershop: technical due diligence, read from its repository
What Borehole read in evershopcommerce/evershop's code and history at 3c40526: 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 | adequate |
| 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
Architecture & Codebase — including AI provenance
strongpackages/evershop/src/lib/address/data/regions.ts is 3,963 lines, 74× this codebase's median file
adequateThe median source file here is 53 lines. 13 files exceed 1,000 lines, the largest being 3,963. 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/evershop/src/lib/address/data/regions.ts:1 — 3,963 lines (74× median) |
packages/evershop/src/modules/pageBuilder/pages/admin/pageBuilderEdit/Editor.tsx:1 — 3,345 lines (63× median) |
packages/evershop/src/modules/cms/bootstrap.ts:1 — 1,606 lines (30× median) |
packages/evershop/src/modules/import/services/rules/productRules.ts:1 — 1,598 lines (30× median) |
packages/evershop/src/types/db/index.ts:1 — 1,533 lines (28× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/evershop/src/modules/import/tests/unit/write/categoryWriter.test.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.
packages/evershop/src/modules/import/tests/unit/write/categoryWriter.test.ts:540 — test retry |
8% of recent commits change more than 2,000 lines
adequate43 of 564 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.
| 43 commits over 2,000 lines |
Product & Engineering Maturity
adequate111 direct dependencies in a single manifest
adequatepackages/evershop/package.json declares 111 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
packages/evershop/package.json — 111 declared |
packages/create-evershop-app/package.json — 7 declared |
package.json — 6 declared |
packages/postgres-query-builder/package.json — 2 declared |
Node.js 20 is past end of life
adequateThe code is pinned to Node.js 20 (end of life 2026-04-30). None of these receives security fixes any more; the first stopped on 2026-04-30. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
Dockerfile — Node.js 20, end of life 2026-04-30 |
16% of bug fixes add or change a test
adequateOf 368 fixes in the last 24 months, 58 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 58 of 368 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v2.3.0, is not on the branch this survey read; the newest release on it is v2.2.2. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v2.3.0 |
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 4,467 tracked files; 0 present |
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 |
docker/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate4 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.yml:230 — action pinned by tag |
.github/workflows/release.yml:231 — action pinned by tag |
44 SQL statements built from strings
adequate44 places in product code build SQL by formatting or joining strings rather than passing parameters, and in 8 of them a value, not a table or column name, goes into the string. Where any of those values comes from a request, it is an injection point. Each site needs a look; the fix, parameters, is small.
packages/evershop/src/modules/base/services/sitemap/collectors/entityCollector.ts:43 — SQL built from a string |
packages/evershop/src/modules/base/services/sitemap/collectors/entityCollector.ts:53 — SQL built from a string |
packages/evershop/src/modules/checkout/services/package/packageManager.ts:157 — SQL built from a string |
16 locked dependencies have published vulnerabilities, 10 high or critical in what ships
adequate16 of 904 locked dependencies match 28 published advisories in OSV, 11 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.
package-lock.json — dompurify 3.4.15: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
package-lock.json — handlebars 4.7.9: GHSA-8r5x-fm3f-whwj (critical), fixed in 4.7.10 |
package-lock.json — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8 |
14 places insert HTML from a variable without sanitising it
adequate14 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.
packages/evershop/src/components/common/react/server/Server.tsx:21 — HTML from a variable |
packages/evershop/src/components/common/react/server/Server.tsx:26 — HTML from a variable |
packages/evershop/src/components/common/react/server/Server.tsx:29 — HTML from a variable |
8 advisories against this project in the last 24 months, 5 high or critical
adequateThe newest was published on 2026-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. 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.3.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 8 records name evershop with nothing tying them to this repository (CVE-2023-46493, CVE-2023-46494, CVE-2023-46495, …).
| 2026-10-22: CVE-2026-115323 (moderate): EverShop 1.2.2 before 2.2.1 contains a missing authorization vulnerability in the customer address API that allows unauthenticated attackers to manage other cus |
| 2026-08-20: CVE-2026-72843 (critical): The customer update route in EverShop is declared with "access": "public" in packages/evershop/src/modules/customer/api/updateCustomer/route.json, which causes |
| 2026-02-26: GHSA-cg73-g723-39jw (critical): Arbitrary Customer Account Takeover via Exposure of Password Reset Token in API Response |
| 2026-02-10: GHSA-3h84-9rhc-j2ch (high), fixed in 2.1.1: Second-Order SQL Injection in URL Rewrite Processing Derived from Category URL Keys |
| 2026-01-05: GHSA-m2q5-xhqg-92r2 (high): evershop allows unauthenticated attackers to exhaust application server's resources via "GET /images" API |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 3,985 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 3,985 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 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:5 — 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 evershopcommerce/evershop: 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.