5cf3a36 · 7,210 commits · 4,597 files
Issued 2026-09-27
Nothing significant. Questions worth asking about Security & Reliability Posture, Organization & Key-Person Risk.
102 checks ran across 6 assessable dimensions. None found a significant problem; 3 raised something worth a question. 11 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.
- 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 | adequate | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | not assessable | |
| 07 | Fit with the Acquirer | not assessable |
- 6% 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
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑frontend/appflowy_flutter/lib/workspace/presentation/settings/widgets/emoji_picker/src/emoji_lists.dart is 3,224 lines, 37× this codebase's median file
adequateThe median source file here is 85 lines. 16 files exceed 1,000 lines, the largest being 3,224. 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 | frontend/appflowy_flutter/lib/workspace/presentation/settings/widgets/emoji_picker/src/emoji_lists.dart:1 — 3,224 lines (37× median) |
| line-count | frontend/rust-lib/flowy-folder/src/manager.rs:1 — 2,638 lines (31× median) |
| line-count | frontend/rust-lib/flowy-database2/src/services/database/database_editor.rs:1 — 2,465 lines (29× median) |
| line-count | frontend/appflowy_flutter/lib/shared/popup_menu/appflowy_popup_menu.dart:1 — 1,668 lines (19× median) |
| line-count | frontend/rust-lib/flowy-database2/src/event_handler.rs:1 — 1,451 lines (17× median) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Engineering Process & SDLC Maturity
02 · strong · ratings ↑No finding. 16 checks ran and none fired; the rejection log below says why each did not.
Organization & Key-Person Risk
03 · adequate · ratings ↑The contributor who wrote a quarter or more of this has not committed here for more than six months
adequateOne person authored a quarter or more of 6,362 commits and has not committed here for more than six months, while the repository has kept moving. The concentration figure alone would not show this. Whoever is changing this code now is not the person who wrote most of it, which is the situation an acquirer is usually told they are avoiding. The history shows only that no commits of theirs landed here, not why.
| last-commit-by-top-author | last commit more than six months ago, measured to the survey |
| git shortlog -sn | top author a quarter or more of 6,362 commits |
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.
One person alone changes infrastructure
adequateIn the last 24 months, of 85 contributors, a single person made every change to: infrastructure (13 commits). These are the parts where a mistake is expensive and where knowledge is hardest to rebuild. Ask who else could change them safely tomorrow.
| git log -- <area> | sole author over 24 months: infrastructure (13 commits) |
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 next contributor after the top one has not committed here for more than a year
adequateThe #2 contributor of the last three years (less than a quarter of the commits) has not committed here for more than six months, while the repository is still active. These are the people a buyer assumes would step up if the top contributor stopped. The history shows only that no commits of theirs landed here, not why.
| git shortlog -sn | the #2 contributor of the last three years (less than a quarter of the commits) has not committed here for more than six months |
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.
Regular contributors fell from 14 to 1 in a year
adequate12 people who committed regularly the year before made no commits in the last year, and 0 new regular contributors arrived. Ask whether the work they did is still covered.
| regular contributors by year | 14 then 1; 12 stopped committing, 0 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 · 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 ↑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 4,597 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 environment file is committed
adequatefrontend/rust-lib/flowy-sqlite/.env is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
| frontend/rust-lib/flowy-sqlite/.env | frontend/rust-lib/flowy-sqlite/.env — committed environment 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.
The build runs third-party code it does not pin
adequate19 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; 3 steps pipe a download straight into a shell. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
| .github/workflows/commit_lint.yml | .github/workflows/commit_lint.yml:11 — action pinned by tag |
| .github/workflows/docker_ci.yml | .github/workflows/docker_ci.yml:23 — action pinned by tag |
| frontend/scripts/docker-buildfiles/Dockerfile | frontend/scripts/docker-buildfiles/Dockerfile:23 — 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.
53 locked dependencies have published vulnerabilities, 13 high or critical
adequate53 of 799 locked dependencies match 77 published advisories in OSV, 13 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.
| frontend/rust-lib/Cargo.lock | frontend/rust-lib/Cargo.lock — diesel 2.2.10: GHSA-h5x4-m2qf-r4f2 (high), fixed in 2.3.8 |
| frontend/rust-lib/Cargo.lock | frontend/rust-lib/Cargo.lock — lz4_flex 0.11.2: GHSA-vvp9-7p8x-rfvv (high), fixed in 0.11.6 |
| frontend/rust-lib/Cargo.lock | frontend/rust-lib/Cargo.lock — mio 0.8.9: GHSA-r8w9-5wcg-vfj7 (high), fixed in 0.8.11 |
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.
| frontend/appflowy_flutter/ios/Runner/Info.plist | frontend/appflowy_flutter/ios/Runner/Info.plist:46 — cleartext allowed app-wide |
| frontend/appflowy_flutter/macos/Runner/Info.plist | frontend/appflowy_flutter/macos/Runner/Info.plist:47 — 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.
Relicensed: Apache-2.0 → AGPL-3.0 (2021-11-09)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
| a4fb87713 | LICENSE — Apache-2.0 from 2021-06-16 |
| e697a6d33 | LICENSE — AGPL-3.0 from 2021-11-09 |
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 · not assessable · ratings ↑Not rated: only 3 of 15 checks could reach a conclusion here; the rest do not apply to this repository or could not read it. What a person adds here.
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
5 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 3,552 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 387 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 16 commits landed in the last year, against 1,434 the year before (-99%). Is that maintenance mode, a pivot, or fewer people working on it? The count looks the same for all three.
- measured A roadmap file is in the tree (ROADMAP.md, last changed July 2022). 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.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.
- 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 coverageNot rated: only 3 of 15 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
- 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 Dart codebase, with Rust alongside (26% of source files). Does your engineering organisation already run Dart in production, or would this be the first?
- The bulk of this system sits in frontend/, project.inlang/. 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/appflowy-io/appflowy/5cf3a36)If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
Rejection log — 91 signals that ran and did not fire
Appendix: rejection log — 91 signals that ran and did not fire
Published on purpose. A signal that looked and decided not to fire has told you something, and this is the calibration data behind every threshold above.
Looked, and found nothing — 53
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 27,220 · top5 share 0.02 |
| 04.debt_markers | debt markers are sparsemarkers 84 · per kloc 0.16 · lines read 511,076 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.133 · early test per code 0.116 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.685 · early delete per insert 0.772 |
| 04.fixes_with_tests | fixes usually come with a testfixes 560 · share 0.316 · with tests 177 |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 2,397 · compat files 0 |
| 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 3,289 |
| 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 monthsyears 5.0 · window last 24 months · authors 387 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 387 · active 12mo 12 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 387 · one off share 0.646 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 84 · window last 24 months · with tracked 1 |
| 02.ci_presence | CI configuration is present in the working treecount 13 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 444 · source 2,818 · test ratio 0.158 |
| 02.release_cadence | tags are presenttags 151 |
| 02.conventional_commits | commit subjects generally carry contentsampled 6,366 · low content share 0.009 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 13 · with tests 3 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 511 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 13 |
| 02.revert_share | change is rarely undoneshare 0.003 · reverts 5 · recent commits 1,459 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 1 · commits since 34 · days since lockfile changed 388 |
| 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 6 · ci configs 13 · product files 2,397 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.0 · merges 62 · long lived 0 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.05 · commits 1,311 · over 2000 lines 65 |
| 01.burst_import | the largest burst was translation files (97% of it), 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, a branch merged by a merge commit was reviewed as one piece, and an export or mirror tool dates history when it replays itlargest commits 145d1e5..13028c6 · bursts explained 2 · largest net added 6,455 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 212 · share of insertions 0.0001 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 17.11 · repeat share 0.07 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 3,117 · write once share 0.349 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0198 · product files 2,397 · distinct blocks 246,646 |
| 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 3,289 |
| 05.license_present | a licence file is presentfound True |
| 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 3 |
| 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.deprecations_lingering | few deprecations have outlived two yearsolder than two years 0 · files with deprecations 8 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 339 · added in two years 57 · removed within 60 days 8 |
| 04.ci_platforms_dropped | no platform was dropped from CI in the last two years |
| 04.repository_status | the README's first screen states no end, move or freezestatements 0 |
| 02.development_elsewhere | nothing says development happens elsewhereno pr statements 0 · mirror statements 0 · replayed commit share 0.0 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 0.0 · days since last tag 0 · commits last 90 days 1 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 30 · on branch 121 · tags in window 151 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
| 05.project_advisories | no published advisory affects the surveyed versionaffecting 0 · exploited 0 · advisories 0 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 38
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.dependency_sprawl | no recognised dependency manifest found |
| 04.eol_runtime | no pinned runtime version to check |
| 04.fix_share_trend | fewer than six busy quarters to compare |
| 04.schema_churn | columns, once added, stay |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.structured_logging | not assessed for Dart, the main language here: this check's patterns read other languages only |
| 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.knowledge_silos | too few substantial top-level directories to read ownership |
| 03.bus_factor_trend | fewer than three active years to compare |
| 01.swallowed_errors | not assessed for Dart, the main language here: this check's patterns read other languages only |
| 01.build_reproducibility | no product Dockerfile to 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.container_runs_as_root | no Dockerfile outside development, test and example paths |
| 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.shell_from_strings | not assessed for Dart, the main language here: this check's patterns read other languages only |
| 05.unsafe_deserialization | not assessed for Dart, the main language here: this check's patterns read other languages only |
| 05.tls_verification_off | not assessed for Dart, the main language here: this check's patterns read other languages only |
| 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_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 AP9A-BQ7J-VFHE at borehole.dev/verify.
The code commits to the 103 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/AP9ABQ7JVFHE?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-27 · shown | borehole 0.7.1 | 12 | adequate |
12 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 12 | strong |
| 2026-10-03 | borehole 0.7.12 | 12 | strong |
| 2026-10-03 | borehole 0.7.11 | 12 | strong |
| 2026-10-02 | borehole 0.7.10 | 12 | strong |
| 2026-10-01 | borehole 0.7.9 | 12 | adequate |
| 2026-09-30 | borehole 0.7.8 | 11 | adequate |
| 2026-09-29 | borehole 0.7.6 | 11 | adequate |
| 2026-09-28 | borehole 0.7.5 | 11 | adequate |
| 2026-09-27 | borehole 0.7.4 | 11 | adequate |
| 2026-09-27 | borehole 0.7.3 | 12 | adequate |
| 2026-09-27 | borehole 0.7.2 | 12 | adequate |
| 2026-09-26 | borehole 0.7.0 | 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 | authenticated: False |
| 10.2s | cloned the repository to a temporary directory | depth: full |
| 20.9s | read the git history | commits: 7210tracked files: 4597 |
| 149.3s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 149.3s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 182.3s | kept the facts, never the source, for re-reading under new checks | |
| 182.3s | deleting the working copy |
Total 182.3s ·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).