e9b5a3e · 12,673 commits · 1,861 files
Issued 2026-10-03
Nothing significant. Questions worth asking about Security & Reliability Posture, Engineering Process & SDLC Maturity.
104 checks ran across 6 assessable dimensions. None found a significant problem; 4 raised something worth a question. 6 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 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 | strong | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | strong | |
| 07 | Fit with the Acquirer | not assessable |
- 22% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- no widespread author/committer date divergence
- deep scan blamed 1,839 of 1,839 counted files
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑No finding. 11 checks ran and none fired; the rejection log below says why each did not.
Engineering Process & SDLC Maturity
02 · adequate · ratings ↑Nothing in the history is tagged as a release
adequateAcross 17.4 years of history there is not one tag. There may still be a deployment process, but this repository holds no record of what shipped when — which is the record a buyer needs to reconstruct an incident or a regression after the fact.
| tag-list | 0 tags across 12,673 commits and 6348 days |
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.
Organization & Key-Person Risk
03 · adequate · ratings ↑The next contributor after the top one has not committed here for more than a year
adequateThe #3 contributor of the last three years (less than a quarter of the commits) has not committed here for more than a year, while the repository is still active. These are the people a buyer assumes would step up if the top contributor stopped. The history shows only that no commits of theirs landed here, not why.
| git shortlog -sn | the #3 contributor of the last three years (less than a quarter of the commits) has not committed here for more than a year |
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.
Product & Engineering Maturity
04 · adequate · ratings ↑API v1 and v2 have been served together for 136 months
adequatev2 first appeared in Jul 2015, and v1 is still in the code 136 months later. Two versions mean two surfaces to secure, document and support. Ask who still calls the old one, and whether retiring it is planned.
| config/routes.rb | config/routes.rb — v1 since Nov 2009 |
| config/routes.rb | config/routes.rb — v2 since Jul 2015 |
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 ↑1 Dockerfile runs 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.
| no-USER-instruction | Dockerfile — runs as root |
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.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| vendor/assets | vendor/assets — 10 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.
5 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-09-30. 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 5 of them are fixed in the code you ship could not be told from this history. Answer lives in: the release you run, set against each fixed version.
A note that does not affect this rating: it describes the project's advisory record, and no advisory in it is known to affect the surveyed commit.
| GHSA-4v88-44mv-8c5r | 2026-09-30: GHSA-4v88-44mv-8c5r (moderate), fixed in a881d8d: Expired organization invitations could still be accepted |
| GHSA-wpx5-r587-w6j2 | 2026-09-30: GHSA-wpx5-r587-w6j2 (moderate), fixed in fdd3a19: Email-change confirmation mails could be sent far more often than intended |
| GHSA-p37h-pvp2-fh88 | 2026-09-22: GHSA-p37h-pvp2-fh88 (moderate), fixed in c08c02b: Unbounded number of regex evaluations per request in OIDC access policies |
| GHSA-wj84-52wx-4c26 | 2026-09-15: GHSA-wj84-52wx-4c26 (high), fixed in f6f674e: Organization admins can escalate to owner through gem transfers |
| GHSA-9j48-x3c3-mrp2 | 2026-07-22: GHSA-9j48-x3c3-mrp2 (high), fixed in d3d11c0: Possible leak of legacy API keys via improper cache configuration |
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 · strong · ratings ↑No finding. 16 checks ran and none fired; the rejection log below says why each did not.
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
3 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 1,275 product files. Where does the design live, and who holds it?
- measured The repository pulls code in through git submodules (.gitmodules). A buyer receives pointers, not that code. Can every submodule be fetched without the team's credentials, and who owns each one?
- 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 497 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 379 commits landed in the last year, against 220 the year before (+72%). What drove it: new people, a deadline, or code produced faster than before?
- 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 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 app/, public/, config/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (Dockerfile and 1 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/rubygems/rubygems.org/e9b5a3e)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 — 98 signals that ran and did not fire
Appendix: rejection log — 98 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 — 76
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 3,387 · top5 share 0.084 |
| 04.debt_markers | debt markers are sparsemarkers 23 · per kloc 0.2 · lines read 112,708 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 1.633 · early test per code 0.366 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.43 · early delete per insert 0.885 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fixes_with_tests | fixes usually come with a testfixes 70 · share 0.586 · with tests 41 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.001 · code files 914 · compat files 1 |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 57 |
| 06.structured_logging | a structured logging library is referencedmatches 2 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.telemetry_depth | the service is visible in more than one way |
| 06.correlation_ids | a request can be followed through the logstracing True · request id sites 13 |
| 06.error_reporting | an error reporter is initialisedinitialised 1 · config files 0 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.deployed_image_floats | every deployed image names a versionimages 5 · floating 0 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 0 · release commits 0 · changelog commits 19 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 17.4 · window last 24 months · authors 497 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 497 · active 12mo 46 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 497 · one off share 0.449 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 497 · 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 72 |
| 03.bus_factor_trend | the team has not narrowed to one person |
| 03.joiners_and_leavers | the team is not shrinkingleft 6 · joined 15 · regular last year 18 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 202 · window last 24 months · with tracked 10 |
| 02.ci_presence | CI configuration is present in the working treecount 6 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 525 · source 1,428 · test ratio 0.368 |
| 02.conventional_commits | commit subjects generally carry contentsampled 10,246 · low content share 0.007 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 552 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 6 |
| 02.revert_share | change is rarely undoneshare 0.003 · reverts 2 · recent commits 600 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 1 · commits since 2 · days since lockfile changed 0 |
| 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 2 · ci configs 6 · product files 914 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.01 · merges 199 · long lived 2 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.011 · commits 537 · over 2000 lines 6 |
| 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 3 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 16.93 · repeat share 0.019 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 1,249 · write once share 0.211 |
| 01.oversized_modules | no module is an outlier against this codebase's own normlargest 1,614 · threshold 1,000 · median lines 29 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0066 · product files 903 · distinct blocks 17,502 |
| 01.swallowed_errors | errors are rarely thrown awayloc 114,212 · files 1 · per kloc 0.01 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 3 |
| 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 1,507 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.dependency_pinning | a lockfile is committed, so builds are reproduciblelockfile True |
| 05.license_present | a licence file is presentfound True |
| 05.secrets_in_history | no credential-shaped string was ever added outside test and fixture pathspatterns 8 · truncated False · added lines 330,546 |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.supply_chain_pinning | third-party build steps are pinned, or fewaction refs 36 · pipe to shell 0 · unpinned third party 0 |
| 05.migration_reversibility | migrations can be rolled backshare 0.004 · migrations 244 · 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.known_vulnerabilities | no locked dependency has a published advisoryadvisories 0 · dependencies 299 · high or critical 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 21 |
| 05.license_grant_unclear | the licence is recognisable as MITclass permissive · license MIT |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 246 · added in two years 20 · removed within 60 days 1 |
| 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 0 · unreleased changes 0 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 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 — 22
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.dependency_sprawl | no recognised dependency manifest found |
| 04.schema_churn | columns, once added, stay |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 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 |
| 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.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 |
| 04.deprecations_lingering | few deprecations have outlived two years |
| 04.releases_stopped | too few tagged releases to judge a cadence |
| 04.release_branch | too few release tags to tell |
| 05.project_advisories | could not tell whether 10 published advisories affect the surveyed code: its version could not be placed |
Anyone can check this report against the authoritative record — click the stamp, or enter RMRY-K4MH-6BF0 at borehole.dev/verify.
The code commits to the 106 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/RMRYK4MH6BF0?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-10-03 · shown | borehole 0.7.12 | 8 | adequate |
8 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 8 | adequate |
| 2026-10-03 | borehole 0.7.11 | 8 | adequate |
| 2026-10-02 | borehole 0.7.10 | 8 | adequate |
| 2026-10-01 | borehole 0.7.9 | 8 | adequate |
| 2026-09-30 | borehole 0.7.8 | 8 | adequate |
| 2026-09-29 | borehole 0.7.6 | 8 | adequate |
| 2026-09-28 | borehole 0.7.5 | 8 | adequate |
| 2026-09-28 | borehole 0.7.4 | 8 | 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 — 7 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 | read repository metadata from the GitHub API | authenticated: False |
| 4.3s | cloned the repository to a temporary directory | depth: full |
| 7.8s | read the git history | commits: 12673tracked files: 1861 |
| 131.2s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 131.2s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 150.9s | kept the facts, never the source, for re-reading under new checks | |
| 150.9s | deleting the working copy |
Total 150.9s ·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).