0d8f7d7 · 20,164 commits · 10,514 files
Issued 2026-09-26
Nothing significant. Questions worth asking about Security & Reliability Posture, Engineering Process & SDLC Maturity.
91 checks ran across 6 assessable dimensions. None found a significant problem; 5 raised something worth a question. 9 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- Words about people are today's: bands rather than exact shares, dates or day counts, and what the history measured rather than why.
- 3 findings from checks Borehole's calibration found wrong more often than right are no longer published.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | adequate | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | strong | |
| 07 | Fit with the Acquirer | not assessable |
- 1% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- 39% of commits show author/committer date divergence, which is the shape of replayed history that can drop trailers
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑app/src/main/java/org/thoughtcrime/securesms/database/MessageTable.kt is 7,364 lines, 99× this codebase's median file
adequateThe median source file here is 74 lines. 51 files exceed 1,000 lines, the largest being 7,364. 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 | app/src/main/java/org/thoughtcrime/securesms/database/MessageTable.kt:1 — 7,364 lines (99× median) |
| line-count | app/src/main/java/org/thoughtcrime/securesms/conversation/v2/ConversationFragment.kt:1 — 5,679 lines (76× median) |
| line-count | app/src/main/java/org/thoughtcrime/securesms/database/RecipientTable.kt:1 — 5,571 lines (75× median) |
| line-count | app/src/main/java/org/thoughtcrime/securesms/database/AttachmentTable.kt:1 — 4,666 lines (63× median) |
| line-count | app/src/main/java/org/thoughtcrime/securesms/conversation/ConversationItem.java:1 — 3,200 lines (43× 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 ↑Little of the recent change carries a trace of review
adequateIn the last 24 months, 194 of 5,409 commits (3.6%) carry any trace of review: a merge, a pull-request reference, a Reviewed-by or Reviewed-on trailer, a Closes/Fixes reference, or a maintainer's sign-off on someone else's change. That is low but not absent. Review may happen in a workflow this history does not record; a buyer should ask how change is approved before it ships.
| reviewable-arrivals | 194 of 5,409 commits in the last 24 months carry review evidence; 10.4% across all 20,164 commits read |
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 cover a thin slice of the codebase
adequate103 test files against 1,727 source files (6.0%). 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.
| test-file-ratio | 103 test files / 1,727 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.
Organization & Key-Person Risk
03 · adequate · ratings ↑Regular contributors fell from 21 to 14 in a year
adequate9 people who committed regularly the year before made no commits in the last year, and 4 new regular contributors arrived. Ask whether the work they did is still covered.
| regular contributors by year | 21 then 14; 9 stopped committing, 4 began |
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.
Product & Engineering Maturity
04 · adequate · ratings ↑19% of bug fixes add or change a test
adequateOf 1214 fixes in the last 24 months, 225 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 | 225 of 1214 |
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 files still carry code deprecated more than two years ago
adequate13 files were marked deprecated over two years ago and still are, the oldest since Jan 2020. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
| app/src/main/java/org/thoughtcrime/securesms/util/TextSecurePreferences.java | app/src/main/java/org/thoughtcrime/securesms/util/TextSecurePreferences.java — deprecated since Jan 2020 |
| app/src/main/java/org/thoughtcrime/securesms/jobs/CleanPreKeysJob.java | app/src/main/java/org/thoughtcrime/securesms/jobs/CleanPreKeysJob.java — deprecated since Feb 2022 |
| app/src/main/java/org/thoughtcrime/securesms/util/SingleLiveEvent.java | app/src/main/java/org/thoughtcrime/securesms/util/SingleLiveEvent.java — deprecated since Sep 2022 |
| app/src/main/java/org/thoughtcrime/securesms/database/MessageTable.kt | app/src/main/java/org/thoughtcrime/securesms/database/MessageTable.kt — deprecated since Mar 2023 |
| app/src/main/java/org/thoughtcrime/securesms/components/spoiler/SpoilerDrawable.kt | app/src/main/java/org/thoughtcrime/securesms/components/spoiler/SpoilerDrawable.kt — deprecated since Mar 2023 |
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 ↑None of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| guardrail-scan | checked 5 kinds of guard rail across 10,514 tracked files; 0 present |
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 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
| no-USER-instruction | reproducible-builds/Dockerfile — runs as root |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
The app allows plain HTTP to any server
adequateThe app's manifest allows unencrypted HTTP app-wide (NSAllowsArbitraryLoads, or cleartext traffic permitted), rather than for named domains. Anything sent over plain HTTP can be read on the network, and enterprise security reviews ask about it. Some apps need it by nature (a podcast or feed reader fetches whatever URL a feed gives), so ask which case this is.
| app/src/nightlyStaging/AndroidManifest.xml | app/src/nightlyStaging/AndroidManifest.xml:6 — cleartext allowed app-wide |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Observability & Operations
06 · strong · ratings ↑No finding. 15 checks ran and none fired; the rejection log below says why each did not.
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 No architecture or design document is in the tree, across 8,085 product files. Where does the design live, and who holds it?
- 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 383 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 3,204 commits landed in the last year, against 2,188 the year before (+46%). What drove it: new people, a deadline, or code produced faster than before?
- Can this team deliver the stated roadmap on the stated timeline?
- Does leadership know about the debt, and is time budgeted to repay it?
- Is the engineering shape consistent with the commercial story?
Security & Reliability Posture
05 · partial coverage- measured 05.5 found credential-shaped strings in this repository. Was each one revoked at the provider? Deleting it from the code revokes nothing; only the provider's audit log shows that it was.
- measured The Android app requests 3 sensitive permissions: MANAGE_EXTERNAL_STORAGE, READ_CONTACTS, RECORD_AUDIO. Does the product need each one, and has the store's review accepted them?
- 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- 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 Kotlin codebase, with Java alongside (31% of source files). Does your engineering organisation already run Kotlin in production, or would this be the first?
- The bulk of this system sits in app/, feature/, lib/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (reproducible-builds/Dockerfile). 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/signalapp/signal-android/0d8f7d7)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 — 82 signals that ran and did not fire
Appendix: rejection log — 82 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 — 47
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few files, in the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026)files 33,916 · top5 share 0.025 · history read the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026) |
| 04.debt_markers | debt markers are sparsemarkers 127 · per kloc 0.14 · lines read 897,802 |
| 04.test_growth | test effort kept pace with code written, in the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026)history read the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026) · late test per code 0.06 · early test per code 0.029 |
| 04.churn_trend | rework is not rising against new work, in the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026)history read the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026) · late delete per insert 0.646 · early delete per insert 0.279 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.schema_churn | columns, once added, staydropped within 90 days 0 · columns added last year 27 |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 5,128 · compat files 1 |
| 06.telemetry_presence | this repository does not deploy a running service, so instrumentation is not expected of itbasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere · files read 6,352 |
| 06.structured_logging | not a running service; structured logging is not expected of a librarybasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.healthcheck_presence | not a running service, so a health endpoint is not expectedbasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthswindow last 24 months · authors 383 · top share a quarter or more |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 78 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.bus_factor_trend | the team has not narrowed to one person |
| 02.ci_presence | CI configuration is present in the working treecount 4 |
| 02.conventional_commits | commit subjects generally carry content, in the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026)sampled 20,075 · history read the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026) · low content share 0.002 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 29 · test files 1,914 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 4 |
| 02.revert_share | change is rarely undoneshare 0.004 · reverts 22 · recent commits 5,395 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 1 · commits since 534 · days since lockfile changed 44 |
| 02.flaky_test_markers | tests are not retried until they passtest retries 0 · suite retries 0 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.046 · commits 4,791 · over 2000 lines 220 |
| 01.burst_import | no commit run met both the rate and the net-addition threshold, in the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026)gap seconds 180 · history read the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026) · min add ratio 3.0 |
| 01.message_uniformity | commit subjects vary in wording and length, in the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026)history read the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026) · length stdev 15.46 · repeat share 0.092 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0082 · product files 5,129 · distinct blocks 492,201 |
| 01.swallowed_errors | errors are rarely thrown awayloc 904,004 · files 14 · per kloc 0.04 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 1 |
| 01.unfinished_migration | Java to Kotlin: the move is still under way: the new language's share rose in the last yearmigration Java to Kotlin · new share now 0.694 · new share at start 0.007 |
| 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 7 · files read 6,352 |
| 05.license_present | a licence file is presentfound True |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.supply_chain_pinning | third-party build steps are pinned, or fewaction refs 19 · pipe to shell 0 · unpinned third party 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.known_vulnerabilities | no locked dependency has a published advisoryadvisories 0 · dependencies 41 · high or critical 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_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.license_grant_unclear | the licence is recognisable as AGPL-3.0class network-copyleft · license AGPL-3.0 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 7 · added in two years 4 · 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 — 35
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.dependency_sprawl | no recognised dependency manifest found |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.telemetry_depth | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.print_logging | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.correlation_ids | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.error_reporting | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.alert_rules | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.deployed_image_floats | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.environment_branching | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.release_markers | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.active_contributors | not assessed: this check needs the whole history, and only the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026) were read |
| 03.knowledge_silos | not assessed: this check needs the whole history, and only the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026) were read |
| 03.drive_by_contributors | not assessed: this check needs the whole history, and only the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026) were read |
| 03.contributor_attrition | not assessed: this check needs the whole history, and only the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026) were read |
| 02.release_cadence | not assessed: this check needs the whole history, and only the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026) were read |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.initial_dump | not assessed: this check needs the whole history, and only the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026) were read |
| 01.revision_depth | not assessed: this check needs the whole history, and only the most recent 20,164 commits (24 Feb 2014 to 23 Sep 2026) were read |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.dependency_pinning | no manifest whose pinning can be read without a lockfile |
| 05.outbound_timeouts | not a running service |
| 05.migration_reversibility | too few migrations to judge |
| 05.sql_from_strings | not a running service; a library that builds SQL is doing its job |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.public_env_secret | not a frontend |
| 05.unsafe_html | not a frontend |
| 05.source_maps_shipped | not a frontend |
| 05.dataset_provenance | not a data or machine-learning repository |
| 05.license_copyleft_inherited | no third-party code is committed to this repository, so the licences it depends on are resolved at build time and are not readable here |
| 05.license_manifest_conflict | no packaging manifest states a licence |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | not a running service |
Anyone can check this report against the authoritative record — click the stamp, or enter HNKK-ZPVC-8ZRC 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/HNKKZPVC8ZRC?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.2 | 12 | adequate |
13 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 12 | adequate |
| 2026-10-03 | borehole 0.7.12 | 12 | adequate |
| 2026-10-03 | borehole 0.7.11 | 12 | adequate |
| 2026-10-02 | borehole 0.7.10 | 12 | adequate |
| 2026-09-29 | borehole 0.7.6 | 13 | adequate |
| 2026-09-29 | borehole 0.7.5 | 13 | adequate |
| 2026-09-28 | borehole 0.7.4 | 13 | adequate |
| 2026-09-27 | borehole 0.7.3 | 12 | adequate |
| 2026-09-27 | borehole 0.7.2 | 12 | adequate |
| 2026-09-27 | borehole 0.7.1 | 12 | adequate |
| 2026-09-26 | borehole 0.7.0 | 12 | adequate |
| 2026-09-26 | borehole 0.6.3 | 12 | adequate |
| 2026-09-25 | borehole 0.6.1 | 12 | 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: 2523.6authenticated: False |
| 233.9s | cloned the repository to a temporary directory | depth: 20,000 commits |
| 413.7s | read the git history | commits: 20164tracked files: 10514 |
| 828.8s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 828.8s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 1131.5s | kept the facts, never the source, for re-reading under new checks | |
| 1131.5s | deleting the working copy |
Total 1131.5s ·source content sent off this machine: none · calls to a language model: 0 · the clone was deleted when the survey ended
An automated reading of a repository's code and its history up to one commit, with public advisory records. It may be wrong, it is not legal, financial, investment or security advice, and it does not replace diligence by a qualified person. It is provided for information: nobody may rely on it (Borehole's terms, section 3).