3fce3b5 · 2,287 commits · 237 files
Issued 2026-09-23
Nothing significant. Questions worth asking about Architecture & Codebase — including AI provenance, Engineering Process & SDLC Maturity.
32 checks ran across 6 assessable dimensions. None found a significant problem; 4 raised something worth a question. 5 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- Words about people are today's: bands rather than exact shares, dates or day counts, and what the history measured rather than why.
- 3 findings from checks Borehole's calibration found wrong more often than right are no longer published.
- 1 finding about one contributor is withheld: this repository belongs to a person.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | adequate | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 03 | Organization & Key-Person Risk | not assessable | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | strong | |
| 07 | Fit with the Acquirer | not assessable |
- 1% 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 235 of 235 counted files
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑crates/core/flags/defs.rs is 8,162 lines, 46× this codebase's median file
adequateThe median source file here is 174 lines. 4 files exceed 1,740 lines, the largest being 8,162. 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 | crates/core/flags/defs.rs:1 — 8,162 lines (46× median) |
| line-count | crates/printer/src/standard.rs:1 — 3,988 lines (22× median) |
| line-count | crates/ignore/src/walk.rs:1 — 2,741 lines (15× median) |
| line-count | tests/regression.rs:1 — 1,745 lines (10× 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 · adequate · ratings ↑Change lands directly on the trunk rather than through review
adequateOnly 88 of 2,287 commits (3.8%) arrived either as a merge or as a squash carrying a pull-request reference. Both of the usual review workflows leave one of those traces, so either review happens somewhere this repository cannot see, or it is not happening. A buyer should establish which before relying on the code-review story they are told.
| reviewable-arrivals | 62 merge commits and 26 squashes with a pull-request reference, across 2,287 commits |
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 · not assessable · ratings ↑Not rated: this repository belongs to a person rather than an organisation, so a finding about one contributor would be about someone the address names; the public report does not carry those, and does not rate this dimension without them. The findings below are what it could still read.
83% of contributors committed exactly once and never returned
adequate413 of 497 contributors made a single commit. That is the signature of a codebase that is hard to join: people arrive, land one change and do not come back. It matters after an acquisition because putting new engineers on this system is the first thing anyone will try to do.
| one-commit-authors | 413 of 497 authors (83.1%) have exactly one commit |
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 ↑Change keeps returning to the same few files
adequateFive files out of 578 absorb 26% of all file-level change. Concentration like this is where debt is usually being serviced rather than repaid: the same code is reopened because it is load-bearing, fragile, or both. A repository cannot tell you which — that is a conversation with the team.
| touch-count | Cargo.lock — 495 commits touched it |
| touch-count | CHANGELOG.md — 294 commits touched it |
| touch-count | Cargo.toml — 242 commits touched it |
| touch-count | README.md — 179 commits touched it |
| touch-count | src/args.rs — 162 commits touched it |
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 ↑None of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| guardrail-scan | checked 7 standard paths across 237 tracked files; 0 present |
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. 3 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
2 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.
Engineering Process & SDLC Maturity
02 · high coverage- Incident response practice is not visible in a repository.
Organization & Key-Person Risk
03 · partial coverageNot rated: this repository belongs to a person rather than an organisation, so a finding about one contributor would be about someone the address names; the public report does not carry those, and does not rate this dimension without them.
- Hiring pipeline, bench depth and retention are not visible in a repository.
- Whether the dominant contributor is part of the transaction.
- Seniority, levelling and who actually mentors whom.
- Whether the team wants to stay after the deal closes.
Product & Engineering Maturity
04 · minimal coverage- Roadmap credibility requires the data room.
- Whether technical debt is acknowledged and funded.
Security & Reliability Posture
05 · partial coverage- Incident history and failure-mode analysis are not in the repository.
Observability & Operations
06 · partial coverage- Whether anyone watches the telemetry that exists.
Fit with the Acquirer
07 · none coverageNot rated: structurally not assessable from a repository.
- This is a Rust codebase. Does your engineering organisation already run Rust in production, or would this be the first?
- One contributor authored 68% of this history. Is that person part of the transaction, and for how long after it?
- The bulk of this system sits in crates/, src/, grep/. Which of your existing systems would each of those have to absorb or replace?
- There is no deployment configuration in the repository. Where does this actually run today, and who owns that environment?
- 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?
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/burntsushi/ripgrep/3fce3b5)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 — 27 signals that ran and did not fire
Appendix: rejection log — 27 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 — 23
| Signal | What it found |
|---|---|
| 04.debt_markers | debt markers are sparsemarkers 21 · per kloc 0.32 · lines read 66,324 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.499 · early delete per insert 0.48 |
| 06.telemetry_presence | this repository does not deploy a running service, so instrumentation is not expected of itbasis nothing in this repository starts a long-running server · files read 183 |
| 06.structured_logging | not a running service; structured logging is not expected of a librarybasis nothing in this repository starts a long-running server |
| 06.healthcheck_presence | not a running service, so a health endpoint is not expectedbasis nothing in this repository starts a long-running server |
| 03.active_contributors | withheld: this check's result would describe one person |
| 03.contributor_attrition | withheld: this check's result would describe one person |
| 02.ci_presence | CI configuration is present in the working treecount 2 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 18 · source 111 · test ratio 0.162 |
| 02.release_cadence | tags are presenttags 272 |
| 02.conventional_commits | commit subjects generally carry contentsampled 2,225 · low content share 0.059 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 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 259 · share of insertions 0.0017 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 14.39 · repeat share 0.067 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 578 · write once share 0.443 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.002 · product files 86 · distinct blocks 30,280 |
| 05.committed_secrets | no credential-shaped strings outside test and fixture pathsnote the working tree only; history is scanned at --deep · patterns 7 · files read 183 |
| 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 7 · truncated False · added lines 134,384 |
| 05.license_manifest_conflict | manifest and licence file agree on Unlicenselicense Unlicense |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.license_grant_unclear | the licence is recognisable as Unlicenseclass public-domain · license Unlicense |
Could not conclude, or did not apply — 4
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.dependency_sprawl | no recognised dependency manifest found |
| 05.dependency_pinning | no manifest whose pinning can be read without a lockfile |
| 05.container_runs_as_root | no Dockerfile to read |
| 05.license_copyleft_inherited | no third-party code is committed to this repository, so the licences it depends on are resolved at build time and are not readable here |
Anyone can check this report against the authoritative record — click the stamp, or enter F189-YVZP-ZBXQ at borehole.dev/verify.
The code commits to the 36 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/F189YVZPZBXQ?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-23 · shown | borehole 0.1.0.dev0 | 9 | adequate |
20 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 1 | adequate |
| 2026-10-03 | borehole 0.7.12 | 1 | adequate |
| 2026-10-03 | borehole 0.7.11 | 1 | adequate |
| 2026-10-02 | borehole 0.7.10 | 1 | adequate |
| 2026-10-01 | borehole 0.7.9 | 1 | adequate |
| 2026-09-30 | borehole 0.7.8 | 1 | strong |
| 2026-09-29 | borehole 0.7.6 | 1 | strong |
| 2026-09-28 | borehole 0.7.5 | 2 | adequate |
| 2026-09-27 | borehole 0.7.4 | 2 | adequate |
| 2026-09-27 | borehole 0.7.3 | 2 | adequate |
| 2026-09-27 | borehole 0.7.2 | 2 | adequate |
| 2026-09-27 | borehole 0.7.1 | 2 | adequate |
| 2026-09-26 | borehole 0.7.0 | 2 | adequate |
| 2026-09-26 | borehole 0.6.3 | 1 | strong |
| 2026-09-26 | borehole 0.6.2 | 1 | strong |
| 2026-09-25 | borehole 0.6.1 | 2 | strong |
| 2026-09-25 | borehole 0.6.0 | 5 | adequate |
| 2026-09-24 | borehole 0.4.0 | 5 | strong |
| 2026-09-24 | borehole 0.4.0.dev2 | 5 | strong |
| 2026-09-24 | borehole 0.4.0.dev1 | 5 | strong |
What this scan did with the repository — 5 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.4s | read repository metadata from the GitHub API | size mb: 5.6authenticated: False |
| 2.2s | cloned the repository to a temporary directory | depth: full |
| 3.0s | read the git history | commits: 2287tracked files: 237 |
| 11.0s | ran the deterministic checks | blame pass: Trueread working tree: True |
| 11.0s | deleting the working copy |
Total 11.0s ·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).