ed57fa2 · 30,954 commits · 3,769 files
Issued 2026-09-27
Nothing significant. Questions worth asking about Observability & Operations, Security & Reliability Posture.
103 checks ran across 6 assessable dimensions. None found a significant problem; 4 raised something worth a question. 10 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 04.62 Releases are cut from another branch than the one surveyed
- Words about people are today's: bands rather than exact shares, dates or day counts, and what the history measured rather than why.
- 2 findings from checks Borehole's calibration found wrong more often than right are no longer published.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | adequate | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | strong | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 2% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- 44% of commits show author/committer date divergence, which is the shape of replayed history that can drop trailers
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑core/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.
| line-count | core/db/migrate/20160101010000_solidus_one_four.rb:1 — 1,068 lines (31× median) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Engineering Process & SDLC Maturity
02 · strong · ratings ↑No finding. 16 checks ran and none fired; the rejection log below says why each did not.
Organization & Key-Person Risk
03 · strong · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · adequate · ratings ↑Releases 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.
| 7bc987bd7 | tag v4.7.1 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Security & Reliability Posture
05 · adequate · ratings ↑The 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 | .github/workflows/backport.yml:30 — action pinned by tag |
| .github/workflows/install_dummy_app.yml | .github/workflows/install_dummy_app.yml:24 — action pinned by tag |
| .dockerdev/Dockerfile | .dockerdev/Dockerfile:32 — download piped into a shell |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
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 | storefront/templates/vendor/assets — 2 tracked files, no licence file |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
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.
| GHSA-92gv-2pxv-7gjg | 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 |
| GHSA-c2fq-w6qj-3hj4 | 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 |
| GHSA-g82m-w3m9-rrwh | 2026-09-09: GHSA-g82m-w3m9-rrwh (high): Guest token fixation in Solidus Storefront enables cart takeover and order data disclosure |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Observability & Operations
06 · adequate · ratings ↑No 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.
| telemetry-scan | searched 2,704 tracked text files for 16 known instrumentation libraries; 0 matched |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
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.
| logging-scan | searched 2,704 files for 10 structured logging libraries; 0 matched |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
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.
| request ids | no request id, correlation id or tracing found |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
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.
| error reporting | no error reporter initialised |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
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 | docker-compose.yml:29 — image without a version |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Fit with the Acquirer
07 · not assessable · ratings ↑Not rated: structurally not assessable from a repository. What a person adds here.
Check it on the running system
8 checks against the running system follow from the findings above: what a buyer's engineer will try, how to run it first, and what to have ready. A paid survey of this repository includes them.
A paid survey of a public repository is also reviewed: a language model reads each finding against the code and withdraws only findings it judges the code contradicts, each listed with its reason. The review is a language model's reading of the findings against the code, and it can be wrong. It never adds a finding, never raises a band, and never removes a finding from a proven check or an advisory that affects the surveyed version.
What a person adds
The survey reads what the repository can show. The code cannot settle these questions, and on them this report states nothing. Each says where its answer lives: your own engineer, the company, or an assessor you choose can settle it. Questions marked measured open with something this repository shows.
Architecture & Codebase — including AI provenance
01 · full coverage- measured No architecture or design document is in the tree, across 2,750 product files. Where does the design live, and who holds it?
- Is the architecture right for the next three years of the product?
- Were the home-grown components reasonable choices when they were made, and are they now?
Engineering Process & SDLC Maturity
02 · high coverage- Is review real or a rubber stamp? Comment depth and time to approve need the pull request history.
- Is delivery planned and measured, or heroic?
- How are incidents run, reviewed and learned from?
Organization & Key-Person Risk
03 · partial coverage- measured 1,162 people have committed here. Which of them are you acquiring, and which are you replacing?
- Who mentors whom, and would that survive a departure?
- Can the team grow, and who stands behind the top three contributors?
- Is the seniority mix sound, and will pay survive your salary bands?
- Is the pace sustainable? Commit times cannot say: git keeps no reliable local time.
- Does the team want to stay after close?
- How are decisions made and disagreements resolved?
Product & Engineering Maturity
04 · minimal coverage- measured 553 commits landed in the last year, against 1,053 the year before (-47%). Is that maintenance mode, a pivot, or fewer people working on it? The count looks the same for all three.
- Can this team deliver the stated roadmap on the stated timeline?
- Does leadership know about the debt, and is time budgeted to repay it?
- Is the engineering shape consistent with the commercial story?
Security & Reliability Posture
05 · partial coverage- measured 05.5 found credential-shaped strings in this repository. Was each one revoked at the provider? Deleting it from the code revokes nothing; only the provider's audit log shows that it was.
- measured No threat model is in the tree of what looks like a running service. Does one exist elsewhere, and who owns it?
- What has actually broken, how often, and how badly?
- What did external testing find, and was it fixed?
- What is the SOC 2, ISO 27001 or GDPR status, and where is the evidence?
Observability & Operations
06 · partial coverage- measured Nothing in the tree backs up or restores data. How is data backed up, and has a restore ever been rehearsed?
- measured No alert rule is defined in the repository. Where are alerts defined, who receives them, and when did one last fire?
- Are the dashboards opened, the alerts acknowledged and the pages answered?
- Are the service-level objectives actually met?
- Who carries the pager, and how often does it go off?
- What does it cost to run, and how much headroom is there?
Fit with the Acquirer
07 · none coverageNot rated: structurally not assessable from a repository.
- This is primarily a Ruby codebase. Does your engineering organisation already run Ruby in production, or would this be the first?
- The bulk of this system sits in core/, i18n/, backend/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (.dockerdev/Dockerfile and 5 more). Does that match your deployment and on-call model, or does it need rehosting first?
- What is your tolerance for the findings above remaining unaddressed for the first two quarters after close, given everything else that will compete for this team's time?
- Which of these systems duplicate yours, and which get retired?
- What will integration cost, and in what order?
- Where does the team land in your organisation, and who reports to whom?
- Are there earn-outs, retention packages or contractor IP to assign?
- Do customer contracts limit hosting, regions or vendors?
A human assessment is Borehole's own paid service, €12,000+ (total price is determined per engagement; travel billed at cost). It is not independent of this report: the same business produced both. It is a separate contract, with its own scope, terms and reliance.
Embed the badge
Tied to this commit and this date, and it fades after 90 days — an honest badge is one that expires. A repository with significant findings gets a neutral "read" badge rather than a red one: the library is where the range is visible, not someone else's README.
[](/r/solidusio/solidus/ed57fa2)If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
Rejection log — 93 signals that ran and did not fire
Appendix: rejection log — 93 signals that ran and did not fire
Published on purpose. A signal that looked and decided not to fire has told you something, and this is the calibration data behind every threshold above.
Looked, and found nothing — 70
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 35,412 · top5 share 0.02 |
| 04.debt_markers | debt markers are sparsemarkers 39 · per kloc 0.16 · lines read 238,014 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 1.081 · early test per code 0.723 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.677 · early delete per insert 0.872 |
| 04.fixes_with_tests | fixes usually come with a testfixes 201 · share 0.428 · with tests 86 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.073 · code files 1,585 · compat files 116 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 5 · release commits 0 · changelog commits 8 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 18.6 · window last 24 months · authors 1,162 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 1,162 · active 12mo 31 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 1,162 · directories 10 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 1,162 · one off share 0.474 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 1,162 · top share less than a quarter · top contributor last committed more than three years ago |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 56 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.bus_factor_trend | the team has not narrowed to one person |
| 03.joiners_and_leavers | the team is not shrinkingleft 11 · joined 11 · regular last year 17 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 420 · window last 24 months · with tracked 11 |
| 02.ci_presence | CI configuration is present in the working treecount 13 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 890 · source 2,402 · test ratio 0.371 |
| 02.release_cadence | tags are presenttags 214 |
| 02.conventional_commits | commit subjects generally carry contentsampled 26,335 · low content share 0.007 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 13 · with tests 3 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 933 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 13 |
| 02.revert_share | change is rarely undoneshare 0.005 · reverts 8 · recent commits 1,606 |
| 02.flaky_test_markers | tests are not retried until they passtest retries 0 · suite retries 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 1 · ci configs 13 · product files 1,585 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.168 · merges 386 · long lived 65 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.002 · commits 1,450 · over 2000 lines 3 |
| 01.burst_import | no commit run met both the rate and the net-addition thresholdgap seconds 180 · min add ratio 3.0 · min net added 2,000 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 0 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 27.47 · repeat share 0.055 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 2,184 · write once share 0.204 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0087 · product files 1,513 · distinct blocks 30,212 |
| 01.swallowed_errors | errors are rarely thrown awayloc 240,711 · files 0 · per kloc 0.0 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 2 |
| 01.unfinished_migration | no language migration is stalled halfway |
| 01.weights_in_git | no model weights are committedfiles 0 |
| 05.committed_secrets | no credential-shaped strings outside test and fixture pathsnote the working tree only; the history is 05.5 · patterns 8 · files read 2,704 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.dependency_pinning | dependencies are substantially pinnedunpinned 0 |
| 05.license_present | a licence file is presentfound True |
| 05.container_runs_as_root | every shipped Dockerfile drops to a non-root user or builds on a non-root base imagedockerfiles 2 |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.migration_reversibility | migrations can be rolled backshare 0.01 · migrations 97 · irreversible 1 |
| 05.sql_from_strings | no SQL is assembled from strings in product codefiles 0 · sites 0 · value interpolated 0 |
| 05.shell_from_strings | product code does not build shell commands from stringssites 0 |
| 05.unsafe_deserialization | no code-executing deserialiser in product codesites 0 |
| 05.tls_verification_off | no TLS verification is switched off in product codefiles 0 · sites 0 · pinned instead 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 0 |
| 05.credentials_in_deploy_config | deployment configuration references secrets, never holds themfiles 0 · sites 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_copyleft_inherited | every licence found in vendored code is permissive or weak-copyleftvendored paths 177 |
| 05.license_grant_unclear | the licence is recognisable as BSD-3-Clauseclass permissive · license BSD-3-Clause |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.api_versions_coexisting | one API version is served, or none |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 1 · files with deprecations 35 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 188 · added in two years 6 · removed within 60 days 0 |
| 04.ci_platforms_dropped | no platform was dropped from CI in the last two years |
| 04.repository_status | the README's first screen states no end, move or freezestatements 0 |
| 02.development_elsewhere | nothing says development happens elsewhereno pr statements 0 · mirror statements 0 · replayed commit share 0.0 |
| 05.licence_changes | the root licence has not changed in the history readlicence versions 1 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 10.0 · days since last tag 18 · commits last 90 days 350 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 23
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.dependency_sprawl | no recognised dependency manifest found |
| 04.eol_runtime | no pinned runtime version to check |
| 04.schema_churn | columns, once added, stay |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.telemetry_depth | none at all is 06.1 |
| 06.print_logging | not assessed for Ruby: its logger calls are not read |
| 06.alert_rules | no alert rules in the repository; they may live in a console |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 02.dependency_update_cadence | no lockfile to date |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.outbound_timeouts | not assessed for Ruby, the language the product is written in: this check's patterns read other languages only |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.known_vulnerabilities | no lockfile this survey can read, or a collector older than 0.4.0 |
| 05.public_env_secret | not a frontend |
| 05.unsafe_html | not a frontend |
| 05.source_maps_shipped | not a frontend |
| 05.cleartext_traffic | not a mobile app |
| 05.dataset_provenance | not a data or machine-learning repository |
| 05.license_manifest_conflict | no packaging manifest states a licence |
| 04.flags_accumulating | few or no feature flags in the history |
| 05.project_advisories | could not tell whether 3 published advisories affect the surveyed code: its version is only known to be at least 4.7.0 |
Anyone can check this report against the authoritative record — click the stamp, or enter SHPM-NF23-QZT2 at borehole.dev/verify.
The code commits to the 105 checks this run performed, the bands they produced, and the commit they were read at. It does not cover checks written since.
Put the mark in your README
The image is wrapped in a link to the verification page, so a reader can check it rather than take it on trust. If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
[](https://borehole.dev/verify/SHPMNF23QZT2?via=badge)
A survey is a reading by a particular version of the assessor. Older readings are kept rather than replaced, because a verification mark attests to the survey it was issued for — overwriting one would make every code already in circulation read as tampered.
| Read | Assessor | Findings | Band |
|---|---|---|---|
| 2026-09-27 · shown | borehole 0.7.4 | 12 | adequate |
9 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 12 | strong |
| 2026-10-03 | borehole 0.7.12 | 12 | strong |
| 2026-10-03 | borehole 0.7.11 | 12 | strong |
| 2026-10-02 | borehole 0.7.10 | 12 | strong |
| 2026-10-01 | borehole 0.7.9 | 12 | adequate |
| 2026-09-30 | borehole 0.7.8 | 12 | adequate |
| 2026-09-29 | borehole 0.7.6 | 12 | adequate |
| 2026-09-28 | borehole 0.7.5 | 12 | adequate |
| 2026-09-27 | borehole 0.7.3 | 12 | adequate |
Where this scan ran
This scan ran on ordinary cloud infrastructure (cloud-run), not in a hardware-isolated confidential VM. Nothing about it is attested by Google.
What an attested survey proves, and what it does not.
What this scan did with the repository — 3 steps
Written by the steps themselves as they ran, not described afterwards. A hand-written account of a data flow drifts the first time somebody changes the flow and not the account.
| At | Step | Detail |
|---|---|---|
| 0.0s | re-read from the facts kept at the last survey; nothing was cloned | facts version: a9f6f77559f9717d |
| 40.5s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 40.5s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
Total 40.5s ·source content sent off this machine: none · calls to a language model: 0 · the clone was deleted when the survey ended
An automated reading of a repository's code and its history up to one commit, with public advisory records. It may be wrong, it is not legal, financial, investment or security advice, and it does not replace diligence by a qualified person. It is provided for information: nobody may rely on it (Borehole's terms, section 3).