d8f9c6d · 9,882 commits · 3,952 files
Issued 2026-09-27
Nothing significant. Questions worth asking about Security & Reliability Posture, Product & Engineering Maturity.
102 checks ran across 6 assessable dimensions. 2 findings are worth checking first. 10 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 04.62 Releases are cut from another branch than the one surveyed
- 1 submodule(s) this survey does not read: develop/docker-compose/grafana/provisioning/temporalio-dashboards .gitmodules:1
Borehole's proprietary scoring is calibrated across hundreds of repositories. Each finding here reads significant, but its check has not yet held up often enough in that calibration to rate significant on its own. If one holds when someone checks it, it is significant.
- 2 findings rated significant by a check that has not yet held up in Borehole's calibration are now worth checking first.
- 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 | adequate | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | strong | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 7% 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 · adequate · ratings ↑service/history/workflow/mutable_state_impl.go is 10,104 lines, 71× this codebase's median file
adequateThe median source file here is 141 lines. 30 files exceed 1,410 lines, the largest being 10,104. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
| line-count | service/history/workflow/mutable_state_impl.go:1 — 10,104 lines (71× median) |
| line-count | service/frontend/workflow_handler.go:1 — 7,876 lines (55× median) |
| line-count | chasm/tree.go:1 — 4,060 lines (28× median) |
| line-count | service/matching/matching_engine.go:1 — 4,001 lines (28× median) |
| line-count | service/history/interfaces/mutable_state_mock.go:1 — 3,922 lines (27× 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 ↑81 direct dependencies in a single manifest
adequatego.mod declares 81 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
| direct-dependencies | go.mod — 81 declared |
| direct-dependencies | tests/mixedbrain/go.mod — 7 declared |
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.
40 files still carry code deprecated more than two years ago
adequate40 files were marked deprecated over two years ago and still are, the oldest since Feb 2022. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
| api/persistence/v1/executions.pb.go | api/persistence/v1/executions.pb.go — deprecated since Feb 2022 |
| api/adminservice/v1/request_response.pb.go | api/adminservice/v1/request_response.pb.go — deprecated since Mar 2022 |
| api/history/v1/message.pb.go | api/history/v1/message.pb.go — deprecated since Jul 2022 |
| api/historyservice/v1/request_response.pb.go | api/historyservice/v1/request_response.pb.go — deprecated since Jul 2022 |
| api/persistence/v1/history_tree.pb.go | api/persistence/v1/history_tree.pb.go — deprecated since Sep 2022 |
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, v1.32.0-162.5, is not on the branch this survey read; the newest release on it is v1.29.0-135.0. The shipped product may differ from what this report describes. Survey the release branch too.
| bc14ca36c | tag v1.32.0-162.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 ↑The build runs third-party code it does not pin
adequate8 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.
| .github/workflows/claude-review-teams.yml | .github/workflows/claude-review-teams.yml:235 — action pinned by tag |
| .github/workflows/features-integration.yml | .github/workflows/features-integration.yml:72 — 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.
12 SQL statements built from strings
adequate worth checking first12 places in product code build SQL by formatting or joining strings rather than passing parameters. Where any part of the string comes from a request, it is an injection point. Each site needs a look; the fix, parameters, is small.
The check that found this reads significant, but it has not yet held up often enough in Borehole's calibration to rate a finding significant on its own. Opening common/persistence/cassandra/helpers.go:23 and the 1 other file it cites settles it. If it holds when someone checks it, this finding is significant.
| common/persistence/cassandra/helpers.go | common/persistence/cassandra/helpers.go:23 — SQL built from a string |
| common/persistence/cassandra/helpers.go | common/persistence/cassandra/helpers.go:36 — SQL built from a string |
| common/persistence/sql/sqlplugin/mysql/admin.go | common/persistence/sql/sqlplugin/mysql/admin.go:99 — SQL built from a string |
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.
3 locked dependencies have published vulnerabilities
adequate3 of 221 locked dependencies match 3 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.
| go.mod | go.mod — go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.43.0: GHSA-8wmf-6v46-5gfg (low), fixed in 1.45.0 |
| go.mod | go.mod — go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.43.0: GHSA-8wmf-6v46-5gfg (low), fixed in 1.45.0 |
| go.mod | go.mod — go.opentelemetry.io/otel/sdk v1.44.0: GHSA-8wmf-6v46-5gfg (low), fixed in 1.45.0 |
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 workload settings give a container the host
adequate worth checking first6 places in the deployment configuration run a container privileged or in the host's network, process or IPC namespace. A compromise of that container is a compromise of the machine, and most acquirers' security reviews block it. Node agents (network, storage, monitoring) are excluded.
The check that found this reads significant, but it has not yet held up often enough in Borehole's calibration to rate a finding significant on its own. Opening develop/docker-compose/docker-compose.cdc.linux.yml:6 and the 1 other file it cites settles it. If it holds when someone checks it, this finding is significant.
| develop/docker-compose/docker-compose.cdc.linux.yml | develop/docker-compose/docker-compose.cdc.linux.yml:6 — privileged or host namespace |
| develop/docker-compose/docker-compose.cdc.linux.yml | develop/docker-compose/docker-compose.cdc.linux.yml:10 — privileged or host namespace |
| develop/docker-compose/docker-compose.linux.yml | develop/docker-compose/docker-compose.linux.yml:4 — privileged or host namespace |
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 ↑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.
| 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.
4 of 11 deployed images carry no version, or `latest`
adequate4 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
| develop/docker-compose/docker-compose.yml | develop/docker-compose/docker-compose.yml:86 — image without a version |
| develop/docker-compose/docker-compose.yml | develop/docker-compose/docker-compose.yml:62 — image without a version |
| develop/docker-compose/docker-compose.yml | develop/docker-compose/docker-compose.yml:72 — image without a version |
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
6 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 (docs/architecture/README.md and 14 more). Does it match what the team believes today? Ask them to walk through it against the code.
- measured The repository pulls code in through git submodules (.gitmodules). A buyer receives pointers, not that code. Can every submodule be fetched without the team's credentials, and who owns each one?
- 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 301 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 1,988 commits landed in the last year, against 1,299 the year before (+53%). 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- 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 Go codebase. Does your engineering organisation already run Go in production, or would this be the first?
- The bulk of this system sits in service/, common/, api/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (develop/docker-compose/README.md and 18 more). Does that match your deployment and on-call model, or does it need rehosting first?
- What is your tolerance for the findings above remaining unaddressed for the first two quarters after close, given everything else that will compete for this team's time?
- Which of these systems duplicate yours, and which get retired?
- What will integration cost, and in what order?
- Where does the team land in your organisation, and who reports to whom?
- Are there earn-outs, retention packages or contractor IP to assign?
- Do customer contracts limit hosting, regions or vendors?
A human assessment is Borehole's own paid service, €12,000+ (total price is determined per engagement; travel billed at cost). It is not independent of this report: the same business produced both. It is a separate contract, with its own scope, terms and reliance.
Embed the badge
Tied to this commit and this date, and it fades after 90 days — an honest badge is one that expires. A repository with significant findings gets a neutral "read" badge rather than a red one: the library is where the range is visible, not someone else's README.
[](/r/temporalio/temporal/d8f9c6d)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 — 92 signals that ran and did not fire
Appendix: rejection log — 92 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 — 69
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 8,891 · top5 share 0.032 |
| 04.debt_markers | debt markers are sparsemarkers 947 · per kloc 0.87 · lines read 1,082,606 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 1.31 · early test per code 0.398 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.576 · early delete per insert 0.81 |
| 04.fixes_with_tests | fixes usually come with a testfixes 558 · share 0.746 · with tests 416 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 1,855 · compat files 0 |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 135 |
| 06.structured_logging | a structured logging library is referencedmatches 17 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.telemetry_depth | the service is visible in more than one way |
| 06.print_logging | raw prints are few, or outnumbered by logger callsprints 4 · logger calls 1,328 |
| 06.correlation_ids | a request can be followed through the logstracing True · request id sites 170 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 176 · release commits 3 · changelog commits 8 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 9.9 · window last 24 months · authors 301 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 301 · active 12mo 99 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 301 · directories 13 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 301 · one off share 0.439 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 301 · top share less than a quarter · top contributor last committed more than two years ago |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 126 |
| 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 7 · joined 33 · regular last year 53 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 2 · window last 24 months · with tracked 31 |
| 02.ci_presence | CI configuration is present in the working treecount 22 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 1,199 · source 2,857 · test ratio 0.42 |
| 02.release_cadence | tags are presenttags 567 |
| 02.conventional_commits | commit subjects generally carry contentsampled 9,838 · 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 22 · with tests 4 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 1,618 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 22 |
| 02.revert_share | change is rarely undoneshare 0.009 · reverts 29 · recent commits 3,291 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 2 · commits since 30 · days since lockfile changed 8 |
| 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 2 · ci configs 22 · product files 1,855 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.018 · commits 3,056 · over 2000 lines 54 |
| 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 325 · share of insertions 0.0001 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 18.3 · repeat share 0.001 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 1,913 · write once share 0.185 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0148 · product files 1,667 · distinct blocks 271,395 |
| 01.swallowed_errors | errors are rarely thrown awayloc 1,085,954 · files 0 · per kloc 0.0 |
| 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 3,421 |
| 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.outbound_timeouts | outbound calls set timeouts, or are fewcalls without timeout 1 |
| 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 1 |
| 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 MITclass permissive · license MIT |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 322 · added in two years 100 · 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 | the root licence has not changed in the history readlicence versions 1 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 0.5 · days since last tag 6 · commits last 90 days 547 |
| 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 0 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 23
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.dependency_redundancy | no JavaScript manifest to read |
| 06.alert_rules | no alert rules in the repository; they may live in a console |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 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.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.migration_reversibility | too few migrations to judge |
| 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_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 |
| 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 |
Anyone can check this report against the authoritative record — click the stamp, or enter WMHX-DD5H-ARC0 at borehole.dev/verify.
The code commits to the 103 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/WMHXDD5HARC0?via=badge)
A survey is a reading by a particular version of the assessor. Older readings are kept rather than replaced, because a verification mark attests to the survey it was issued for — overwriting one would make every code already in circulation read as tampered.
| Read | Assessor | Findings | Band |
|---|---|---|---|
| 2026-09-27 · shown | borehole 0.7.3 | 11 | adequate |
9 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 12 | strong |
| 2026-10-03 | borehole 0.7.12 | 12 | strong |
| 2026-10-03 | borehole 0.7.11 | 12 | strong |
| 2026-10-02 | borehole 0.7.10 | 12 | strong |
| 2026-10-01 | borehole 0.7.9 | 12 | adequate |
| 2026-09-30 | borehole 0.7.8 | 11 | adequate |
| 2026-09-29 | borehole 0.7.6 | 11 | adequate |
| 2026-09-28 | borehole 0.7.5 | 11 | adequate |
| 2026-09-28 | borehole 0.7.4 | 11 | 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: aa57b0e0fea635c1 |
| 27.3s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 27.3s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
Total 27.3s ·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).