Borehole · Project · free tier
vendurehq/vendure
Free reading: not for reliance
b665351 · 9,088 commits · 5,903 files
Read 2026-10-22

vendurehq/vendure: technical due diligence, read from its repository

What Borehole read in vendurehq/vendure's code and history at b665351: 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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturitystrong
Security & Reliability Postureadequate
Observability & Operationsadequate
Fit with the Acquirernot assessable

What the repository says

  • LICENSE.md: Relicensed: proprietary → MIT (2018-06-22) → GPL-3.0 (2024-07-17)

Architecture & Codebase — including AI provenance

strong
01.6

packages/common/src/generated-types.ts is 7,576 lines, 111× this codebase's median file

adequate

The median source file here is 68 lines. 11 files exceed 1,000 lines, the largest being 7,576. 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.

Evidence
packages/common/src/generated-types.ts:1 — 7,576 lines (111× median)
packages/common/src/generated-shop-types.ts:1 — 3,751 lines (55× median)
packages/core/src/service/services/order.service.ts:1 — 2,790 lines (41× median)
packages/core/src/config/vendure-config.ts:1 — 1,576 lines (23× median)
packages/cli/src/commands/console/console.ts:1 — 1,488 lines (21× median)

Engineering Process & SDLC Maturity

strong
02.16

Tests are retried until they pass

adequate

The suite is configured to retry failing tests (packages/core/src/job-queue/in-memory-job-queue-strategy.spec.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.

Product & Engineering Maturity

strong
04.38

17 files still carry code deprecated more than two years ago

adequate

17 files were marked deprecated over two years ago and still are, the oldest since Jan 2023. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.

Security & Reliability Posture

adequate
05.1

1 credential-shaped string in the tree sit in tests, examples, documentation or local development settings

adequate

Strings 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.

Evidence
Google API key, where fakes are usual
05.25

1 environment file is committed

adequate

packages/create/templates/.env.hbs 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.

Evidence
packages/create/templates/.env.hbs — committed environment file
05.20

13 SQL statements built from strings

adequate

13 places in product code build SQL by formatting or joining strings rather than passing parameters, and in 5 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.

05.48

8 places insert HTML from a variable without sanitising it

adequate

8 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.

05.49

The production build publishes source maps

adequate

The 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.

Evidence
packages/admin-ui/angular.json:67 — source maps in a production build
packages/graphiql-plugin/vite.config.mts:11 — source maps in a production build
packages/ui-devkit/scaffold/angular.json:82 — source maps in a production build
05.60

Relicensed: proprietary → MIT (2018-06-22) → GPL-3.0 (2024-07-17)

adequate

The root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.

Evidence
LICENSE.md — proprietary from 2018-06-11
LICENSE — MIT from 2018-06-22
LICENSE — GPL-3.0 from 2024-07-17
05.65

27 advisories against this project in the last 24 months, 16 high or critical

adequate

The newest was published on 2026-10-05. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version. The record is incomplete: NVD: 2 records name vendure with nothing tying them to this repository (CVE-2022-23065, CVE-2024-48914).

Evidence
2026-10-05: GHSA-37xp-mjp8-6f9x (high), fixed in 3.7.4: `rotateApiKey` performs no ownership / permission-subset check and returns the new plaintext secret, so an admin holding only `UpdateApiKey` can rotate a higher
2026-10-05: GHSA-8ghm-q833-cmgp (low), fixed in 3.7.4: Stock Level Race Condition Allows Inventory Overselling via Concurrent Checkout
2026-09-30: GHSA-7g8c-5hg8-348m (moderate), fixed in 3.6.5: AISLE-2026-0093 Missing channel scoping in TranslatableSaver.update allows cross-channel entity mutation by restricted administrators
2026-09-30: GHSA-5fpx-9m35-w745 (high), fixed in 3.8.0: Authenticated session is not bound to its API audience (cross-context session replay)
2026-09-02: GHSA-gg28-cx38-jxxr (moderate), fixed in 3.7.3: Vendure createProductOption missing channel scoping allows cross-channel ProductOptionGroup writes

Observability & Operations

adequate
06.2

No structured logging library is in use

adequate

Nothing 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.

Evidence
searched 4,118 files for 10 structured logging libraries; 0 matched
06.18

4 of 11 deployed images carry no version, or `latest`

adequate

4 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.

Evidence
docker-compose.yml:7 — image without a version
docker-compose.yml:71 — image without a version
docker-compose.yml:111 — image without a version

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on vendurehq/vendure: 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.