c512e06 · 9,696 commits · 8,999 files
Issued 2026-09-25
Nothing significant. Questions worth asking about Security & Reliability Posture, Architecture & Codebase — including AI provenance.
89 checks ran across 6 assessable dimensions. 2 findings are worth checking first. 10 findings, each with evidence. One dimension cannot be assessed without an acquirer.
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.
- Words about people are today's: bands rather than exact shares, dates or day counts, and what the history measured rather than why.
- 2 findings rated significant by a check that has not yet held up in Borehole's calibration are now worth checking first.
- 5 findings from checks Borehole's calibration found wrong more often than right are no longer published.
- The file and line of 1 credential-shaped match is 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 | adequate | |
| 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 |
- 16% 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 · adequate · ratings ↑src/modules/cmdpal/ext/Microsoft.CmdPal.Ext.WindowsSettings/Properties/Resources.Designer.cs is 4,951 lines, 85× this codebase's median file
adequateThe median source file here is 58 lines. 49 files exceed 1,000 lines, the largest being 4,951. 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 | src/modules/cmdpal/ext/Microsoft.CmdPal.Ext.WindowsSettings/Properties/Resources.Designer.cs:1 — 4,951 lines (85× median) |
| line-count | src/modules/launcher/Plugins/Microsoft.PowerToys.Run.Plugin.WindowsSettings/Properties/Resources.Designer.cs:1 — 4,870 lines (83× median) |
| line-count | src/modules/registrypreview/RegistryPreviewUILib/Controls/HexBox/HexBox.cs:1 — 2,914 lines (50× median) |
| line-count | src/modules/MouseUtils/CursorWrap/CursorWrapTests/WrapSimulator/wrap_simulator.py:1 — 2,376 lines (40× median) |
| line-count | src/modules/MouseWithoutBorders/App/Class/SocketStuff.cs:1 — 2,131 lines (36× 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.
1 model weight file committed directly to git
adequate1 model weight files are stored in git itself, not in LFS, DVC or a model hub. Every clone carries them, the history keeps every version for good, and nothing records which run or data produced them.
| src/modules/ZoomIt/ZoomIt/selfie_segmentation.onnx | src/modules/ZoomIt/ZoomIt/selfie_segmentation.onnx — weights in git |
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 ↑Tests cover a thin slice of the codebase
adequate worth checking first16 test files against 4,419 source files (0.4%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
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. If it holds when someone checks it, this finding is significant.
| test-file-ratio | 16 test files / 4,419 source files |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
5% of recent commits change more than 2,000 lines
adequate108 of 2022 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| git log --numstat | 108 commits over 2,000 lines |
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. 9 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · adequate · ratings ↑11% of bug fixes add or change a test
adequateOf 593 fixes in the last 24 months, 66 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| fix commits touching tests | 66 of 593 |
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.
5 files still carry code deprecated more than two years ago
adequate5 files were marked deprecated over two years ago and still are, the oldest since Apr 2020. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
| src/modules/launcher/Wox.Infrastructure/Alphabet.cs | src/modules/launcher/Wox.Infrastructure/Alphabet.cs — deprecated since Apr 2020 |
| src/modules/launcher/Wox.Plugin/Query.cs | src/modules/launcher/Wox.Plugin/Query.cs — deprecated since Apr 2020 |
| src/modules/launcher/Wox.Infrastructure/StringMatcher.cs | src/modules/launcher/Wox.Infrastructure/StringMatcher.cs — deprecated since Apr 2020 |
| src/modules/launcher/Wox.Infrastructure/FuzzyMatcher.cs | src/modules/launcher/Wox.Infrastructure/FuzzyMatcher.cs — deprecated since Apr 2020 |
| src/modules/launcher/Wox.Infrastructure/MatchOption.cs | src/modules/launcher/Wox.Infrastructure/MatchOption.cs — deprecated since Aug 2020 |
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 ↑1 credential-shaped string committed to the tree
adequate worth checking firstMatches for JWT appear in tracked files outside test and fixture paths. Whether these are live is not something a repository can settle, and they may well be rotated already — but they are in the history permanently, and the question a buyer must ask is what the rotation process was, not whether one string still works.
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. If it holds when someone checks it, this finding is significant.
| JWT | JWT pattern matched |
| 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.
2 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
| deps/spdlog.props | deps/spdlog.props — 1 tracked files, no licence file |
| deps/vcpkg-overlays | deps/vcpkg-overlays — 3 tracked files, no licence file |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Observability & Operations
06 · adequate · ratings ↑The service logs with print: 79 calls against 0 logger calls
adequate79 `print` or `console.log` calls in the service's code, and 0 calls through a logger. Printed lines carry no level and no context, cannot be switched off, and are hard to find again in production.
| src/modules/MouseUtils/CursorWrap/CursorWrapTests/analyze_test_results.py | src/modules/MouseUtils/CursorWrap/CursorWrapTests/analyze_test_results.py:27 — print used for logging |
| src/modules/MouseUtils/CursorWrap/CursorWrapTests/analyze_test_results.py | src/modules/MouseUtils/CursorWrap/CursorWrapTests/analyze_test_results.py:28 — print used for logging |
| src/modules/MouseUtils/CursorWrap/CursorWrapTests/analyze_test_results.py | src/modules/MouseUtils/CursorWrap/CursorWrapTests/analyze_test_results.py:29 — print used for logging |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| 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
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 (doc/devdocs/core/architecture.md and 2 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 coverage- measured 710 people have committed here. Which of them are you acquiring, and which are you replacing?
- Who mentors whom, and would that survive a departure?
- Can the team grow, and who stands behind the top three contributors?
- Is the seniority mix sound, and will pay survive your salary bands?
- Is the pace sustainable? Commit times cannot say: git keeps no reliable local time.
- Does the team want to stay after close?
- How are decisions made and disagreements resolved?
Product & Engineering Maturity
04 · minimal coverage- measured 1,325 commits landed in the last year, against 868 the year before (+53%). What drove it: new people, a deadline, or code produced faster than before?
- Can this team deliver the stated roadmap on the stated timeline?
- Does leadership know about the debt, and is time budgeted to repay it?
- Is the engineering shape consistent with the commercial story?
Security & Reliability Posture
05 · partial coverage- measured 05.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 (.pipelines/v2/templates/steps-restore-nuget.yml). Has a restore ever been rehearsed, and how long did it take?
- 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 C# codebase. Does your engineering organisation already run C# in production, or would this be the first?
- The bulk of this system sits in src/, installer/, deps/. Which of your existing systems would each of those have to absorb or replace?
- Nothing in the repository says how this is deployed. Is it shipped as a library, a binary or a service, and if it runs somewhere, who owns that environment?
- 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/microsoft/powertoys/c512e06)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 — 79 signals that ran and did not fire
Appendix: rejection log — 79 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 — 56
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 23,619 · top5 share 0.026 |
| 04.debt_markers | debt markers are sparsemarkers 202 · per kloc 0.29 · lines read 686,418 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.076 · early test per code 0.044 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.445 · early delete per insert 0.452 |
| 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 3,744 · 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 4 |
| 06.structured_logging | a structured logging library is referencedmatches 1 |
| 06.correlation_ids | a request can be followed through the logstracing False · request id sites 9 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 35 · release commits 2 · changelog commits 14 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 12.8 · window last 24 months · authors 710 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 710 · active 12mo 146 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 713 · directories 5 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 710 · one off share 0.635 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 710 · 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 234 |
| 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 16 · joined 17 · regular last year 37 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 197 |
| 02.ci_presence | CI configuration is present in the working treecount 11 |
| 02.release_cadence | tags are presenttags 156 |
| 02.conventional_commits | commit subjects generally carry contentsampled 9,097 · low content share 0.025 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 750 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 11 |
| 02.revert_share | change is rarely undoneshare 0.004 · reverts 9 · recent commits 2,198 |
| 02.flaky_test_markers | tests are not retried until they passtest retries 0 · suite retries 0 |
| 01.burst_import | the largest burst was merged pull requests, each developed and reviewed on its own branch (100% of its lines), which explains the rate: translations arrive from a vendor in bulk, dependencies and generated code are committed whole, a merged pull request is dated when it merged, not when it was written, and a branch merged by a merge commit was reviewed as one piecelargest commits 7d8f7aa..7e22f26 · bursts explained 2 · largest net added 61,217 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 132 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 27.69 · repeat share 0.062 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 23,629 · write once share 0.473 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0286 · product files 3,642 · distinct blocks 255,526 |
| 01.swallowed_errors | errors are rarely thrown awayloc 691,245 · files 72 · per kloc 0.21 |
| 01.unfinished_migration | no language migration is stalled halfway |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.dependency_pinning | dependencies are substantially pinnedunpinned 0 |
| 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.supply_chain_pinning | third-party build steps are pinned, or fewaction refs 64 · pipe to shell 0 · unpinned third party 0 |
| 05.outbound_timeouts | outbound calls set timeouts, or are fewcalls without timeout 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.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 |
| 05.credentials_in_deploy_config | deployment configuration references secrets, never holds themfiles 0 · sites 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_copyleft_inherited | every licence found in vendored code is permissive or weak-copyleftvendored paths 4 |
| 05.license_grant_unclear | the licence is recognisable as MITclass permissive · license MIT |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 17 · added in two years 5 · removed within 60 days 0 |
| 04.ci_platforms_dropped | no platform was dropped from CI in the last two years |
Could not conclude, or did not apply — 23
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.eol_runtime | no pinned runtime version to check |
| 04.schema_churn | no schema migrations to read |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.alert_rules | no alert rules in the repository; they may live in a console |
| 06.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 |
| 02.dependency_update_cadence | no lockfile to date |
| 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.migration_reversibility | too few migrations to judge |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.known_vulnerabilities | no lockfile this survey can read, or a collector older than 0.4.0 |
| 05.public_env_secret | not a frontend |
| 05.unsafe_html | not a frontend |
| 05.source_maps_shipped | not a frontend |
| 05.cleartext_traffic | not a mobile app |
| 05.dataset_provenance | not a data or machine-learning repository |
| 05.license_manifest_conflict | no packaging manifest states a licence |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | one API version is served, or none |
Anyone can check this report against the authoritative record — click the stamp, or enter CZS9-B735-0G10 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/CZS9B7350G10?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-25 · shown | borehole 0.6.1 | 15 | adequate |
15 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 8 | adequate |
| 2026-10-03 | borehole 0.7.12 | 8 | adequate |
| 2026-10-03 | borehole 0.7.11 | 8 | adequate |
| 2026-10-02 | borehole 0.7.10 | 8 | adequate |
| 2026-10-01 | borehole 0.7.9 | 8 | adequate |
| 2026-09-30 | borehole 0.7.8 | 8 | adequate |
| 2026-09-29 | borehole 0.7.6 | 11 | adequate |
| 2026-09-28 | borehole 0.7.5 | 11 | adequate |
| 2026-09-28 | borehole 0.7.4 | 11 | adequate |
| 2026-09-27 | borehole 0.7.3 | 7 | adequate |
| 2026-09-27 | borehole 0.7.2 | 7 | adequate |
| 2026-09-27 | borehole 0.7.1 | 7 | adequate |
| 2026-09-26 | borehole 0.7.0 | 7 | adequate |
| 2026-09-26 | borehole 0.6.3 | 8 | adequate |
| 2026-09-26 | borehole 0.6.2 | 8 | 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: 512.9authenticated: False |
| 28.8s | cloned the repository to a temporary directory | depth: full |
| 41.1s | read the git history | commits: 9696tracked files: 8999 |
| 187.2s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 187.3s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 262.1s | kept the facts, never the source, for re-reading under new checks | |
| 262.1s | deleting the working copy |
Total 262.1s ·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).