58920ae · 9,104 commits · 1,917 files
Issued 2026-11-07
Nothing significant. Questions worth asking about Security & Reliability Posture, Organization & Key-Person Risk.
106 checks ran across 6 assessable dimensions. None found a significant problem; 3 raised something worth a question. 12 findings, each with evidence. One dimension cannot be assessed without an acquirer. Last commit 9 October 2026.
- 05.60 Relicensed: GPL-3.0 → Apache-2.0 (2021-12-09) LICENSE
- 1 submodule(s) this survey does not read: vcpkg .gitmodules:1
- The file and line of 3 credential-shaped matches are withheld. File and line are shown to whoever GitHub says controls this repository, signed in, and to a buyer of this report.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | not assessable | |
| 07 | Fit with the Acquirer | not assessable |
- 4% 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
- deep scan blamed 1,915 of 1,916 counted files
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑bcos-executor/src/executor/TransactionExecutor.cpp is 2,999 lines, 28× this codebase's median file
adequateThe median source file here is 105 lines. 19 files exceed 1,050 lines, the largest being 2,999. 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 | bcos-executor/src/executor/TransactionExecutor.cpp:1 — 2,999 lines (28× median) |
| line-count | bcos-ledger/bcos-ledger/Ledger.cpp:1 — 2,397 lines (22× median) |
| line-count | bcos-pbft/bcos-pbft/pbft/engine/PBFTEngine.cpp:1 — 2,236 lines (21× median) |
| line-count | bcos-executor/src/executive/TransactionExecutive.cpp:1 — 2,189 lines (20× median) |
| line-count | bcos-tool/bcos-tool/NodeConfig.cpp:1 — 2,138 lines (20× 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 ↑Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| process-scaffolding | 1 of 5 markers present across 1,917 tracked 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.
Pinned dependencies have not moved in 13 months
adequateThe lockfile last changed 392 days before the newest commit, and 183 commits have landed since. Every security fix published upstream in that time is absent until someone updates it, and the longer the gap the larger and riskier that update becomes.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| git log -1 -- tools/archive-tool/archive-reader/Cargo.lock | tools/archive-tool/archive-reader/Cargo.lock last changed 2025-09-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.
Organization & Key-Person Risk
03 · adequate · ratings ↑Regular contributors fell from 7 to 3 in a year
adequate4 people who committed regularly the year before made no commits in the last year, and 1 new regular contributors arrived. Ask whether the work they did is still covered.
| regular contributors by year | 7 then 3; 4 stopped committing, 1 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.
The bus factor fell from 3 to 1
adequateYear by year, newest first, the number of people who wrote half the changes was 1, 1, 2, 3. The team narrowed to one person, which is a different risk from one that always was: the code does not say why.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| bus factor by year | 1, 1, 2, 3 |
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 ↑Fixes are 63% of recent work, up from 39%
adequateIn the last two quarters 63% of commits were fixes, against 39% in the quarters before. Rising fix work usually means quality debt is coming due, and it takes time that new work would have had.
| fix share by quarter | 55%, 71%, 91%, 33%, 14%, 24%, 37%, 31% |
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 1,917 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.
7 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| unpinned | tools/.ci/requirements.txt:1 — any version |
| unpinned | tools/.ci/requirements.txt:2 — any version |
| unpinned | tools/BcosBuilder/requirements.txt:1 — any version |
| unpinned | tools/BcosBuilder/requirements.txt:2 — any version |
| unpinned | tools/BcosBuilder/requirements.txt:3 — any version |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
3 credential-shaped strings exist in the history
adequateMatches for private key block were committed at some point across 6,738 commits examined. The files that held them are no longer in the working tree — but removal from a file is not removal from the history, and the history is what transfers with the asset. What matters is whether each was rotated after it was committed. The code cannot tell whether any of them is live, and that decides whether this matters: none sits in production configuration, and none is in a format its provider keeps for live keys. Is any of these live? Show that each was rotated after it was committed, and when.
A note that does not affect this rating: notes like it are common in well-run projects.
| history | 3 cited: private key block pattern added here |
| File and line are shown to whoever GitHub says controls this repository, signed in, and to a buyer of this report. |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
The build runs third-party code it does not pin
adequate12 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 1 step pipes a download straight into a shell. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
A note that does not affect this rating: notes like it are common in well-run projects.
| .github/workflows/coverage-comment.yml | .github/workflows/coverage-comment.yml:84 — action pinned by tag |
| .github/workflows/docker.yml | .github/workflows/docker.yml:25 — action pinned by tag |
| tools/.ci/Dockerfile | tools/.ci/Dockerfile:17 — 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.
Relicensed: GPL-3.0 → Apache-2.0 (2021-12-09)
adequateThe root licence changed 1 time(s). The last change widened rights. Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
A note that does not affect this rating: a licence change is a fact for the first screen, and only a narrowing of rights within two years of the surveyed commit costs "strong".
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 advisory against this project in the last 24 months
adequateThe newest was published on 2025-04-06. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 3.17.1. Answer lives in: the release you run, set against each fixed version.
A note that does not affect this rating: it describes the project's advisory record, and no advisory in it is known to affect the surveyed commit.
| CVE-2024-58131 | 2025-04-06: CVE-2024-58131 (moderate): FISCO BCOS 3.11.0 has an issue with synchronization of the transaction pool that can, for example, be observed when a malicious node (that has modified the code |
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 4 of 16 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
6 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 1,229 product files. Where does the design live, and who holds it?
- measured The repository pulls code in through git submodules (.gitmodules). A buyer receives pointers, not that code. Can every submodule be fetched without the team's credentials, and who owns each one?
- 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 52 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 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 4 of 16 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 C codebase, with C++ alongside (36% of source files). Does your engineering organisation already run C in production, or would this be the first?
- The bulk of this system sits in bcos-executor/, bcos-framework/, bcos-sdk/. 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/fisco-bcos/fisco-bcos/58920ae)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 — 94 signals that ran and did not fire
Appendix: rejection log — 94 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 — 54
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 5,164 · top5 share 0.033 |
| 04.debt_markers | debt markers are sparsemarkers 148 · per kloc 0.44 · lines read 332,907 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.467 · early test per code 0.284 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.608 · early delete per insert 0.86 |
| 04.fixes_with_tests | fixes usually come with a testfixes 185 · share 0.584 · with tests 108 |
| 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 1,845 |
| 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.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 8.1 · window last 24 months · authors 52 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 52 · active 12mo 6 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 52 · directories 37 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 52 · one off share 0.231 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 52 · top share less than a quarter · top contributor last committed more than a year ago |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 11 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 68 · window last 24 months · with tracked 0 |
| 02.ci_presence | CI configuration is present in the working treecount 5 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 474 · source 1,601 · test ratio 0.296 |
| 02.release_cadence | tags are presenttags 93 |
| 02.conventional_commits | commit subjects generally carry contentsampled 6,783 · low content share 0.045 |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 5 · with tests 1 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 534 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 5 |
| 02.revert_share | change is rarely undoneshare 0.0 · reverts 0 · recent commits 395 |
| 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 2 · ci configs 5 · product files 1,127 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.304 · merges 23 · long lived 7 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.009 · commits 347 · over 2000 lines 3 |
| 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 674 · share of insertions 0.0007 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 28.67 · repeat share 0.142 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 1,189 · write once share 0.132 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0066 · product files 1,127 · distinct blocks 120,361 |
| 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 1,845 |
| 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.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.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 Apache-2.0class permissive · license Apache-2.0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 11 · added in two years 0 · removed within 60 days 0 |
| 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 24.0 · days since last tag 53 · commits last 90 days 10 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 24 · on branch 61 · tags in window 85 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 40
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.dependency_sprawl | no dependency manifest of the product's own was found |
| 04.eol_runtime | no pinned runtime version to check |
| 04.schema_churn | no schema migrations to read |
| 04.compat_layers | a library, whose compatibility code is usually deliberate |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.structured_logging | not assessed for C or C++, the languages the product is written in: 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 |
| 01.swallowed_errors | not assessed for C or C++, the languages the product is written in: 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.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 C or C++, the languages the product is written in: this check's patterns read other languages only |
| 05.unsafe_deserialization | not assessed for C or C++, the languages the product is written in: this check's patterns read other languages only |
| 05.tls_verification_off | not assessed for C or C++, the languages the product is written in: this check's patterns read other languages only |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.known_vulnerabilities | not assessed for C and C++ package managers, Gradle: this survey does not read their dependency files |
| 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_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 |
| 04.deprecations_lingering | a library, which keeps deprecated interfaces for its users |
| 05.project_advisories | could not tell whether 1 published advisory affects the surveyed code: its version could not be placed |
Anyone can check this report against the authoritative record — click the stamp, or enter Y8NS-DRTY-DMCC 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/Y8NSDRTYDMCC?via=badge)
5 pieces of evidence on this report quote the repository directly. Four checks quote text: up to five TODO-style comments, up to four commit subjects, up to five unpinned dependency lines and one status line from the README's first screen, such as “no longer maintained”. In each case the text is the evidence, which is why it is kept by default.
This rewrites every stored reading of this repository, and every later reading, including a re-read, is stored without the quoted text. The facts we keep to re-read it still hold the lines, as the privacy notice says. The pointers stay.
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-11-07 · shown | borehole 0.7.16 | 12 | adequate |
1 earlier (show)
| 2026-11-03 | borehole 0.7.15 | 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: 317.7authenticated: False |
| 12.0s | cloned the repository to a temporary directory | depth: full |
| 20.1s | read the git history | commits: 9104tracked files: 1917 |
| 92.5s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 92.6s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 121.5s | kept the facts, never the source, for re-reading under new checks | |
| 121.5s | deleting the working copy |
Total 121.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).