Read 2026-10-04
solidusio/solidus: technical due diligence, read from its repository
What Borehole read in solidusio/solidus's code and history at ed57fa2: 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 | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | strong |
| 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
strongcore/db/migrate/20160101010000_solidus_one_four.rb is 1,068 lines, 31× this codebase's median file
adequateThe median source file here is 34 lines. 1 file exceed 1,000 lines, the largest being 1,068. 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.
core/db/migrate/20160101010000_solidus_one_four.rb:1 — 1,068 lines (31× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v4.7.1, is not on the branch this survey read; the newest release on it is v4.7.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v4.7.1 |
Security & Reliability Posture
strongThe build runs third-party code it does not pin
adequate3 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; 2 steps pipe a download straight into a shell. 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/backport.yml:30 — action pinned by tag |
.github/workflows/install_dummy_app.yml:24 — action pinned by tag |
.dockerdev/Dockerfile:32 — download piped into a shell |
1 vendored component 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.
storefront/templates/vendor/assets — 2 tracked files, no licence file |
3 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-09-09. 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 3 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 4.7.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 4 records name solidus with nothing tying them to this repository (CVE-2024-4859, CVE-2025-22872, CVE-2026-54506, …).
| 2026-09-09: GHSA-92gv-2pxv-7gjg (moderate), fixed in >= 4.7.1: Unauthenticated tampering with and disclosure of guest-checkout credit cards via nil-user ability |
| 2026-09-09: GHSA-c2fq-w6qj-3hj4 (moderate), fixed in >= 4.7.1: Arbitrary payment amounts via the orders and payments APIs enable order underpayment |
| 2026-09-09: GHSA-g82m-w3m9-rrwh (high): Guest token fixation in Solidus Storefront enables cart takeover and order data disclosure |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 2,704 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 2,704 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 2,704 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 |
1 of 6 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:29 — 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 solidusio/solidus: 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.