Borehole · Project · free tier
orchardcms/orchardcore
Free reading: not for reliance
41a6b01 · 9,916 commits · 11,002 files
Read 2026-10-04

orchardcms/orchardcore: technical due diligence, read from its repository

What Borehole read in orchardcms/orchardcore's code and history at 41a6b01: 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 Maturityadequate
Product & Engineering Maturitystrong
Security & Reliability Postureadequate
Observability & Operationsadequate
Fit with the Acquirernot assessable

Architecture & Codebase — including AI provenance

strong
01.6

src/OrchardCore.Modules/OrchardCore.Resources/Assets/Vendor/jquery-ui-1.14.2/jquery-ui.js is 18,842 lines, 607× this codebase's median file

adequate

The median source file here is 31 lines. 36 files exceed 1,000 lines, the largest being 18,842. 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.

Engineering Process & SDLC Maturity

adequate
02.3

Tests cover a thin slice of the codebase

adequate

486 test files against 6,178 source files (7.9%). 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.

Evidence
486 test files / 6,178 source files

Product & Engineering Maturity

strong
04.38

16 files still carry code deprecated more than two years ago

adequate

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

Security & Reliability Posture

adequate
05.6

1 Dockerfile runs the application as root

adequate

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

Evidence
Dockerfile — runs as root
05.21

4 shell commands built from strings

adequate

4 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.

Evidence
.scripts/assets-manager/build.mjs:31 — command run through a shell
.scripts/assets-manager/build.mjs:108 — command run through a shell
.scripts/assets-manager/build.mjs:110 — command run through a shell
05.26

66 locked dependencies have published vulnerabilities, 94 high or critical

adequate

66 of 1,724 locked dependencies match 166 published advisories in OSV, 94 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.

Evidence
yarn.lock — shell-quote 1.8.3: GHSA-w7jw-789q-3m8p (critical), fixed in 1.8.4
yarn.lock — tar 7.5.2: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19
yarn.lock — websocket-driver 0.7.4: GHSA-xv26-6w52-cph6 (critical), fixed in 0.7.5
05.48

92 places insert HTML from a variable without sanitising it

adequate

92 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.9

1 vendored component with no licence

adequate

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

Observability & Operations

adequate
06.1

No telemetry or error reporting is wired in anywhere

adequate

None of 8,022 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.

Evidence
searched 8,022 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
06.9

No error reporter is wired in

adequate

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

Evidence
no error reporter initialised

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on orchardcms/orchardcore: 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.