6cd2245 · 11,572 commits · 6,053 files
Issued 2026-09-26
Nothing significant. Questions worth asking about Security & Reliability Posture, Observability & Operations.
90 checks ran across 6 assessable dimensions. 1 finding is worth checking first. 12 findings, each with evidence. One dimension cannot be assessed without an acquirer.
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 13 locked dependencies have published vulnerabilities, 12 high or critical
- Words about people are today's: bands rather than exact shares, dates or day counts, and what the history measured rather than why.
- 1 finding rated significant by a check that has not yet held up in Borehole's calibration is now worth checking first.
- 4 findings from checks Borehole's calibration found wrong more often than right are no longer published.
- The file and line of 5 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 | 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 |
- 76% of non-merge commits carry any trailer at all
- no widespread author/committer date divergence
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑gitops-engine/pkg/utils/kube/scheme/parser.go is 17,708 lines, 148× this codebase's median file
adequateThe median source file here is 119 lines. 24 files exceed 1,190 lines, the largest being 17,708. 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 | gitops-engine/pkg/utils/kube/scheme/parser.go:1 — 17,708 lines (148× median) |
| line-count | pkg/apis/application/v1alpha1/openapi_generated.go:1 — 8,625 lines (72× median) |
| line-count | pkg/apis/application/v1alpha1/types.go:1 — 4,281 lines (35× median) |
| line-count | reposerver/repository/repository.go:1 — 3,772 lines (31× median) |
| line-count | pkg/apiclient/application/application.pb.gw.go:1 — 3,744 lines (31× 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. 15 checks ran and none fired; the rejection log below says why each did not.
Organization & Key-Person Risk
03 · strong · ratings ↑No finding. 9 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · adequate · ratings ↑126 direct dependencies in a single manifest
adequatego.mod declares 126 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 — 126 declared |
| direct-dependencies | ui/package.json — 39 declared |
| direct-dependencies | gitops-engine/go.mod — 25 declared |
| direct-dependencies | docs/requirements.txt — 8 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.
8 files still carry code deprecated more than two years ago
adequate8 files were marked deprecated over two years ago and still are, the oldest since Oct 2018. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
| pkg/client/informers/externalversions/factory.go | pkg/client/informers/externalversions/factory.go — deprecated since Oct 2018 |
| pkg/apiclient/repository/repository.pb.go | pkg/apiclient/repository/repository.pb.go — deprecated since Oct 2019 |
| server/repository/repository.go | server/repository/repository.go — deprecated since Oct 2019 |
| pkg/apis/application/v1alpha1/types.go | pkg/apis/application/v1alpha1/types.go — deprecated since Dec 2019 |
| pkg/apis/application/v1alpha1/openapi_generated.go | pkg/apis/application/v1alpha1/openapi_generated.go — deprecated since Dec 2019 |
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 ↑19 credential-shaped strings 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.
| Slack token | Slack token, where fakes are usual |
| private key block | 4 cited: private key block, 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
adequate2 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; 1 step pipes 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.
| .github/workflows/image.yaml | .github/workflows/image.yaml:145 — action pinned by tag |
| .github/workflows/release.yaml | .github/workflows/release.yaml:210 — action pinned by tag |
| .github/workflows/ci-build.yaml | .github/workflows/ci-build.yaml:621 — 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.
3 outbound calls can wait forever
adequate3 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.
| applicationset/generators/scm_provider.go | applicationset/generators/scm_provider.go:325 — outbound call without a timeout |
| applicationset/utils/utils.go | applicationset/utils/utils.go:632 — outbound call without a timeout |
| pkg/apiclient/apiclient.go | pkg/apiclient/apiclient.go:302 — 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.
25 of 25 Kubernetes workloads declare no resource limits
adequate25 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.
| gitops-engine/agent/manifests/base/gitops-agent-deploy.yaml | gitops-engine/agent/manifests/base/gitops-agent-deploy.yaml — workload with no limits |
| gitops-engine/agent/manifests/install-namespaced.yaml | gitops-engine/agent/manifests/install-namespaced.yaml — workload with no limits |
| gitops-engine/agent/manifests/install.yaml | gitops-engine/agent/manifests/install.yaml — workload with no limits |
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.
13 locked dependencies have published vulnerabilities, 12 high or critical
adequate worth checking first13 of 1,568 locked dependencies match 28 published advisories in OSV, 12 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.
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 and the 1 other file it cites settles it. If it holds when someone checks it, this finding is significant.
| go.mod | go.mod — github.com/go-git/go-git/v5 v5.19.1: GHSA-hc8v-wwc9-vgxm (high), fixed in 5.19.2 |
| ui/pnpm-lock.yaml | ui/pnpm-lock.yaml — brace-expansion 1.1.14: GHSA-3jxr-9vmj-r5cp (high), fixed in 1.1.16 |
| ui/pnpm-lock.yaml | ui/pnpm-lock.yaml — brace-expansion 2.1.0: GHSA-3jxr-9vmj-r5cp (high), fixed in 2.1.2 |
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.
3 of 8 deployed images carry no version, or `latest`
adequate3 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.
| gitops-engine/agent/manifests/install.yaml | gitops-engine/agent/manifests/install.yaml:56 — image without a version |
| manifests/namespace-install.yaml | manifests/namespace-install.yaml:2901 — image without a version |
| manifests/dev-tilt/ui-deployment.yaml | manifests/dev-tilt/ui-deployment.yaml:16 — 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.
Readiness and liveness probes are identical in 2 of 15 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
| manifests/ha/namespace-install-with-hydrator.yaml | manifests/ha/namespace-install-with-hydrator.yaml — same probe endpoint twice |
| manifests/ha/namespace-install.yaml | manifests/ha/namespace-install.yaml — same probe endpoint twice |
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 of 25 deployments run a single replica
adequate6 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
| manifests/base/application-controller-deployment/argocd-application-controller-deployment.yaml | manifests/base/application-controller-deployment/argocd-application-controller-deployment.yaml — replicas: 1 |
| manifests/base/application-controller/argocd-application-controller-statefulset.yaml | manifests/base/application-controller/argocd-application-controller-statefulset.yaml — replicas: 1 |
| manifests/ha/namespace-install-with-hydrator.yaml | manifests/ha/namespace-install-with-hydrator.yaml — replicas: 1 |
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
10 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/operator-manual/architecture.md). Does it match what the team believes today? Ask them to walk through it against the code.
- Is the architecture right for the next three years of the product?
- Were the home-grown components reasonable choices when they were made, and are they now?
Engineering Process & SDLC Maturity
02 · high coverage- Is review real or a rubber stamp? Comment depth and time to approve need the pull request history.
- Is delivery planned and measured, or heroic?
- How are incidents run, reviewed and learned from?
Organization & Key-Person Risk
03 · partial coverage- measured 2,002 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 A roadmap file is in the tree (docs/roadmap.md, last changed January 2023). 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 05.1 and 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 Backup or restore tooling is in the tree (resource_customizations/astra.netapp.io/Backup/health_test.yaml). Has a restore ever been rehearsed, and how long did it take?
- measured Alert rules are defined in the repository. 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, with Lua alongside (37% of source files). Does your engineering organisation already run Go in production, or would this be the first?
- The bulk of this system sits in pkg/, manifests/, util/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (Dockerfile and 14 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/argoproj/argo-cd/6cd2245)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 — 78 signals that ran and did not fire
Appendix: rejection log — 78 signals that ran and did not fire
Published on purpose. A signal that looked and decided not to fire has told you something, and this is the calibration data behind every threshold above.
Looked, and found nothing — 67
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 11,322 · top5 share 0.051 |
| 04.debt_markers | debt markers are sparsemarkers 191 · per kloc 0.22 · lines read 874,548 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.29 · early delete per insert 0.453 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fixes_with_tests | fixes usually come with a testfixes 1,086 · share 0.497 · with tests 540 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.003 · code files 756 · compat files 2 |
| 04.dependency_redundancy | one library per job, mostly |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 41 |
| 06.structured_logging | a structured logging library is referencedmatches 233 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.telemetry_depth | the service is visible in more than one way |
| 06.correlation_ids | a request can be followed through the logstracing True · request id sites 2 |
| 06.alert_rules | alert rules are defined as codealert files 1 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 78 · release commits 0 · changelog commits 24 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 8.6 · window last 24 months · authors 2,002 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 2,002 · active 12mo 366 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 2,008 · directories 22 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 2,002 · one off share 0.709 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 2,002 · top share less than a quarter · top contributor last committed within the last three months |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 669 |
| 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 22 · joined 32 · regular last year 61 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 27 · window last 24 months · with tracked 26 |
| 02.ci_presence | CI configuration is present in the working treecount 19 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 498 · source 1,342 · test ratio 0.371 |
| 02.release_cadence | tags are presenttags 596 |
| 02.conventional_commits | commit subjects generally carry contentsampled 11,497 · low content share 0.0 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 17 · with tests 1 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 2,876 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 19 |
| 02.revert_share | change is rarely undoneshare 0.002 · reverts 6 · recent commits 2,459 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 4 · commits since 2 · days since lockfile changed 0 |
| 02.flaky_test_markers | tests are not retried until they passtest retries 0 · suite retries 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 4 · ci configs 19 · product files 756 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.011 · commits 2,176 · over 2000 lines 24 |
| 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 888 · share of insertions 0.0001 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 19.39 · repeat share 0.004 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0041 · product files 733 · distinct blocks 142,989 |
| 01.swallowed_errors | errors are rarely thrown awayloc 879,057 · files 0 · per kloc 0.0 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 5 |
| 01.unfinished_migration | no language migration is stalled halfway |
| 01.weights_in_git | no model weights are committedfiles 0 |
| 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.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.sql_from_strings | no SQL is assembled from strings in product codefiles 0 · sites 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.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 |
| 05.credentials_in_deploy_config | deployment configuration references secrets, never holds themfiles 0 · sites 0 |
| 05.public_env_secret | only publishable values carry a public prefixnames 0 · sites 0 · not secrets 0 |
| 05.unsafe_html | raw HTML is rare, literal or sanitisedsites 0 |
| 05.source_maps_shipped | production builds do not publish source mapssites 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 3 |
| 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 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 353 · added in two years 98 · removed within 60 days 11 |
| 04.ci_platforms_dropped | no platform was dropped from CI in the last two years |
Could not conclude, or did not apply — 11
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.schema_churn | no schema migrations to read |
| 06.print_logging | a frontend: console output is the browser's, not the server's |
| 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.notebook_outputs | not a data or machine-learning repository |
| 05.migration_reversibility | too few migrations to judge |
| 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 |
Anyone can check this report against the authoritative record — click the stamp, or enter YWB4-44M2-X2HT at borehole.dev/verify.
The code commits to the 94 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/YWB444M2X2HT?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-26 · shown | borehole 0.6.3 | 16 | adequate |
15 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 17 | adequate |
| 2026-10-03 | borehole 0.7.12 | 17 | adequate |
| 2026-10-03 | borehole 0.7.11 | 17 | adequate |
| 2026-10-02 | borehole 0.7.10 | 17 | adequate |
| 2026-10-01 | borehole 0.7.9 | 17 | adequate |
| 2026-09-30 | borehole 0.7.8 | 16 | adequate |
| 2026-09-29 | borehole 0.7.6 | 16 | adequate |
| 2026-09-28 | borehole 0.7.5 | 16 | adequate |
| 2026-09-28 | borehole 0.7.4 | 16 | adequate |
| 2026-09-27 | borehole 0.7.3 | 15 | adequate |
| 2026-09-27 | borehole 0.7.2 | 16 | adequate |
| 2026-09-27 | borehole 0.7.1 | 16 | adequate |
| 2026-09-26 | borehole 0.7.0 | 16 | adequate |
| 2026-09-26 | borehole 0.6.2 | 16 | adequate |
| 2026-09-25 | borehole 0.6.1 | 14 | 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 — 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: 216.5authenticated: False |
| 42.4s | cloned the repository to a temporary directory | depth: full |
| 100.7s | read the git history | commits: 11572tracked files: 6053 |
| 327.7s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 327.8s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 492.8s | kept the facts, never the source, for re-reading under new checks | |
| 492.8s | deleting the working copy |
Total 492.8s ·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).