7d311e6 · 2,205 commits · 1,223 files
Issued 2026-10-23
Reads strong: 4 of 5 rated dimensions are strong, 1 is adequate and none is significant.
105 checks ran across 6 assessable dimensions. Organization & Key-Person Risk is adequate. 7 findings, each with evidence. One dimension cannot be assessed without an acquirer.
This repository reads strong. Show it in your README: the badge links to a page where anyone can check the reading. 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/QTSM4ZZMJVDD?via=badge)- 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 | strong | |
| 06 | Observability & Operations | not assessable | |
| 07 | Fit with the Acquirer | not assessable |
- 24% 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 1,189 of 1,191 counted files
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑rust/core/src/engine/component.rs is 3,071 lines, 16× this codebase's median file
adequateThe median source file here is 182 lines. 8 files exceed 1,820 lines, the largest being 3,071. 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 | rust/core/src/engine/component.rs:1 — 3,071 lines (16× median) |
| line-count | rust/sdk/cocoindex/src/cypher_graph.rs:1 — 2,585 lines (14× median) |
| line-count | rust/sdk/cocoindex/src/connectors/lancedb.rs:1 — 2,480 lines (13× median) |
| line-count | python/cocoindex/_internal/function.py:1 — 2,308 lines (12× median) |
| line-count | rust/core/src/engine/execution.rs:1 — 2,204 lines (12× 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 ↑The next contributor after the top one has not committed here for more than a year
adequateThe #2 contributor of the last three years (a quarter or more of the commits) has not committed here for more than a year, while the repository is still active. These are the people a buyer assumes would step up if the top contributor stopped. The history shows only that no commits of theirs landed here, not why.
| git shortlog -sn | the #2 contributor of the last three years (a quarter or more of the commits) has not committed here for more than a year |
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 · strong · ratings ↑1 environment file is committed
adequate.env.lib_debug is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| .env.lib_debug | .env.lib_debug — committed environment file |
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
adequate9 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. 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.
A note that does not affect this rating: notes like it are common in well-run projects.
| .github/workflows/CI.yml | .github/workflows/CI.yml:60 — action pinned by tag |
| .github/workflows/_docs_release.yml | .github/workflows/_docs_release.yml:23 — action pinned by tag |
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.
6 deserialisers that can run code
adequate6 places read data with a deserialiser that executes what it reads (pickle). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| python/cocoindex/_internal/function.py | python/cocoindex/_internal/function.py:1206 — code-executing deserialiser |
| python/cocoindex/_internal/runner.py | python/cocoindex/_internal/runner.py:176 — code-executing deserialiser |
| python/cocoindex/_internal/runner.py | python/cocoindex/_internal/runner.py:202 — code-executing deserialiser |
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.
22 locked dependencies have published vulnerabilities
adequate22 of 1,348 locked dependencies match 29 published advisories in OSV. 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.
| uv.lock | uv.lock — accelerate 1.14.0: GHSA-4j2p-28q2-5m79 (moderate); an optional extra |
| uv.lock | uv.lock — setuptools 81.0.0: GHSA-h35f-9h28-mq5c (moderate), fixed in 83.0.0; an optional extra |
| Cargo.lock | Cargo.lock — rsa 0.9.10: RUSTSEC-2023-0071 (moderate) |
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, 1 high or critical
adequateThe newest was published on 2026-02-28. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed 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-59g6-v3vg-f7wc | 2026-02-28: GHSA-59g6-v3vg-f7wc (high), fixed in 0.3.34: CocoIndex Doris target connector didn't verify table name when constructing ALTER TABLE statements |
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
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 The tree carries design documentation (examples/conversation_to_knowledge/design.md). Does it match what the team believes today? Ask them to walk through it against the code.
- 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 100 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- measured No experiment tracking is configured in the repository. How was the shipped model trained and evaluated, and could it be reproduced?
- measured No model card is in the tree. What is the model's intended use, what was it trained on, and where does it fail?
- 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 05.5 found credential-shaped strings in this repository. Was each one revoked at the provider? Deleting it from the code revokes nothing; only the provider's audit log shows that it was.
- 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 Rust codebase, with Python alongside (34% of source files). Does your engineering organisation already run Rust in production, or would this be the first?
- The bulk of this system sits in rust/, python/, skills/. Which of your existing systems would each of those have to absorb or replace?
- 38% 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/cocoindex-io/cocoindex/7d311e6)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 — 98 signals that ran and did not fire
Appendix: rejection log — 98 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 — 67
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 2,980 · top5 share 0.035 |
| 04.debt_markers | debt markers are sparsemarkers 9 · per kloc 0.04 · lines read 246,409 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.223 · early delete per insert 0.437 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fixes_with_tests | fixes usually come with a testfixes 417 · share 0.247 · with tests 103 |
| 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 1,009 |
| 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.contributor_concentration | no single contributor dominates the last 24 monthsyears 1.6 · window last 24 months · authors 100 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 100 · active 12mo 74 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 100 · directories 6 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 100 · one off share 0.56 |
| 03.contributor_attrition | the dominant contributor is still activeauthors 100 · 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 100 |
| 03.joiners_and_leavers | the team is not shrinkingleft 8 · joined 16 · regular last year 20 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 90 · window last 24 months · with tracked 28 |
| 02.ci_presence | CI configuration is present in the working treecount 10 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 288 · source 498 · test ratio 0.578 |
| 02.release_cadence | tags are presenttags 223 |
| 02.conventional_commits | commit subjects generally carry contentsampled 2,115 · low content share 0.001 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 10 · with tests 1 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 196 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 10 |
| 02.revert_share | change is rarely undoneshare 0.0 · reverts 0 · recent commits 2,017 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 32 · commits since 7 · days since lockfile changed 0 |
| 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 10 · product files 303 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.0 · merges 62 · long lived 0 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.029 · commits 1,813 · over 2000 lines 52 |
| 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 201 · share of insertions 0.0002 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 16.86 · repeat share 0.001 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 346 · write once share 0.228 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0209 · product files 303 · distinct blocks 79,244 |
| 01.swallowed_errors | errors are rarely thrown awayloc 247,382 · files 13 · per kloc 0.09 |
| 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 1,009 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.dependency_pinning | a lockfile is committed, so builds are reproduciblelockfile True |
| 05.license_present | a licence file is presentfound True |
| 05.shell_from_strings | product code does not build shell commands from stringssites 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.dataset_provenance | data files carry a licence or carddata files 0 · licence or card files 1 |
| 05.license_manifest_conflict | manifest and licence file agree on Apache-2.0license 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.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 299 · added in two years 299 · removed within 60 days 15 |
| 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 8.0 · days since last tag 1 · commits last 90 days 199 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 3 · on branch 220 · tags in window 223 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
| 05.project_advisories | no published advisory affects the surveyed versionaffecting 0 · exploited 0 · advisories 1 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 31
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.test_growth | tests are kept inside the files they test, which a count by file name cannot see |
| 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 |
| 03.bus_factor_trend | fewer than three active years to compare |
| 01.build_reproducibility | no product Dockerfile to read |
| 01.notebook_outputs | too few notebooks |
| 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.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.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 |
Anyone can check this report against the authoritative record — click the stamp, or enter QTSM-4ZZM-JVDD 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/QTSM4ZZMJVDD?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: 115.5authenticated: False |
| 7.3s | cloned the repository to a temporary directory | depth: full |
| 10.6s | read the git history | commits: 2205tracked files: 1223 |
| 85.2s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 85.2s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 115.9s | kept the facts, never the source, for re-reading under new checks | |
| 115.9s | deleting the working copy |
Total 115.9s ·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).