af8c6d3 · 2,048 commits · 2,936 files
Issued 2026-10-28
Nothing significant. Questions worth asking about Security & Reliability Posture, Engineering Process & SDLC Maturity.
105 checks ran across 6 assessable dimensions. 1 finding is worth checking first. 8 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- states a policy on AI-generated contributions AGENTS.md:469
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 79 locked dependencies have published vulnerabilities, 57 high or critical in what ships
- 1 finding from checks Borehole's calibration found wrong more often than right is no longer published.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 03 | Organization & Key-Person Risk | strong | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 38% 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
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑packages/swc-plugin-workflow/transform/src/lib.rs is 10,502 lines, 128× this codebase's median file
adequateThe median source file here is 82 lines. 42 files exceed 1,000 lines, the largest being 10,502. 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 | packages/swc-plugin-workflow/transform/src/lib.rs:1 — 10,502 lines (128× median) |
| line-count | packages/core/src/runtime.ts:1 — 5,812 lines (70× median) |
| line-count | packages/core/src/serialization.ts:1 — 4,567 lines (55× median) |
| line-count | packages/world-local/src/storage/events-storage.ts:1 — 4,111 lines (50× median) |
| line-count | packages/world-postgres/src/storage.ts:1 — 3,707 lines (45× 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 · adequate · ratings ↑CI runs tests that cannot fail the build
adequate2 test commands in CI end in `|| true` or an equivalent, so the pipeline passes whatever the tests say. A green build then means the tests ran, not that they passed.
| .github/workflows/e2e-community-world.yml | .github/workflows/e2e-community-world.yml:228 — a test command that cannot fail |
| .github/workflows/e2e-community-world.yml | .github/workflows/e2e-community-world.yml:230 — a test command that cannot fail |
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.
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/core/src/serialization-format.test.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
A note that does not affect this rating: notes like it are common in well-run projects.
| packages/core/src/serialization-format.test.ts | packages/core/src/serialization-format.test.ts:302 — test retry |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Organization & Key-Person Risk
03 · strong · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · strong · ratings ↑No finding. 19 checks ran and none fired; the rejection log below says why each did not.
Security & Reliability Posture
05 · adequate · ratings ↑79 locked dependencies have published vulnerabilities, 57 high or critical in what ships
adequate worth checking first79 of 3,147 locked dependencies match 184 published advisories in OSV, 83 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 pnpm-lock.yaml settles it. If it holds when someone checks it, this finding is significant.
| pnpm-lock.yaml | pnpm-lock.yaml — next 16.3.8: GHSA-2464-fhr4-w9xw (critical), fixed in 16.4.1 |
| pnpm-lock.yaml | pnpm-lock.yaml — piscina 4.9.2: GHSA-67c8-pqhq-4rmx (critical), fixed in 4.9.4 |
| pnpm-lock.yaml | pnpm-lock.yaml — tar 7.4.3: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19 |
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 production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
| tarballs/vite.config.ts | tarballs/vite.config.ts:14 — source maps in a production build |
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 shell commands built from strings
adequate2 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| packages/swc-plugin-workflow/build.js | packages/swc-plugin-workflow/build.js:22 — command run through a shell |
| workbench/swc-playground/wasm/build.js | workbench/swc-playground/wasm/build.js:16 — command run through 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.
4 places insert HTML from a variable without sanitising it
adequate4 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| packages/web-shared/src/components/ui/decrypt-button.tsx | packages/web-shared/src/components/ui/decrypt-button.tsx:33 — HTML from a variable |
| packages/web-shared/src/components/ui/load-more-button.tsx | packages/web-shared/src/components/ui/load-more-button.tsx:26 — HTML from a variable |
| packages/web-shared/src/components/ui/menu-dropdown.tsx | packages/web-shared/src/components/ui/menu-dropdown.tsx:46 — HTML from a variable |
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 structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| logging-scan | searched 2,270 files for 10 structured logging libraries; 0 matched |
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
4 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 (packages/world-sim/DESIGN.md). Does it match what the team believes today? Ask them to walk through it against the code.
- Is the architecture right for the next three years of the product?
- Were the home-grown components reasonable choices when they were made, and are they now?
Engineering Process & SDLC Maturity
02 · high coverage- Is review real or a rubber stamp? Comment depth and time to approve need the pull request history.
- Is delivery planned and measured, or heroic?
- How are incidents run, reviewed and learned from?
Organization & Key-Person Risk
03 · partial coverage- measured 130 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- 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 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 TypeScript codebase. Does your engineering organisation already run TypeScript in production, or would this be the first?
- The bulk of this system sits in packages/, workbench/, skills/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (packages/world-postgres/docker-compose.yaml). 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/vercel/workflow/af8c6d3)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 — 97 signals that ran and did not fire
Appendix: rejection log — 97 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 — 73
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 6,475 · top5 share 0.03 |
| 04.debt_markers | debt markers are sparsemarkers 40 · per kloc 0.08 · lines read 513,535 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.972 · early test per code 0.369 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.358 · early delete per insert 0.311 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fixes_with_tests | fixes usually come with a testfixes 538 · share 0.571 · with tests 307 |
| 04.compat_layers | little code is kept for the old wayshare 0.001 · code files 953 · compat files 1 |
| 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 105 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.correlation_ids | a request can be followed through the logstracing True · request id sites 96 |
| 06.error_reporting | an error reporter is initialisedinitialised 0 · config files 3 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 851 · release commits 2 · changelog commits 35 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 1.0 · window last 24 months · authors 130 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 130 · active 12mo 119 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 130 · directories 5 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 130 · one off share 0.646 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 130 · 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 130 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.joiners_and_leavers | the team is not shrinkingleft 0 · joined 27 · regular last year 32 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 1 · window last 24 months · with tracked 38 |
| 02.ci_presence | CI configuration is present in the working treecount 14 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 788 · source 1,740 · test ratio 0.453 |
| 02.release_cadence | tags are presenttags 851 |
| 02.conventional_commits | commit subjects generally carry contentsampled 2,047 · low content share 0.002 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 14 · with tests 7 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 15 · test files 828 |
| 02.revert_share | change is rarely undoneshare 0.007 · reverts 13 · recent commits 1,894 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 3 · commits since 11 · days since lockfile changed 3 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 21 · ci configs 14 · product files 953 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.048 · commits 1,709 · over 2000 lines 82 |
| 01.burst_import | no commit run met both the rate and the net-addition thresholdgap seconds 180 · min add ratio 3.0 · min net added 2,000 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 201,396 · share of insertions 0.1881 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 19.69 · repeat share 0.001 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 1,312 · write once share 0.407 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0103 · product files 877 · distinct blocks 121,844 |
| 01.swallowed_errors | errors are rarely thrown awayloc 515,794 · files 11 · per kloc 0.03 |
| 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 2,270 |
| 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 973,673 |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.supply_chain_pinning | third-party build steps are pinned, or fewaction refs 109 · pipe to shell 0 · unpinned third party 0 |
| 05.sql_from_strings | no SQL is assembled from strings in product codefiles 0 · sites 0 · value interpolated 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 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.public_env_secret | only publishable values carry a public prefixnames 0 · sites 0 · not secrets 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_manifest_conflict | manifest and licence file agree on Apache-2.0license Apache-2.0 |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.license_grant_unclear | the licence is recognisable as Apache-2.0class permissive · license Apache-2.0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 0 · files with deprecations 23 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 288 · added in two years 288 · removed within 60 days 32 |
| 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 | relicensed only between permissive licences: MIT → Apache-2.0 (2025-11-03)latest Apache-2.0 · weaker False · licence versions 2 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 0.0 · days since last tag 1 · commits last 90 days 505 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 34 · on branch 138 · tags in window 172 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 24
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.fix_share_trend | fewer than six busy quarters to compare |
| 04.schema_churn | no schema migrations to read |
| 06.print_logging | a frontend: console output is the browser's, not the server's |
| 06.alert_rules | no alert rules in the repository; they may live in a console |
| 06.deployed_image_floats | no deployment descriptor names an image |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.bus_factor_trend | fewer than three active years to compare |
| 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.container_runs_as_root | no Dockerfile to read |
| 05.outbound_timeouts | not assessed for TypeScript, the language the product is written in: this check's patterns read other languages only |
| 05.migration_reversibility | too few migrations to judge |
| 05.resource_limits | no Kubernetes workload manifests |
| 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 |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | one API version is served, or none |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; OSV npm @workflow/ai (an empty record for a package published here), OSV npm @workflow/astro (an empty record for a package published here), OSV npm @workflow/builders (an empty record for a package published here), OSV npm @workflow/cli (an empty record for a package published here), OSV npm @workflow/errors (an empty record for a package published here), OSV npm @workflow/nest (an empty record for a package published here), OSV npm @workflow/next (an empty record for a package published here), OSV npm @workflow/nitro (an empty record for a package published here), OSV npm @workflow/nuxt (an empty record for a package published here), OSV npm @workflow/rollup (an empty record for a package published here), OSV npm @workflow/serde (an empty record for a package published here), OSV npm @workflow/sveltekit (an empty record for a package published here), OSV npm @workflow/swc-plugin (an empty record for a package published here), OSV npm @workflow/typescript-plugin (an empty record for a package published here), OSV npm @workflow/utils (an empty record for a package published here), OSV npm @workflow/vite (an empty record for a package published here), OSV npm @workflow/vitest (an empty record for a package published here), OSV npm @workflow/web-shared (an empty record for a package published here), OSV npm @workflow/web (an empty record for a package published here), OSV npm @workflow/world-local (an empty record for a package published here), OSV npm @workflow/world-postgres (an empty record for a package published here), OSV npm @workflow/world-testing (an empty record for a package published here), OSV npm @workflow/world-vercel (an empty record for a package published here) did not; NVD: 558 records name workflow with nothing tying them to this repository (CVE-2006-6705, CVE-2006-6706, CVE-2007-1854, …) |
| 05.advisory_record | 1 advisory in the last 24 months, none high or critical, none affecting the surveyed version; the newest on 2026-03-05; record incomplete: NVD: 558 records name workflow with nothing tying them to this repository (CVE-2006-6705, CVE-2006-6706, CVE-2007-1854, …) |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited list |
Anyone can check this report against the authoritative record — click the stamp, or enter ZDJ3-X1AY-FSQY 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/ZDJ3X1AYFSQY?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: 121.5authenticated: False |
| 18.5s | cloned the repository to a temporary directory | depth: full |
| 26.9s | read the git history | commits: 2048tracked files: 2936 |
| 213.1s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 213.2s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 318.8s | kept the facts, never the source, for re-reading under new checks | |
| 318.8s | deleting the working copy |
Total 318.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).