9e0f57a · 5,018 commits · 1,517 files
Issued 2026-10-03
Reads strong: 4 of 5 rated dimensions are strong, 1 is adequate and none is significant.
104 checks ran across 6 assessable dimensions. Product & Engineering Maturity is adequate. 4 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 .github/CONTRIBUTING.md:80
- names OpenSSF README.md:3
- 2 findings from checks Borehole's calibration found wrong more often than right are no longer published.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | strong | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | strong | |
| 06 | Observability & Operations | not assessable | |
| 07 | Fit with the Acquirer | not assessable |
- 5% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- 35% of commits show author/committer date divergence, which is the shape of replayed history that can drop trailers
- deep scan blamed 1,448 of 1,448 counted files
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑src/gui/styles/base/BaseStyle.cpp is 4,861 lines, 59× this codebase's median file
adequateThe median source file here is 82 lines. 11 files exceed 1,000 lines, the largest being 4,861. 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/gui/styles/base/BaseStyle.cpp:1 — 4,861 lines (59× median) |
| line-count | src/gui/DatabaseWidget.cpp:1 — 2,847 lines (34× median) |
| line-count | src/gui/MainWindow.cpp:1 — 2,261 lines (27× median) |
| line-count | src/gui/entry/EditEntryWidget.cpp:1 — 1,817 lines (22× median) |
| line-count | src/browser/BrowserService.cpp:1 — 1,788 lines (21× 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 · strong · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · adequate · ratings ↑Fixes are 54% of recent work, up from 33%
adequateIn the last two quarters 54% of commits were fixes, against 33% in the quarters before. Rising fix work usually means quality debt is coming due, and it takes time that new work would have had.
| fix share by quarter | 35%, 73%, 37%, 30%, 41%, 29%, 22%, 39% |
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.
Releases are cut from another branch than the one surveyed
adequateThe newest release, 2.7.12, is not on the branch this survey read; the newest release on it is 2.7.1. 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.
| 860e51d8e | tag 2.7.12 |
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 · strong · ratings ↑7 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-09-23. 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 7 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 2.7.1. Answer lives in: the release you run, set against each fixed version.
A note that does not affect this rating: it describes the project's advisory record, and no advisory in it is known to affect the surveyed commit.
| GHSA-rq29-wgrv-xgh4 | 2026-09-23: GHSA-rq29-wgrv-xgh4 (low), fixed in 2.8.0: Heap ouf-of-bounds via integer overflow in legacy .kdb import |
| GHSA-mffq-j98j-wfr2 | 2026-09-23: GHSA-mffq-j98j-wfr2 (low), fixed in 2.8.0: Pageant SSH agent key sharing uses predictable shared memory name |
| GHSA-3448-gh8j-3227 | 2026-09-23: GHSA-3448-gh8j-3227 (moderate), fixed in 2.8.0: Out-of-bounds write in browser integration response encryption with oversized database responses |
| GHSA-2vm2-vmc3-vccr | 2026-09-23: GHSA-2vm2-vmc3-vccr (moderate), fixed in 2.8.0: Browser extension allows creating references to other entries enabling limited data exfiltration |
| GHSA-4642-49vv-4p43 | 2026-09-23: GHSA-4642-49vv-4p43 (moderate), fixed in 2.8.0: Heap use-after-free in KeePass1 (KDB) importer via unpruned m_entryUuids map |
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.
What a person adds
The survey reads what the repository can show. The code cannot settle these questions, and on them this report states nothing. Each says where its answer lives: your own engineer, the company, or an assessor you choose can settle it. Questions marked measured open with something this repository shows.
Architecture & Codebase — including AI provenance
01 · full coverage- measured No architecture or design document is in the tree, across 1,173 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 498 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- 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 C codebase, with C++ alongside (45% of source files). Does your engineering organisation already run C in production, or would this be the first?
- The bulk of this system sits in share/, src/, cmake/. 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.
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.
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/keepassxreboot/keepassxc/9e0f57a)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 — 100 signals that ran and did not fire
Appendix: rejection log — 100 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 — 61
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 2,955 · top5 share 0.078 |
| 04.debt_markers | debt markers are sparsemarkers 58 · per kloc 0.37 · lines read 157,863 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.237 · early test per code 0.119 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.542 · early delete per insert 0.506 |
| 04.fixes_with_tests | fixes usually come with a testfixes 112 · share 0.214 · with tests 24 |
| 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 905 |
| 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.contributor_concentration | no single contributor dominates the last 24 monthsyears 16.1 · window last 24 months · authors 498 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 498 · active 12mo 51 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 498 · directories 5 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 498 · one off share 0.689 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 498 · top share less than a quarter · top contributor last committed more than three years ago |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 87 |
| 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 1 · joined 4 · regular last year 8 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 23 |
| 02.ci_presence | CI configuration is present in the working treecount 2 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 138 · source 828 · test ratio 0.167 |
| 02.release_cadence | tags are presenttags 64 |
| 02.conventional_commits | commit subjects generally carry contentsampled 4,516 · low content share 0.006 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 214 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 2 |
| 02.revert_share | change is rarely undoneshare 0.0 · reverts 0 · recent commits 310 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 1 · commits since 35 · days since lockfile changed 44 |
| 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 1 · ci configs 2 · product files 755 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.01 · commits 288 · over 2000 lines 3 |
| 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 2,446 · share of insertions 0.0014 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 20.76 · repeat share 0.051 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 1,080 · write once share 0.289 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0019 · product files 690 · distinct blocks 69,127 |
| 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 905 |
| 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.supply_chain_pinning | third-party build steps are pinned, or fewaction refs 5 · pipe to shell 0 · unpinned third party 0 |
| 05.known_vulnerabilities | no locked dependency has a published advisory; not assessed for C and C++ package managersadvisories 0 · dependencies 3 · high or critical 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 0 |
| 05.credentials_in_deploy_config | deployment configuration references secrets, never holds themfiles 0 · sites 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_copyleft_inherited | every licence found in vendored code is permissive or weak-copyleftvendored paths 20 |
| 05.license_vendored_unlicensed | all 3 vendored components state their terms, in a licence file, their own headers or a notices filecomponents 3 · stated in headers or notices 3 |
| 05.license_grant_unclear | the licence is recognisable as MITclass permissive · license MIT |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 2 · added in two years 2 · 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 | relicensed only between permissive licences: BSD-3-Clause → MIT (2017-06-14)latest MIT · weaker False · licence versions 2 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 99.5 · days since last tag 10 · commits last 90 days 46 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 39
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.structured_logging | not assessed for C or C++, the languages 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 |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.swallowed_errors | not assessed for C or C++, the languages 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 C or C++, the languages the product is written in: this check's patterns read other languages only |
| 05.unsafe_deserialization | not assessed for C or C++, the languages the product is written in: this check's patterns read other languages only |
| 05.tls_verification_off | not assessed for C or C++, the languages the product is written in: this check's patterns read other languages only |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.public_env_secret | not a frontend |
| 05.unsafe_html | not a frontend |
| 05.source_maps_shipped | not a frontend |
| 05.cleartext_traffic | not a mobile app |
| 05.dataset_provenance | not a data or machine-learning repository |
| 05.license_manifest_conflict | no packaging manifest states a licence |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | not a running service |
| 04.deprecations_lingering | a library, which keeps deprecated interfaces for its users |
| 05.project_advisories | could not tell whether 10 published advisories affect the surveyed code: its version is only known to be at least 2.7.1 |
Anyone can check this report against the authoritative record — click the stamp, or enter VTVR-9NE6-RVC1 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/VTVR9NE6RVC1?via=badge)
A survey is a reading by a particular version of the assessor. Older readings are kept rather than replaced, because a verification mark attests to the survey it was issued for — overwriting one would make every code already in circulation read as tampered.
| Read | Assessor | Findings | Band |
|---|---|---|---|
| 2026-10-03 · shown | borehole 0.7.12 | 6 | strong |
15 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 6 | strong |
| 2026-10-03 | borehole 0.7.11 | 6 | strong |
| 2026-10-02 | borehole 0.7.10 | 6 | strong |
| 2026-10-01 | borehole 0.7.9 | 6 | strong |
| 2026-09-30 | borehole 0.7.8 | 6 | adequate |
| 2026-09-29 | borehole 0.7.6 | 5 | adequate |
| 2026-09-28 | borehole 0.7.5 | 5 | adequate |
| 2026-09-28 | borehole 0.7.4 | 5 | adequate |
| 2026-09-27 | borehole 0.7.3 | 4 | strong |
| 2026-09-27 | borehole 0.7.2 | 4 | strong |
| 2026-09-27 | borehole 0.7.1 | 4 | strong |
| 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 |
| 2026-09-25 | borehole 0.6.1 | 7 | strong |
Where this scan ran
This scan ran on ordinary cloud infrastructure (cloud-run), not in a hardware-isolated confidential VM. Nothing about it is attested by Google.
What an attested survey proves, and what it does not.
What this scan did with the repository — 7 steps
Written by the steps themselves as they ran, not described afterwards. A hand-written account of a data flow drifts the first time somebody changes the flow and not the account.
| At | Step | Detail |
|---|---|---|
| 0.0s | read repository metadata from the GitHub API | authenticated: False |
| 10.3s | cloned the repository to a temporary directory | depth: full |
| 18.0s | read the git history | commits: 5018tracked files: 1517 |
| 167.6s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 167.6s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 198.7s | kept the facts, never the source, for re-reading under new checks | |
| 198.7s | deleting the working copy |
Total 198.7s ·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).