b415df8 · 653 commits · 320 files
Issued 2026-10-23
Nothing significant. Questions worth asking about Security & Reliability Posture, Architecture & Codebase — including AI provenance.
104 checks ran across 6 assessable dimensions. 1 finding is worth checking first. 12 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 6 submodule(s) this survey does not read: packages/leann-backend-diskann/third_party/DiskANN, packages/leann-backend-hnsw/third_party/faiss, packages/leann-backend-hnsw/third_party/msgpack-c .gitmodules:1
Borehole's proprietary scoring is calibrated across hundreds of repositories. Each finding here reads significant, but its check has not yet held up often enough in that calibration to rate significant on its own. If one holds when someone checks it, it is significant.
- 05.26 28 locked dependencies have published vulnerabilities, 47 high or critical in what ships
- 2 findings from checks Borehole's calibration found wrong more often than right are no longer published.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | adequate | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 16% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- no widespread author/committer date divergence
- the declared share is neither decisive nor negligible, so the true figure is more sensitive to undeclared work
- deep scan blamed 310 of 311 counted files
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑The repository begins with most of itself already written
adequateThe first commit carries 278,432 lines — 56% of every line ever added. Whatever happened before that commit happened somewhere this repository cannot show you, so the early history is not available as evidence of how the system was designed.
| 46f6cc1 | 2025-06-30T09:05:05+00:00; +278,432 across 1231 files; subject: 'Initial commit' |
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.
packages/leann-core/src/leann/cli.py is 4,026 lines, 21× this codebase's median file
adequateThe median source file here is 184 lines. 2 files exceed 1,840 lines, the largest being 4,026. 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 | packages/leann-core/src/leann/cli.py:1 — 4,026 lines (21× median) |
| line-count | packages/leann-core/src/leann/api.py:1 — 1,878 lines (10× 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.
68 errors caught and discarded in product code
adequate68 places catch an error and do nothing with it, across 20 files (1.1 per thousand lines). Each is a failure the system will not report. They surface later as problems nobody can explain, and they are cheap to fix now.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| apps/base_rag_example.py | apps/base_rag_example.py:365 — error caught and discarded |
| apps/document_rag.py | apps/document_rag.py:49 — error caught and discarded |
| apps/document_rag.py | apps/document_rag.py:63 — error caught and discarded |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Engineering Process & SDLC Maturity
02 · adequate · ratings ↑No finding. 16 checks ran and none fired; the rejection log below says why each did not.
Organization & Key-Person Risk
03 · adequate · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · adequate · ratings ↑Fixes are 52% of recent work, up from 33%
adequateIn the last two quarters 52% of commits were fixes, against 33% 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 | 57%, 48%, 40%, 27%, 38%, 25% |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Security & Reliability Posture
05 · adequate · ratings ↑1 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
| no-USER-instruction | docker/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.
28 locked dependencies have published vulnerabilities, 47 high or critical in what ships
adequate worth checking first28 of 242 locked dependencies match 120 published advisories in OSV, 49 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.
The check that found this reads significant, but it has not yet held up often enough in Borehole's calibration to rate a finding significant on its own. Opening uv.lock settles it. If it holds when someone checks it, this finding is significant.
| uv.lock | uv.lock — anyio 4.11.0: GHSA-82r6-8w77-94w6 (critical), fixed in 4.14.2 |
| uv.lock | uv.lock — certifi 2025.8.3: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.19 |
| uv.lock | uv.lock — nltk 3.9.1: GHSA-7p94-766c-hgjp (critical), fixed in 3.9.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.
6 outbound calls can wait forever
adequate6 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| packages/leann-core/src/leann/chat.py | packages/leann-core/src/leann/chat.py:484 — outbound call without a timeout |
| packages/leann-core/src/leann/web_search.py | packages/leann-core/src/leann/web_search.py:29 — outbound call without a timeout |
| packages/leann-core/src/leann/web_search.py | packages/leann-core/src/leann/web_search.py:60 — outbound call without a timeout |
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.
6 deserialisers that can run code
adequate6 places read data with a deserialiser that executes what it reads (pickle). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| packages/leann-core/src/leann/api.py | packages/leann-core/src/leann/api.py:242 — code-executing deserialiser |
| packages/leann-core/src/leann/api.py | packages/leann-core/src/leann/api.py:854 — code-executing deserialiser |
| packages/leann-core/src/leann/api.py | packages/leann-core/src/leann/api.py:924 — code-executing deserialiser |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
2 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| packages/leann-backend-diskann/third_party/embedding.pb.cc | packages/leann-backend-diskann/third_party/embedding.pb.cc — 1 tracked files, no licence file |
| packages/leann-backend-diskann/third_party/embedding.proto | packages/leann-backend-diskann/third_party/embedding.proto — 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.
Observability & Operations
06 · adequate · ratings ↑No telemetry or error reporting is wired in anywhere
adequateNone of 278 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 278 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 | searched 278 files for 10 structured logging libraries; 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 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.
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 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 63 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 A roadmap file is in the tree (docs/roadmap.md, last changed March 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?
- measured No experiment tracking is configured in the repository. How was the shipped model trained and evaluated, and could it be reproduced?
- measured No model card is in the tree. What is the model's intended use, what was it trained on, and where does it fail?
- 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 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 Python codebase. Does your engineering organisation already run Python in production, or would this be the first?
- The bulk of this system sits in packages/, apps/, data/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (docker/Dockerfile and 2 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/startrail-org/leann/b415df8)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 — 92 signals that ran and did not fire
Appendix: rejection log — 92 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 — 72
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 1,591 · top5 share 0.109 |
| 04.debt_markers | debt markers are sparsemarkers 12 · per kloc 0.19 · lines read 64,303 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.533 · early test per code 0.175 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.391 · early delete per insert 0.512 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fixes_with_tests | fixes usually come with a testfixes 215 · share 0.2 · with tests 43 |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 92 · compat files 0 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.print_logging | raw prints are few, or outnumbered by logger callsprints 799 · logger calls 352 |
| 06.correlation_ids | a request can be followed through the logstracing False · request id sites 1 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 4 · release commits 1 · changelog commits 12 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 1.3 · window last 24 months · authors 63 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 63 · active 12mo 55 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 63 · directories 5 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 63 · one off share 0.635 |
| 03.contributor_attrition | the dominant contributor is still activeauthors 63 · top share a quarter or more · top contributor last committed between three and six months ago |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 63 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.joiners_and_leavers | the team is not shrinkingleft 0 · joined 10 · regular last year 15 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 48 · window last 24 months · with tracked 19 |
| 02.ci_presence | CI configuration is present in the working treecount 4 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 62 · source 152 · test ratio 0.408 |
| 02.release_cadence | tags are presenttags 31 |
| 02.conventional_commits | commit subjects generally carry contentsampled 605 · low content share 0.089 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 4 · with tests 1 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 1 · test files 69 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 4 |
| 02.revert_share | change is rarely undoneshare 0.005 · reverts 3 · recent commits 605 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 1 · commits since 43 · days since lockfile changed 84 |
| 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 3 · ci configs 4 · product files 92 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.042 · commits 527 · over 2000 lines 22 |
| 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.message_uniformity | commit subjects vary in wording and lengthlength stdev 23.48 · repeat share 0.099 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 142 · write once share 0.444 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 1 |
| 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 paths; the only other matches are expired or licence tokens or placeholders, which grant nothingnote the working tree only; the history is 05.5 · patterns 8 · files read 278 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.dependency_pinning | a lockfile is committed, so builds are reproduciblelockfile True |
| 05.license_present | a licence file is presentfound True |
| 05.secrets_in_history | no credential-shaped string was ever added outside test and fixture paths; the only other matches are expired or licence tokens or placeholders, which grant nothingpatterns 8 · truncated False · added lines 434,506 |
| 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 14 · pipe to shell 0 · unpinned third party 2 |
| 05.sql_from_strings | no SQL is assembled from strings in product codefiles 0 · sites 0 · value interpolated 0 |
| 05.shell_from_strings | product code does not build shell commands from stringssites 1 |
| 05.tls_verification_off | no TLS verification is switched off in product codefiles 0 · sites 0 · pinned instead 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · 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.dataset_provenance | data files carry a licence or carddata files 0 · licence or card files 1 |
| 05.license_copyleft_inherited | every licence found in vendored code is permissive or weak-copyleftvendored paths 7 |
| 05.license_grant_unclear | the licence is recognisable as MITclass permissive · license MIT |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 0 · files with deprecations 2 |
| 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.licence_changes | the root licence has not changed in the history readlicence versions 1 · unreleased changes 0 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 8.5 · days since last tag 27 · commits last 90 days 44 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 0 · on branch 31 · tags in window 31 |
| 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.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 — 20
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 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.alert_rules | no alert rules in the repository; they may live in a console |
| 06.deployed_image_floats | no deployment descriptor names an image |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.bus_factor_trend | fewer than three active years to compare |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.notebook_outputs | too few notebooks |
| 05.migration_reversibility | too few migrations to judge |
| 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.cleartext_traffic | not a mobile app |
| 05.license_manifest_conflict | no packaging manifest states a licence |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | one API version is served, or none |
Anyone can check this report against the authoritative record — click the stamp, or enter WM4S-SAEY-MFAT 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/WM4SSAEYMFAT?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: 82.4authenticated: False |
| 4.7s | cloned the repository to a temporary directory | depth: full |
| 7.2s | read the git history | commits: 653tracked files: 320 |
| 70.2s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 70.2s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 93.4s | kept the facts, never the source, for re-reading under new checks | |
| 93.4s | deleting the working copy |
Total 93.4s ·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).