ccc89b8 · 9,226 commits · 645 files
Issued 2026-11-07
Nothing significant. Questions worth asking about Organization & Key-Person Risk.
105 checks ran across 6 assessable dimensions. None found a significant problem; 1 raised something worth a question. 3 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- states a policy on AI-generated contributions AI_POLICY.md:1
- 1 finding from checks Borehole's calibration found wrong more often than right is no longer published.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | not assessable | |
| 06 | Observability & Operations | not assessable | |
| 07 | Fit with the Acquirer | not assessable |
- 3% 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 644 of 644 counted files
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑clap_builder/src/builder/command.rs is 5,297 lines, 76× this codebase's median file
adequateThe median source file here is 69 lines. 7 files exceed 1,000 lines, the largest being 5,297. 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.
A note that does not affect this rating: measured against its own codebase's median, it is below the 85th percentile of 382 surveyed projects' largest files, where this check begins to count.
| line-count | clap_builder/src/builder/command.rs:1 — 5,297 lines (76× median) |
| line-count | clap_builder/src/builder/arg.rs:1 — 5,209 lines (75× median) |
| line-count | clap_builder/src/builder/value_parser.rs:1 — 2,697 lines (39× median) |
| line-count | clap_builder/src/parser/matches/arg_matches.rs:1 — 2,046 lines (29× median) |
| line-count | clap_builder/src/parser/parser.rs:1 — 1,686 lines (24× 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 · adequate · ratings ↑Bus factor 1: recent work is concentrated in one contributor
adequateIn the last 24 months, one contributor authored more than half of 642 non-merge commits among 93 authors; across all history, a quarter or more of 6,778. In a project with 93 recent contributors and 12 years of history, that is a question about one person's role rather than a fragile team — but it is the question to ask.
| git shortlog -sn | last 24 months: top author more than half of 642 commits; bus factor 1; 93 authors |
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 · strong · ratings ↑No finding. 19 checks ran and none fired; the rejection log below says why each did not.
Security & Reliability Posture
05 · not assessable · ratings ↑Not rated: only 16 of 34 checks could reach a conclusion here; the rest do not apply to this repository or could not read it. The findings below are what it could still read.
26 locked dependencies have published vulnerabilities, 8 high or critical
adequate26 of 472 locked dependencies match 45 published advisories in OSV, 8 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.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| Cargo.lock | Cargo.lock — zip 0.6.6: GHSA-m665-v7pm-7grj (critical), fixed in 9.0.5 |
| Cargo.lock | Cargo.lock — openssl 0.10.64: GHSA-8c75-8mhr-p7r9 (high), fixed in 0.10.78 |
| Cargo.lock | Cargo.lock — uucore 0.0.27: GHSA-fqf6-gxhh-2xhw (high), fixed in 0.6.0 |
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 · not assessable · ratings ↑Not rated: only 4 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it. What a person adds here.
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
1 check 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- 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 One contributor authored a quarter or more of the commits in this history. Is that person part of the transaction, and for how long after it?
- 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- 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 coverageNot rated: only 16 of 34 checks could reach a conclusion here; the rest do not apply to this repository or could not read 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 coverageNot rated: only 4 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
- 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 Rust codebase. Does your engineering organisation already run Rust in production, or would this be the first?
- The bulk of this system sits in src/, clap_complete/, clap_derive/. Which of your existing systems would each of those have to absorb or replace?
- Nothing in the repository says how this is deployed. Is it shipped as a library, a binary or a service, and if it runs somewhere, 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?
- 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/clap-rs/clap/ccc89b8)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 — 102 signals that ran and did not fire
Appendix: rejection log — 102 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 — 62
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 2,572 · top5 share 0.11 |
| 04.debt_markers | debt markers are sparsemarkers 22 · per kloc 0.21 · lines read 103,132 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.797 · early delete per insert 0.778 |
| 04.fixes_with_tests | fixes usually come with a testfixes 112 · share 0.58 · with tests 65 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 124 · compat files 0 |
| 06.telemetry_presence | this repository does not deploy a running service, so instrumentation is not expected of itbasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere · files read 532 |
| 06.healthcheck_presence | not a running service, so a health endpoint is not expectedbasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.active_contributors | more than one contributor active in the trailing yearall time 602 · active 12mo 46 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 602 · directories 10 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 602 · one off share 0.576 |
| 03.contributor_attrition | the dominant contributor is still activeauthors 602 · top share a quarter or more · top contributor last committed within the last three months |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 92 |
| 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 9 · joined 6 · regular last year 7 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 230 · window last 24 months · with tracked 32 |
| 02.ci_presence | CI configuration is present in the working treecount 9 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 242 · source 346 · test ratio 0.699 |
| 02.release_cadence | tags are presenttags 666 |
| 02.conventional_commits | commit subjects generally carry contentsampled 6,944 · low content share 0.017 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 9 · with tests 2 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 2 · test files 326 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 9 |
| 02.revert_share | change is rarely undoneshare 0.003 · reverts 2 · recent commits 622 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 1 · commits since 1 · days since lockfile changed 5 |
| 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 5 · ci configs 9 · product files 124 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.011 · merges 189 · long lived 2 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.0 · commits 492 · over 2000 lines 0 |
| 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 353 · share of insertions 0.0008 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 19.13 · repeat share 0.183 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 167 · write once share 0.18 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.003 · product files 124 · distinct blocks 21,402 |
| 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 532 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.secrets_in_history | no credential-shaped string was ever added outside test and fixture pathspatterns 8 · truncated False · added lines 409,125 |
| 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 44 · pipe to shell 0 · unpinned third party 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_manifest_conflict | manifest and licence file agree on Apache-2.0 and MITlicense MIT OR Apache-2.0 |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.license_grant_unclear | the licence is recognisable as Apache-2.0class permissive · license Apache-2.0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 1 · files with deprecations 40 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 203 · added in two years 27 · 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 · unreleased changes 0 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 0.5 · days since last tag 20 · commits last 90 days 157 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 23 · on branch 347 · tags in window 370 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 40
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.dependency_sprawl | no recognised dependency manifest found |
| 04.test_growth | Rust keeps unit tests inside the files they test, which a count by file name cannot see |
| 04.eol_runtime | no pinned runtime version to check |
| 04.schema_churn | no schema migrations to read |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.structured_logging | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 06.telemetry_depth | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.print_logging | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.correlation_ids | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.error_reporting | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.alert_rules | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.deployed_image_floats | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.environment_branching | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.release_markers | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 01.swallowed_errors | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 01.build_reproducibility | no product Dockerfile to read |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.dependency_pinning | no manifest whose pinning can be read without a lockfile |
| 05.container_runs_as_root | no Dockerfile to read |
| 05.outbound_timeouts | not a running service |
| 05.migration_reversibility | too few migrations to judge |
| 05.sql_from_strings | not a running service; a library that builds SQL is doing its job |
| 05.shell_from_strings | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 05.unsafe_deserialization | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 05.tls_verification_off | not assessed for Rust, 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_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 |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | not a running service |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; OSV crates.io clap (an empty record for a package published here), OSV crates.io clap_builder (an empty record for a package published here), OSV crates.io clap_complete (an empty record for a package published here), OSV crates.io clap_complete_nushell (an empty record for a package published here), OSV crates.io clap_derive (an empty record for a package published here), OSV crates.io clap_lex (an empty record for a package published here), OSV crates.io clap_mangen (an empty record for a package published here) did not; NVD: 1 record names clap with nothing tying it to this repository (CVE-2026-84450) |
| 05.advisory_record | record incomplete: no advisory against the project in the last 24 months; OSV crates.io clap (an empty record for a package published here), OSV crates.io clap_builder (an empty record for a package published here), OSV crates.io clap_complete (an empty record for a package published here), OSV crates.io clap_complete_nushell (an empty record for a package published here), OSV crates.io clap_derive (an empty record for a package published here), OSV crates.io clap_lex (an empty record for a package published here), OSV crates.io clap_mangen (an empty record for a package published here) did not answer; NVD: 1 record names clap with nothing tying it to this repository (CVE-2026-84450) |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited list |
Anyone can check this report against the authoritative record — click the stamp, or enter HR5F-43AF-YFQT 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/HR5F43AFYFQT?via=badge)
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 | size mb: 20.3authenticated: False |
| 4.0s | cloned the repository to a temporary directory | depth: full |
| 8.8s | read the git history | commits: 9226tracked files: 645 |
| 75.8s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 75.8s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 87.3s | kept the facts, never the source, for re-reading under new checks | |
| 87.3s | deleting the working copy |
Total 87.3s ·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).