f7e76c1 · 5,062 commits · 1,240 files
Issued 2026-11-07
Reads strong. Apache-2.0 since 2024-07-07: open source; use, change and redistribution need only attribution.
101 checks ran across 6 assessable dimensions. 3 of 5 rated dimensions are strong, 2 are adequate and none is significant. Security & Reliability Posture and Architecture & Codebase — including AI provenance are adequate. 1 finding is worth checking first. 10 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/8J8S4BTJYDWK?via=badge)- 05.60 Apache-2.0 since 2024-07-07: open source; use, change and redistribution need only attribution
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.
- 05.26 3 locked dependencies have published vulnerabilities, 5 high or critical in what ships
- 4 findings from checks Borehole's calibration found wrong more often than right are no longer published.
- 1 finding about one contributor is withheld: one author wrote nearly all of this repository's commits; a buyer of this report reads them.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | adequate | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | not assessable | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | strong | |
| 07 | Fit with the Acquirer | not assessable |
- 27% 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,196 of 1,196 counted files
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑1 base image floats: no version, or `latest`
adequate1 of 2 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
| Dockerfile | Dockerfile:1 — base 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.
cmd/protoc-gen-micro/generator/generator.go is 2,758 lines, 26× this codebase's median file
adequateThe median source file here is 106 lines. 6 files exceed 1,060 lines, the largest being 2,758. 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 | cmd/protoc-gen-micro/generator/generator.go:1 — 2,758 lines (26× median) |
| line-count | cmd/micro/gateway/server.go:1 — 1,924 lines (18× median) |
| line-count | gateway/a2a/a2a.go:1 — 1,245 lines (11× median) |
| line-count | server/grpc/grpc.go:1 — 1,201 lines (11× median) |
| line-count | model/atlascloud/atlascloud.go:1 — 1,198 lines (11× 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 · not assessable · ratings ↑Not rated: one author wrote nearly all of this repository's commits, so a finding about one contributor would be about someone its history all but names; the public report does not carry those, and does not rate this dimension without them. What a person adds here.
Product & Engineering Maturity
04 · strong · ratings ↑Effort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.52 to 0.79 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| deletions-per-insertion | first half 0.52, second half 0.79 (split 2020-12-03) |
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 ↑2 Dockerfiles run the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
| no-USER-instruction | Dockerfile — runs as root |
| no-USER-instruction | internal/website/Dockerfile — runs as root |
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, 5 high or critical in what ships
adequate worth checking first3 of 126 locked dependencies match 17 published advisories in OSV, 6 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.
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 go.mod settles it. If it holds when someone checks it, this finding is significant.
| go.mod | go.mod — github.com/nats-io/nats-server/v2 v2.11.3: GHSA-52jh-2xxh-pwh6 (high), fixed in 2.11.14 |
| go.mod | go.mod — go.opentelemetry.io/otel/sdk v1.44.0: GHSA-8wmf-6v46-5gfg (low), fixed in 1.45.0 |
| go.mod | go.mod — golang.org/x/net v0.60.0: GO-2026-6860 (unrated), fixed in 0.62.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.
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; 2 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/lint.yaml | .github/workflows/lint.yaml:28 — action pinned by tag |
| .github/workflows/release.yml | .github/workflows/release.yml:29 — action pinned by tag |
| internal/website/static/install.sh | internal/website/static/install.sh:3 — 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.
2 outbound calls can wait forever
adequate2 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| cmd/micro/mcp/mcp.go | cmd/micro/mcp/mcp.go:671 — outbound call without a timeout |
| cmd/micro/run/run.go | cmd/micro/run/run.go:209 — outbound call without a timeout |
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.
8 SQL statements built from strings
adequate8 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| store/mysql/mysql.go | store/mysql/mysql.go:50 — SQL built from a string |
| store/mysql/mysql.go | store/mysql/mysql.go:144 — SQL built from a string |
| store/mysql/mysql.go | store/mysql/mysql.go:149 — 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.
Relicensed: Apache-2.0 → BUSL-1.1 (2024-06-04) → Apache-2.0 (2024-07-07)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
A note that does not affect this rating: a licence change is a fact for the first screen, and only a narrowing of rights within two years of the surveyed commit costs "strong".
| de8ab2114 | LICENSE — Apache-2.0 from 2015-02-27 |
| e11395c8f | LICENSE — BUSL-1.1 from 2024-06-04 |
| 6c0a073e3 | LICENSE — Apache-2.0 from 2024-07-07 |
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 · strong · 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.
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
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 (internal/website/DESIGN.md and 1 more). 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 coverageNot rated: one author wrote nearly all of this repository's commits, so a finding about one contributor would be about someone its history all but names; the public report does not carry those, and does not rate this dimension without them.
- Which of the people who wrote this are part of the transaction, and for how long after it?
- Where was the work of that period done, and is it in this history? The history shows the gap, not why it happened.
- 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,151 commits landed in the last year, against 96 the year before (+1099%). What drove it: new people, a deadline, or code produced faster than before?
- measured A roadmap file is in the tree (ROADMAP.md, last changed September 2026). A file is not a plan. Does it match the roadmap in the data room, and has the team delivered the last one it wrote?
- 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 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 internal/, cmd/, transport/. Which of your existing systems would each of those have to absorb or replace?
- 73% of lines added in the last 12 months (28% 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?
- The repository carries deployment configuration (Dockerfile and 11 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/micro/go-micro/f7e76c1)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 — 91 signals that ran and did not fire
Appendix: rejection log — 91 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 — 71
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 4,410 · top5 share 0.056 |
| 04.debt_markers | debt markers are sparsemarkers 85 · per kloc 0.47 · lines read 179,426 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.293 · early test per code 0.161 |
| 04.fixes_with_tests | fixes usually come with a testfixes 115 · share 0.452 · with tests 52 |
| 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 491 · 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 28 |
| 06.structured_logging | a structured logging library is referencedmatches 10 |
| 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 90 · logger calls 43 |
| 06.correlation_ids | a request can be followed through the logstracing True · request id sites 16 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.single_replica | an autoscaler or disruption budget is definedworkloads 1 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 10,386 · release commits 4 · changelog commits 47 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.active_contributors | withheld: this check's result would describe one person |
| 03.drive_by_contributors | withheld: this check's result would describe one person |
| 03.contributor_attrition | withheld: this check's result would describe one person |
| 03.critical_path_ownership | withheld: this check's result would describe one person |
| 03.second_contributor_attrition | withheld: this check's result would describe one person |
| 03.bus_factor_trend | withheld: this check's result would describe one person |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 1 · window last 24 months · with tracked 15 |
| 02.ci_presence | CI configuration is present in the working treecount 5 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 281 · source 758 · test ratio 0.371 |
| 02.release_cadence | tags are presenttags 10,775 |
| 02.conventional_commits | commit subjects generally carry contentsampled 4,409 · low content share 0.054 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 283 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 5 |
| 02.revert_share | change is rarely undoneshare 0.001 · reverts 1 · recent commits 1,247 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 7 · commits since 7 · days since lockfile changed 2 |
| 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 5 · product files 491 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.015 · commits 1,204 · over 2000 lines 18 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 1,639 · share of insertions 0.0024 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 19.39 · repeat share 0.091 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 664 · write once share 0.315 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0188 · product files 478 · distinct blocks 56,513 |
| 01.swallowed_errors | errors are rarely thrown awayloc 180,548 · files 1 · per kloc 0.01 |
| 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,127 |
| 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.secrets_in_history | no credential-shaped string was ever added outside test and fixture pathspatterns 8 · truncated False · added lines 617,403 |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.shell_from_strings | product code does not build shell commands from stringssites 0 |
| 05.unsafe_deserialization | no code-executing deserialiser in product codesites 0 |
| 05.resource_limits | every workload declares limitsworkloads 1 · without limits 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 0 |
| 05.credentials_in_deploy_config | deployment configuration references secrets, never holds themfiles 0 · sites 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.license_grant_unclear | the licence is recognisable as 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 4 · files with deprecations 15 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 395 · added in two years 82 · 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.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 5.0 · days since last tag -5 · commits last 90 days 141 |
| 04.release_branch | the newest release, v6.16.0, was made after the surveyed commit on the branch surveyedelsewhere 17 · on branch 170 · tags in window 188 |
| 03.single_maintainer | withheld: this check's result would describe one person |
| 05.project_advisories | no published advisory affects the surveyed versionaffecting 0 · exploited 0 · advisories 0 |
| 05.advisory_record | no advisory against the project in the last 24 monthscritical 0 · affecting 0 · could not tell 0 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 20
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.deployed_image_floats | no deployment descriptor names an image |
| 06.probes_identical | readiness and liveness are distinct, or not both set |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.joiners_and_leavers | withheld: this check's result would describe one person |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.migration_reversibility | too few migrations to judge |
| 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 8J8S-4BTJ-YDWK 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/8J8S4BTJYDWK?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: 40.3authenticated: False |
| 7.3s | cloned the repository to a temporary directory | depth: full |
| 11.8s | read the git history | commits: 5062tracked files: 1240 |
| 116.8s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 116.8s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 150.5s | kept the facts, never the source, for re-reading under new checks | |
| 150.5s | deleting the working copy |
Total 150.5s ·source content sent off this machine: none · calls to a language model: 0 · the clone was deleted when the survey ended
An automated reading of a repository's code and its history up to one commit, with public advisory records. It may be wrong, it is not legal, financial, investment or security advice, and it does not replace diligence by a qualified person. It is provided for information: nobody may rely on it (Borehole's terms, section 3).