a586f69 · 11,469 commits · 573 files
Issued 2026-10-04
Nothing significant. Questions worth asking about Security & Reliability Posture, Organization & Key-Person Risk.
106 checks ran across 6 assessable dimensions. None found a significant problem; 2 raised something worth a question. 5 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 04.62 Releases are cut from another branch than the one surveyed
- states a policy on AI-generated contributions CONTRIBUTING.md:25
| 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 | adequate | |
| 06 | Observability & Operations | not assessable | |
| 07 | Fit with the Acquirer | not assessable |
- 11% 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
- the declared share is neither decisive nor negligible, so the true figure is more sensitive to undeclared work
- deep scan blamed 573 of 573 counted files
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑src/borg/archive.py is 3,184 lines, 22× this codebase's median file
adequateThe median source file here is 143 lines. 5 files exceed 1,430 lines, the largest being 3,184. 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 | src/borg/archive.py:1 — 3,184 lines (22× median) |
| line-count | src/borg/repository.py:1 — 2,681 lines (18× median) |
| line-count | src/borg/helpers/parseformat.py:1 — 1,712 lines (11× median) |
| line-count | src/borg/legacy/repository.py:1 — 1,681 lines (11× median) |
| line-count | src/borg/crypto/key.py:1 — 1,545 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 · 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 three-quarters or more of 1,784 non-merge commits among 52 authors; across all history, more than half of 7,896. In a project with 52 recent contributors and 17 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 three-quarters or more of 1,784 commits; bus factor 1; 52 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 ↑Releases are cut from another branch than the one surveyed
adequateThe newest release, 1.4.5, is not on the branch this survey read; the newest release on it is 1.2.0. The shipped product may differ from what this report describes. Survey the release branch too.
A note that does not affect this rating: notes like it are common in well-run projects.
| 1b7d3271d | tag 1.4.5 |
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 ↑Manifest says BSD-3-Clause, licence file says BSD-2-Clause
adequatepyproject.toml declares BSD-3-Clause. LICENSE contains the text of BSD-2-Clause. Package managers and downstream users read the first; auditors and acquirers read the second. One of them is wrong, and until it is settled the terms this code is offered under are genuinely ambiguous.
| pyproject.toml | pyproject.toml:30 — declares BSD-3-Clause |
| LICENSE | LICENSE — text of BSD-2-Clause |
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 advisory against this project in the last 24 months
adequateThe newest was published on 2026-08-26. 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 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 1.2.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 4 records name borg with nothing tying them to this repository (CVE-2023-26265, CVE-2026-6885, CVE-2026-6886, …).
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-gfp8-w835-v44j | 2026-08-26: GHSA-gfp8-w835-v44j (low), fixed in 1.4.5: borg extract might modify or disclose out-of-tree files when extracting maliciously crafted archives |
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 5 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 more than half 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- measured 1,351 commits landed in the last year, against 431 the year before (+213%). 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- 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 5 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 Python codebase. Does your engineering organisation already run Python in production, or would this be the first?
- The bulk of this system sits in src/, requirements.d/. Which of your existing systems would each of those have to absorb or replace?
- 34% of lines added in the last 12 months (9% of added lines) came through AI-declared commits. Does your organisation have a policy on inheriting and maintaining that code, and does your engineering team's tooling match how it was produced?
- 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/borgbackup/borg/a586f69)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 — 101 signals that ran and did not fire
Appendix: rejection log — 101 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 — 65
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 1,531 · top5 share 0.105 |
| 04.debt_markers | debt markers are sparsemarkers 30 · per kloc 0.28 · lines read 108,917 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.514 · early test per code 0.125 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.739 · early delete per insert 0.327 |
| 04.fixes_with_tests | fixes usually come with a testfixes 421 · share 0.442 · with tests 186 |
| 04.fix_share_trend | fixing is not crowding out building |
| 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 406 |
| 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.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 374 · active 12mo 29 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 374 · directories 3 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 374 · one off share 0.556 |
| 03.contributor_attrition | the dominant contributor is still activeauthors 374 · top share more than half · top contributor last committed within the last three months |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 52 |
| 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 3 · joined 9 · regular last year 11 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 935 · window last 24 months · with tracked 23 |
| 02.ci_presence | CI configuration is present in the working treecount 11 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 121 · source 278 · test ratio 0.435 |
| 02.release_cadence | tags are presenttags 156 |
| 02.conventional_commits | commit subjects generally carry contentsampled 7,951 · low content share 0.014 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 11 · with tests 6 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 124 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 11 |
| 02.revert_share | change is rarely undoneshare 0.001 · reverts 2 · recent commits 1,784 |
| 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 4 · ci configs 11 · product files 157 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.023 · merges 933 · long lived 21 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.004 · commits 1,612 · over 2000 lines 7 |
| 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 233 · share of insertions 0.0004 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 18.47 · repeat share 0.063 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 185 · write once share 0.086 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0054 · product files 157 · distinct blocks 36,515 |
| 01.swallowed_errors | errors are rarely thrown awayloc 109,282 · files 16 · per kloc 0.32 |
| 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 406 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 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 479,035 |
| 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 70 · pipe to shell 0 · unpinned third party 0 |
| 05.shell_from_strings | product code does not build shell commands from stringssites 0 |
| 05.unsafe_deserialization | no code-executing deserialiser in product codesites 0 |
| 05.tls_verification_off | no TLS verification is switched off in product codefiles 0 · sites 0 · pinned instead 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 0 |
| 05.credentials_in_deploy_config | deployment configuration references secrets, never holds themfiles 0 · sites 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.license_grant_unclear | the licence is recognisable as BSD-2-Clauseclass permissive · license BSD-2-Clause |
| 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 32 · added in two years 12 · removed within 60 days 2 |
| 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 28.0 · days since last tag 1 · commits last 90 days 1,160 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 36
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.eol_runtime | no pinned runtime version to check |
| 04.schema_churn | no schema migrations to read |
| 04.compat_layers | a library, whose compatibility code is usually deliberate |
| 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.dependency_update_cadence | no lockfile to date |
| 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.resource_limits | no Kubernetes workload manifests |
| 05.known_vulnerabilities | no lockfile this survey can read, or a collector older than 0.4.0 |
| 05.public_env_secret | not a frontend |
| 05.unsafe_html | not a frontend |
| 05.source_maps_shipped | not a frontend |
| 05.cleartext_traffic | not a mobile app |
| 05.dataset_provenance | not a data or machine-learning repository |
| 05.license_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 |
| 04.deprecations_lingering | a library, which keeps deprecated interfaces for its users |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; NVD: 4 records name borg with nothing tying them to this repository (CVE-2023-26265, CVE-2026-6885, CVE-2026-6886, …); 1 is fixed in the surveyed commit, and the release users run is not placed by this history |
| 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 8NYT-1Z2X-X3P3 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/8NYT1Z2XX3P3?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-04 · shown | borehole 0.7.13 | 5 | adequate |
5 earlier (show)
| 2026-10-03 | borehole 0.7.12 | 5 | adequate |
| 2026-10-03 | borehole 0.7.11 | 5 | adequate |
| 2026-10-02 | borehole 0.7.10 | 5 | adequate |
| 2026-10-01 | borehole 0.7.9 | 5 | adequate |
| 2026-09-30 | borehole 0.7.8 | 5 | adequate |
Where this scan ran
This scan ran on ordinary cloud infrastructure (cloud-run), not in a hardware-isolated confidential VM. Nothing about it is attested by Google.
What an attested survey proves, and what it does not.
What this scan did with the repository — 3 steps
Written by the steps themselves as they ran, not described afterwards. A hand-written account of a data flow drifts the first time somebody changes the flow and not the account.
| At | Step | Detail |
|---|---|---|
| 0.0s | re-read from the facts kept at the last survey; nothing was cloned | facts version: 1d7c04ef8dca7905 |
| 4.5s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 4.5s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
Total 4.5s ·source content sent off this machine: none · calls to a language model: 0 · the clone was deleted when the survey ended
An automated reading of a repository's code and its history up to one commit, with public advisory records. It may be wrong, it is not legal, financial, investment or security advice, and it does not replace diligence by a qualified person. It is provided for information: nobody may rely on it (Borehole's terms, section 3).