eebd26d · 4,342 commits · 2,726 files
Issued 2026-11-03
Apache-2.0 since 2026-05-28: open source; use, change and redistribution need only attribution.
1 of 6 assessable dimensions carries significant findings, 2 are adequate and 3 are strong. 12 findings, each with its evidence: the commit, path and lines it rests on, or, when something is missing, what was looked for. One dimension cannot be assessed without an acquirer. Last commit 3 November 2026.
- The file and line of 3 credential-shaped matches are withheld. File and line are shown to whoever GitHub says controls this repository, signed in, and to a buyer of this report.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | significant findings | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 1% 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
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑crates/db/src/index_lifecycle/secondary.rs is 8,196 lines, 56× this codebase's median file
adequateThe median source file here is 146 lines. 60 files exceed 1,460 lines, the largest being 8,196. 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 | crates/db/src/index_lifecycle/secondary.rs:1 — 8,196 lines (56× median) |
| line-count | crates/db/src/search/vector/hnsw/mutation/mod.rs:1 — 6,511 lines (44× median) |
| line-count | crates/db/src/execution/interpreter/count.rs:1 — 6,140 lines (42× median) |
| line-count | crates/db/src/lib.rs:1 — 6,118 lines (41× median) |
| line-count | crates/db/src/index_lifecycle/vector/driver.rs:1 — 5,414 lines (37× 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 ↑Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| process-scaffolding | 1 of 5 markers present across 2,726 tracked files |
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 · significant findings · ratings ↑Bus factor 1: recent work is concentrated in one contributor
significant findingsIn the last 24 months, one contributor authored more than half of 3,528 non-merge commits among 43 authors; across all history, more than half of 3,528. This is the single most expensive thing to discover after closing, and the repository cannot tell you whether that person is part of the transaction.
| git shortlog -sn | last 24 months: top author more than half of 3,528 commits; bus factor 1; 43 authors |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Product & Engineering Maturity
04 · strong · ratings ↑No finding. 19 checks ran and none fired; the rejection log below says why each did not.
Security & Reliability Posture
05 · adequate · ratings ↑1 credential-shaped string in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| AWS access key | AWS access key, where fakes are usual |
| File and line are shown to whoever GitHub says controls this repository, signed in, and to a buyer of this report. |
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.
None of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| guardrail-scan | checked 5 kinds of guard rail across 2,726 tracked files; 0 present |
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.
Relicensed: GPL-3.0 → AGPL-3.0 (2025-05-13) → Apache-2.0 (2026-05-28)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
| 923710c52 | LICENSE — GPL-3.0 from 2024-11-23 |
| 8ff161791 | LICENSE — AGPL-3.0 from 2025-05-13 |
| 8ddca5c13 | LICENSE — Apache-2.0 from 2026-05-28 |
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.
2 credential-shaped strings added in the history sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
A note that does not affect this rating: notes like it are common in well-run projects.
| history | 2 cited: AWS access key, where fakes are usual |
| File and line are shown to whoever GitHub says controls this repository, signed in, and to a buyer of this report. |
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
adequate5 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; 6 steps pipe 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.
A note that does not affect this rating: notes like it are common in well-run projects.
| .github/workflows/cargo-target-references.yml | .github/workflows/cargo-target-references.yml:35 — action pinned by tag |
| .github/workflows/cargo-target-references.yml | .github/workflows/cargo-target-references.yml:36 — action pinned by tag |
| crates/cli/install.sh | crates/cli/install.sh:35 — 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.
45 locked dependencies have published vulnerabilities, 10 high or critical
adequate45 of 1,040 locked dependencies match 107 published advisories in OSV, 10 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| crates/cli/Cargo.lock | crates/cli/Cargo.lock — openssl 0.10.75: GHSA-8c75-8mhr-p7r9 (high), fixed in 0.10.78 |
| crates/cli/Cargo.lock | crates/cli/Cargo.lock — quinn-proto 0.11.13: GHSA-4w2j-m93h-cj5j (high), fixed in 0.11.15 |
| sdks/rust/Cargo.lock | sdks/rust/Cargo.lock — quinn-proto 0.11.14: GHSA-4w2j-m93h-cj5j (high), fixed in 0.11.15 |
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 vendored component with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| tools/opencypher-tck/vendor/manifest.json | tools/opencypher-tck/vendor/manifest.json — 1 tracked files, no licence 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.
Observability & Operations
06 · adequate · ratings ↑One request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| request ids | no request id, correlation id or tracing found |
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.
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
A note that does not affect this rating: notes like it are common in well-run projects.
| error reporting | no error reporter initialised |
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.
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
9 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 1,630 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 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- 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.
- measured No threat model is in the tree of what looks like a running service. Does one exist elsewhere, and who owns it?
- What has actually broken, how often, and how badly?
- What did external testing find, and was it fixed?
- What is the SOC 2, ISO 27001 or GDPR status, and where is the evidence?
Observability & Operations
06 · partial coverage- measured Nothing in the tree backs up or restores data. How is data backed up, and has a restore ever been rehearsed?
- measured No alert rule is defined in the repository. Where are alerts defined, who receives them, and when did one last fire?
- 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/, sdks/, docker-image/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (Dockerfile). 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/helixdb/helix-db/eebd26d)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 — 94 signals that ran and did not fire
Appendix: rejection log — 94 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 — 60
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 5,386 · top5 share 0.048 |
| 04.debt_markers | debt markers are sparsemarkers 2 · per kloc 0.0 · lines read 758,350 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.202 · early delete per insert 0.716 |
| 04.fixes_with_tests | fixes usually come with a testfixes 599 · share 0.272 · with tests 163 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.008 · code files 1,491 · compat files 12 |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 5 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.usage_reporting_default | reporting is off until someone turns it onsettings on 0 · settings off 2 |
| 06.release_markers | releases are markedtags last year 53 · release commits 6 · changelog commits 2 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.active_contributors | more than one contributor active in the trailing yearall time 43 · active 12mo 29 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 43 · directories 7 |
| 03.drive_by_contributors | a healthy share of contributors committed more than onceshare 0.209 · authors 43 · one commit authors 9 |
| 03.contributor_attrition | the dominant contributor is still activeauthors 43 · 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 43 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.joiners_and_leavers | the team is not shrinkingleft 9 · joined 14 · regular last year 18 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 802 · window last 24 months · with tracked 95 |
| 02.ci_presence | CI configuration is present in the working treecount 15 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 1,179 · source 2,044 · test ratio 0.577 |
| 02.release_cadence | tags are presenttags 198 |
| 02.conventional_commits | commit subjects generally carry contentsampled 3,540 · low content share 0.056 |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 15 · with tests 9 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 1 · test files 572 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 15 |
| 02.revert_share | change is rarely undoneshare 0.001 · reverts 5 · recent commits 3,528 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 10 · commits since 68 · days since lockfile changed 9 |
| 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 6 · ci configs 15 · product files 1,491 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.179 · merges 374 · long lived 67 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.038 · commits 3,361 · over 2000 lines 129 |
| 01.burst_import | the largest burst was a branch merged by a merge commit, developed on its own branch and landed in one piece (100% of it), 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, a branch merged by a merge commit was reviewed as one piece, and an export or mirror tool dates history when it replays itlargest commits 0bc55b1..5426a15 · bursts explained 2 · largest net added 12,588 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 676 · share of insertions 0.0005 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 28.2 · repeat share 0.138 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 1,599 · write once share 0.464 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.005 · product files 1,491 · distinct blocks 349,139 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 2 |
| 01.unfinished_migration | no language migration is stalled halfway |
| 01.weights_in_git | no model weights are committedfiles 0 |
| 05.dependency_pinning | a lockfile is committed, so builds are reproduciblelockfile True |
| 05.license_present | a licence file is presentfound True |
| 05.container_runs_as_root | every shipped Dockerfile drops to a non-root user or builds on a non-root base imagedockerfiles 1 |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 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 245 |
| 05.license_grant_unclear | the licence is recognisable as Apache-2.0class permissive · license Apache-2.0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 0 · files with deprecations 16 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 209 · added in two years 209 · removed within 60 days 26 |
| 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.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 2.0 · days since last tag 25 · commits last 90 days 1,591 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 2 · on branch 190 · tags in window 192 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 34
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.test_growth | Rust keeps unit tests inside the files they test, which a count by file name cannot see |
| 04.eol_runtime | no pinned runtime version to check |
| 04.schema_churn | no schema migrations to read |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.structured_logging | not assessed for Rust: its logging setup is not read |
| 06.telemetry_depth | none at all is 06.1 |
| 06.print_logging | not assessed for Rust: its logger calls are not read |
| 06.alert_rules | no alert rules in the repository; they may live in a console |
| 06.deployed_image_floats | no deployment descriptor names an image |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.environment_branching | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.bus_factor_trend | fewer than three active years to compare |
| 01.swallowed_errors | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.outbound_timeouts | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 05.migration_reversibility | too few migrations to judge |
| 05.sql_from_strings | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 05.shell_from_strings | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 05.unsafe_deserialization | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 05.tls_verification_off | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.public_env_secret | not a frontend |
| 05.unsafe_html | not a frontend |
| 05.source_maps_shipped | not a frontend |
| 05.cleartext_traffic | not a mobile app |
| 05.dataset_provenance | not a data or machine-learning repository |
| 05.license_manifest_conflict | no packaging manifest states a licence |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | one API version is served, or none |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; OSV PyPI helix-db-embedded (an empty record for a package published here), OSV crates.io helix-ast (an empty record for a package published here), OSV crates.io helix-graph-algorithms (an empty record for a package published here), OSV crates.io helix-metrics (an empty record for a package published here), OSV PyPI helix-db (an empty record for a package published here), OSV crates.io helix-db (an empty record for a package published here), OSV npm @helix-db/helix-db (an empty record for a package published here), OSV crates.io helix-dsl-macros (an empty record for a package published here) did not |
| 05.advisory_record | record incomplete: no advisory against the project in the last 24 months; OSV PyPI helix-db-embedded (an empty record for a package published here), OSV crates.io helix-ast (an empty record for a package published here), OSV crates.io helix-graph-algorithms (an empty record for a package published here), OSV crates.io helix-metrics (an empty record for a package published here), OSV PyPI helix-db (an empty record for a package published here), OSV crates.io helix-db (an empty record for a package published here), OSV npm @helix-db/helix-db (an empty record for a package published here), OSV crates.io helix-dsl-macros (an empty record for a package published here) did not answer |
| 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 WR0P-ZA6N-Q8VK 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/WR0PZA6NQ8VK?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: 53.8authenticated: False |
| 6.8s | cloned the repository to a temporary directory | depth: full |
| 11.8s | read the git history | commits: 4342tracked files: 2726 |
| 129.6s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 129.7s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 182.2s | kept the facts, never the source, for re-reading under new checks | |
| 182.2s | deleting the working copy |
Total 182.2s ·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).