bac35f5 · 10,650 commits · 1,791 files
Issued 2026-09-25
Nothing significant. Questions worth asking about Security & Reliability Posture, Architecture & Codebase — including AI provenance.
94 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.
- Words about people are today's: bands rather than exact shares, dates or day counts, and what the history measured rather than why.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | adequate | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | strong | |
| 07 | Fit with the Acquirer | not assessable |
- 18% 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,642 of 1,642 counted files
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑crates/uv-lock/src/lock/mod.rs is 11,107 lines, 60× this codebase's median file
adequateThe median source file here is 185 lines. 36 files exceed 1,850 lines, the largest being 11,107. 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/uv-lock/src/lock/mod.rs:1 — 11,107 lines (60× median) |
| line-count | crates/uv-cli/src/lib.rs:1 — 7,984 lines (43× median) |
| line-count | crates/uv/src/settings.rs:1 — 5,512 lines (29× median) |
| line-count | crates/uv-python/src/discovery.rs:1 — 4,851 lines (26× median) |
| line-count | crates/uv-pep440/src/version.rs:1 — 4,805 lines (25× 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 ↑Tests are retried until they pass
adequateThe suite is configured to retry failing tests (crates/uv-client/tests/it/cached_client.rs). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
| crates/uv-client/tests/it/cached_client.rs | crates/uv-client/tests/it/cached_client.rs:73 — test retry |
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 ↑Regular contributors fell from 48 to 27 in a year
adequate28 people who committed regularly the year before made no commits in the last year, and 17 new regular contributors arrived. Ask whether the work they did is still covered.
| regular contributors by year | 48 then 27; 28 stopped committing, 17 began |
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. 16 checks ran and none fired; the rejection log below says why each did not.
Security & Reliability Posture
05 · adequate · ratings ↑2 Dockerfiles run 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 |
| no-USER-instruction | crates/uv-trampoline/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.
The build runs third-party code it does not pin
adequate1 step pipes 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/test-system.yml | .github/workflows/test-system.yml:681 — 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.
11 locked dependencies have published vulnerabilities, 4 high or critical
adequate11 of 842 locked dependencies match 19 published advisories in OSV, 4 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.
| uv.lock | uv.lock — anyio 4.13.0: GHSA-82r6-8w77-94w6 (critical), fixed in 4.14.2 |
| uv.lock | uv.lock — gitpython 3.1.58: GHSA-284h-m62q-gf8w (critical), fixed in 3.1.59 |
| uv.lock | uv.lock — mkdocs-material 9.7.6: GHSA-xvg9-69gf-fjrf (moderate), fixed in 9.7.7 |
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. 15 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 907 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 618 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- 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 A threat model is in the tree (agents/references/repository-threat-model.md). Does it name the assets this code actually handles, and is it current against the deployment?
- 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- 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 crates/, changelogs/, agents/. 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/astral-sh/uv/bac35f5)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 — 88 signals that ran and did not fire
Appendix: rejection log — 88 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 — 57
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 4,164 · top5 share 0.048 |
| 04.debt_markers | debt markers are sparsemarkers 362 · per kloc 0.73 · lines read 495,237 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.556 · early delete per insert 0.541 |
| 04.fixes_with_tests | fixes usually come with a testfixes 516 · share 0.405 · with tests 209 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.002 · code files 582 · compat files 1 |
| 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 1,517 |
| 06.structured_logging | not a running service; structured logging is not expected of a librarybasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 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.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 3.0 · window last 24 months · authors 618 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 618 · active 12mo 199 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 622 · directories 7 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 618 · one off share 0.731 |
| 03.contributor_attrition | the dominant contributor is still activeauthors 618 · 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 475 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.bus_factor_trend | the team has not narrowed to one person |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 491 |
| 02.ci_presence | CI configuration is present in the working treecount 47 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 148 · source 782 · test ratio 0.189 |
| 02.release_cadence | tags are presenttags 317 |
| 02.conventional_commits | commit subjects generally carry contentsampled 10,650 · low content share 0.0 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 47 · with tests 8 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 635 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 47 |
| 02.revert_share | change is rarely undoneshare 0.007 · reverts 34 · recent commits 5,052 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 7 · commits since 14 · days since lockfile changed 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 5 · ci configs 47 · product files 582 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.013 · commits 4,330 · over 2000 lines 56 |
| 01.burst_import | the largest burst was merged pull requests, each developed and reviewed on its own branch (100% of its lines), which explains the rate: translations arrive from a vendor in bulk, dependencies and generated code are committed whole, a merged pull request is dated when it merged, not when it was written, and a branch merged by a merge commit was reviewed as one piecelargest commits 2c085eb..fcda5c4 · bursts explained 1 · largest net added 2,436 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 250 · share of insertions 0.0001 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 14.56 · repeat share 0.001 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 4,197 · write once share 0.462 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0056 · product files 577 · distinct blocks 191,940 |
| 01.swallowed_errors | errors are rarely thrown awayloc 496,738 · files 3 · per kloc 0.01 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 7 |
| 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 7 · files read 1,517 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.license_present | a licence file is presentfound True |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 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 |
| 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 3 |
| 05.license_manifest_conflict | manifest and licence file agree on MITlicense MIT |
| 05.license_vendored_unlicensed | all 3 vendored components carry a licence filecomponents 3 |
| 05.license_grant_unclear | the licence is recognisable as Apache-2.0class permissive · license Apache-2.0 |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 0 · files with deprecations 6 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 381 · added in two years 159 · removed within 60 days 0 |
| 04.ci_platforms_dropped | no platform was dropped from CI in the last two years |
Could not conclude, or did not apply — 31
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.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 |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.dependency_pinning | no manifest whose pinning can be read without a lockfile |
| 05.secrets_in_history | no credential-shaped string was added outside test and fixture paths in the 3,947 most recent commits scanned; older history was not 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.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 |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | not a running service |
Anyone can check this report against the authoritative record — click the stamp, or enter TM4J-6APF-S6WR at borehole.dev/verify.
The code commits to the 94 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/TM4J6APFS6WR?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-25 · shown | borehole 0.6.1 | 6 | adequate |
15 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 5 | strong |
| 2026-10-03 | borehole 0.7.12 | 5 | strong |
| 2026-10-03 | borehole 0.7.11 | 5 | strong |
| 2026-10-02 | borehole 0.7.10 | 5 | strong |
| 2026-10-01 | borehole 0.7.9 | 5 | strong |
| 2026-09-30 | borehole 0.7.8 | 5 | adequate |
| 2026-09-29 | borehole 0.7.6 | 6 | adequate |
| 2026-09-28 | borehole 0.7.5 | 6 | adequate |
| 2026-09-28 | borehole 0.7.4 | 5 | adequate |
| 2026-09-27 | borehole 0.7.3 | 5 | adequate |
| 2026-09-27 | borehole 0.7.2 | 5 | adequate |
| 2026-09-27 | borehole 0.7.1 | 5 | adequate |
| 2026-09-26 | borehole 0.7.0 | 5 | adequate |
| 2026-09-26 | borehole 0.6.3 | 6 | adequate |
| 2026-09-26 | borehole 0.6.2 | 6 | 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 | size mb: 204.4authenticated: False |
| 26.4s | cloned the repository to a temporary directory | depth: full |
| 47.7s | read the git history | commits: 10650tracked files: 1791 |
| 346.4s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 346.5s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 376.8s | kept the facts, never the source, for re-reading under new checks | |
| 376.8s | deleting the working copy |
Total 376.8s ·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).