8c15222 · 10,902 commits · 3,886 files
Issued 2026-11-03
Nothing significant. Questions worth asking about Security & Reliability Posture, Observability & Operations. People was not rated.
101 checks ran across 6 assessable dimensions. None found a significant problem; 2 raised something worth a question. 12 findings, each with evidence. One dimension cannot be assessed without an acquirer. Last commit 30 October 2026.
- 04.62 Releases are cut from another branch than the one surveyed
- 05.60 Relicensed: EULA → Apache-2.0 (2017-05-06) LICENSE.md
- names Linux Foundation CONTRIBUTING.md:16
- 1 finding from checks Borehole's calibration found wrong more often than right is no longer published.
- 4 findings about one contributor are withheld: one author wrote nearly all of this repository's commits; a buyer of this report reads them.
- The file and line of 5 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 | not assessable | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 12% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- 54% of commits show author/committer date divergence, which is the shape of replayed history that can drop trailers
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑java/calcite/src/main/java/org/apache/calcite/sql/validate/SqlValidatorImpl.java is 8,343 lines, 79× this codebase's median file
adequateThe median source file here is 105 lines. 92 files exceed 1,050 lines, the largest being 8,343. 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 | java/calcite/src/main/java/org/apache/calcite/sql/validate/SqlValidatorImpl.java:1 — 8,343 lines (79× median) |
| line-count | ThriftHandler/DBHandler.cpp:1 — 7,946 lines (75× median) |
| line-count | Catalog/Catalog.cpp:1 — 7,650 lines (72× median) |
| line-count | Parser/ParserNode.cpp:1 — 7,389 lines (70× median) |
| line-count | java/calcite/src/main/java/org/apache/calcite/sql2rel/SqlToRelConverter.java:1 — 6,820 lines (64× 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 · not assessable · ratings ↑Not rated: one author wrote nearly all of this repository's commits, so a finding about one contributor would be about someone its history all but names; the public report does not carry those, and does not rate this dimension without them. The findings below are what it could still read.
Regular contributors fell from 12 to 2 in a year
adequate11 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 | 12 then 2; 11 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.
Product & Engineering Maturity
04 · strong · ratings ↑Releases are cut from another branch than the one surveyed
adequateThe newest release, v10.0.0, is not on the branch this survey read; the newest release on it is v9.0.0. The shipped product may differ from what this report describes. Survey the release branch too.
A note that does not affect this rating: notes like it are common in well-run projects.
| 39952e6c2 | tag v10.0.0 |
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 ↑2 Dockerfiles run 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 | docker/internal/odbc-fsi-deployment/Dockerfile — runs as root |
| no-USER-instruction | docker/internal/odbc-fsi-dev/hive/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.
15 credential-shaped strings added in the history sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key. 1 other match set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
A note that does not affect this rating: notes like it are common in well-run projects.
| history | 3 cited: private key block, where fakes are usual |
| history | 2 cited: JWT, where fakes are usual |
| 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.
1 SQL statement built from strings
adequate1 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| java/utility/src/main/java/com/mapd/utility/db_vendors/Db_vendor_types.java | java/utility/src/main/java/com/mapd/utility/db_vendors/Db_vendor_types.java:208 — SQL built from a string |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
5 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| ThirdParty/LruCache | ThirdParty/LruCache — 1 tracked files, no licence file |
| ThirdParty/earcut | ThirdParty/earcut — 1 tracked files, no licence file |
| ThirdParty/geo_samples | ThirdParty/geo_samples — 2 tracked files, no licence file |
| ThirdParty/linenoise | ThirdParty/linenoise — 7 tracked files, no licence file |
| ThirdParty/vulkan | ThirdParty/vulkan — 1 tracked files, no licence file |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Relicensed: EULA → Apache-2.0 (2017-05-06)
adequateThe root licence changed 1 time(s). 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".
| decae5659 | LICENSE.md — EULA from 2016-09-29 |
| 4fe8668fe | LICENSE.md — Apache-2.0 from 2017-05-06 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Observability & Operations
06 · adequate · ratings ↑No telemetry or error reporting is wired in anywhere
adequateNone of 2,935 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| telemetry-scan | searched 2,935 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
No structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| logging-scan | C source is not searched: C programs log through printf-style calls unless they take a library, and none of the 10 searched for is referenced |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
A note that does not affect this rating: notes like it are common in well-run projects.
| error reporting | no error reporter initialised |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
3 of 3 deployed images carry no version, or `latest`
adequate3 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| dev-tools/docker-compose.yml | dev-tools/docker-compose.yml:7 — image without a version |
| docker/internal/odbc-fsi-dev/docker-compose.yml | docker/internal/odbc-fsi-dev/docker-compose.yml:26 — image without a version |
| docker/internal/odbc-fsi-dev/docker-compose.yml | docker/internal/odbc-fsi-dev/docker-compose.yml:34 — image without a 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.
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
9 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 2,396 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 coverageNot rated: one author wrote nearly all of this repository's commits, so a finding about one contributor would be about someone its history all but names; the public report does not carry those, and does not rate this dimension without them.
- Which of the people who wrote this are part of the transaction, and for how long after it?
- 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 25 commits landed in the last year, against 352 the year before (-93%). 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 September 2026). 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.
- measured No threat model is in the tree of what looks like a running service. Does one exist elsewhere, and who owns it?
- What has actually broken, how often, and how badly?
- What did external testing find, and was it fixed?
- What is the SOC 2, ISO 27001 or GDPR status, and where is the evidence?
Observability & Operations
06 · partial coverage- measured Nothing in the tree backs up or restores data. How is data backed up, and has a restore ever been rehearsed?
- measured No alert rule is defined in the repository. Where are alerts defined, who receives them, and when did one last fire?
- Are the dashboards opened, the alerts acknowledged and the pages answered?
- Are the service-level objectives actually met?
- Who carries the pager, and how often does it go off?
- What does it cost to run, and how much headroom is there?
Fit with the Acquirer
07 · none coverageNot rated: structurally not assessable from a repository.
- This is primarily a C codebase, with C++ alongside (37% 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 ThirdParty/, QueryEngine/, DataMgr/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (dev-tools/docker-compose.yml and 8 more). 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/heavyai/heavydb/8c15222)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 — 89 signals that ran and did not fire
Appendix: rejection log — 89 signals that ran and did not fire
Published on purpose. A signal that looked and decided not to fire has told you something, and this is the calibration data behind every threshold above.
Looked, and found nothing — 56
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 10,144 · top5 share 0.087 |
| 04.debt_markers | debt markers are sparsemarkers 1,308 · per kloc 1.51 · lines read 866,626 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.227 · early test per code 0.099 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.524 · early delete per insert 0.534 |
| 04.fixes_with_tests | fixes usually come with a testfixes 70 · share 0.571 · with tests 40 |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 2,131 · compat files 0 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 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.active_contributors | withheld: this check's result would describe one person |
| 03.drive_by_contributors | withheld: this check's result would describe one person |
| 03.critical_path_ownership | withheld: this check's result would describe one person |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 0 |
| 02.ci_presence | CI configuration is present in the working treecount 13 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 319 · source 2,449 · test ratio 0.13 |
| 02.release_cadence | tags are presenttags 68 |
| 02.conventional_commits | commit subjects generally carry contentsampled 10,711 · low content share 0.004 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 13 · with tests 4 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 4 · test files 1,302 |
| 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.005 · reverts 2 · recent commits 377 |
| 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 7 · ci configs 13 · product files 2,131 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.041 · commits 344 · over 2000 lines 14 |
| 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 25 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 26.07 · repeat share 0.024 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 2,299 · write once share 0.465 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0064 · product files 1,889 · distinct blocks 372,862 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 2 |
| 01.unfinished_migration | no language migration is stalled halfway |
| 01.weights_in_git | no model weights are committedfiles 0 |
| 05.committed_secrets | no credential-shaped strings outside test and fixture pathsnote the working tree only; the history is 05.5 · patterns 8 · files read 2,935 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.dependency_pinning | dependencies are substantially pinnedunpinned 3 |
| 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 76 · pipe to shell 0 · unpinned third party 1 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 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 408 |
| 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.api_versions_coexisting | one API version is served, or none |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 3 · files with deprecations 12 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 26 · added in two years 2 · 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 56.0 · days since last tag 25 · commits last 90 days 25 |
| 03.single_maintainer | withheld: this check's result would describe one person |
| 05.project_advisories | no published advisory affects the surveyed versionaffecting 0 · exploited 0 · advisories 0 |
| 05.advisory_record | no advisory against the project in the last 24 monthscritical 0 · affecting 0 · could not tell 0 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 33
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.fix_share_trend | fewer than six busy quarters to compare |
| 04.schema_churn | no schema migrations to read |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.telemetry_depth | none at all is 06.1 |
| 06.print_logging | not assessed for C: its logger calls are not read |
| 06.correlation_ids | not assessed for C or C++, the languages the product is written in: this check's patterns read other languages only |
| 06.alert_rules | no alert rules in the repository; they may live in a console |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.environment_branching | not assessed for C or C++, the languages the product is written in: this check's patterns read other languages only |
| 06.release_markers | fewer than 100 commits in the last year |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.bus_factor_trend | withheld: this check's result would describe one person |
| 02.dependency_update_cadence | no lockfile to date |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 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.notebook_outputs | not a data or machine-learning repository |
| 05.outbound_timeouts | not assessed for C or C++, the languages the product is written in: this check's patterns read other languages only |
| 05.migration_reversibility | too few migrations to judge |
| 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 Maven: 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_manifest_conflict | no packaging manifest states a licence |
| 04.flags_accumulating | few or no feature flags in the history |
Anyone can check this report against the authoritative record — click the stamp, or enter W6AQ-3FBY-MS0V 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/W6AQ3FBYMS0V?via=badge)
Where this scan ran
This scan ran on ordinary cloud infrastructure (cloud-run), not in a hardware-isolated confidential VM. Nothing about it is attested by Google.
What an attested survey proves, and what it does not.
What this scan did with the repository — 7 steps
Written by the steps themselves as they ran, not described afterwards. A hand-written account of a data flow drifts the first time somebody changes the flow and not the account.
| At | Step | Detail |
|---|---|---|
| 0.0s | read repository metadata from the GitHub API | size mb: 101.0authenticated: False |
| 26.8s | cloned the repository to a temporary directory | depth: full |
| 52.5s | read the git history | commits: 10902tracked files: 3886 |
| 160.4s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 160.4s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 248.8s | kept the facts, never the source, for re-reading under new checks | |
| 248.8s | deleting the working copy |
Total 248.8s ·source content sent off this machine: none · calls to a language model: 0 · the clone was deleted when the survey ended
An automated reading of a repository's code and its history up to one commit, with public advisory records. It may be wrong, it is not legal, financial, investment or security advice, and it does not replace diligence by a qualified person. It is provided for information: nobody may rely on it (Borehole's terms, section 3).