16aa482 · 2,507 commits · 1,705 files
Issued 2026-11-03
Apache-2.0 since 2022-05-01: open source; use, change and redistribution need only attribution. People was not rated.
99 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 30 July 2026.
- 05.60 Apache-2.0 since 2022-05-01: open source; use, change and redistribution need only attribution
- Words about people are today's: bands rather than exact shares, dates or day counts, and what the history measured rather than why.
- 3 findings from checks Borehole's calibration found wrong more often than right are no longer published.
- 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 1 credential-shaped match is 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 | adequate | |
| 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 |
- 8% 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,327 of 1,327 counted files
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑web/src/apis/v1/api-auto.d.ts is 1,726 lines, 29× this codebase's median file
adequateThe median source file here is 59 lines. 5 files exceed 1,000 lines, the largest being 1,726. 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 | web/src/apis/v1/api-auto.d.ts:1 — 1,726 lines (29× median) |
| line-count | server/src/function-template/function-template.service.ts:1 — 1,715 lines (29× median) |
| line-count | cli/template/global.d.ts:1 — 1,218 lines (20× median) |
| line-count | cli/src/api/v1/data-contracts.ts:1 — 1,111 lines (18× median) |
| line-count | web/src/apis/v1/apps.ts:1 — 1,073 lines (18× median) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Engineering Process & SDLC Maturity
02 · adequate · ratings ↑Tests cover a thin slice of the codebase
adequate83 test files against 944 source files (8.8%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| test-file-ratio | 83 test files / 944 source files |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Organization & Key-Person Risk
03 · 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. What a person adds here.
Product & Engineering Maturity
04 · strong · ratings ↑Node.js 20 is past end of life
adequateThe code is pinned to Node.js 20 (end of life 2026-04-30). None of these receives security fixes any more; the first stopped on 2026-04-30. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| runtimes/nodejs/Dockerfile | runtimes/nodejs/Dockerfile — Node.js 20, end of life 2026-04-30 |
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.
16 files still carry code deprecated more than two years ago
adequate16 files were marked deprecated over two years ago and still are, the oldest since Sep 2021. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| packages/database-proxy/src/proxy.ts | packages/database-proxy/src/proxy.ts — deprecated since Sep 2021 |
| packages/database-ql/src/regexp/index.ts | packages/database-ql/src/regexp/index.ts — deprecated since Oct 2021 |
| packages/database-ql/src/serverDate/index.ts | packages/database-ql/src/serverDate/index.ts — deprecated since Oct 2021 |
| packages/database-ql/src/query.ts | packages/database-ql/src/query.ts — deprecated since Oct 2021 |
| packages/database-proxy/src/types.ts | packages/database-proxy/src/types.ts — deprecated since Oct 2021 |
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 | server/Dockerfile — runs as root |
| no-USER-instruction | web/Dockerfile — runs as root |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
| packages/client-sdk/webpack.config.js | packages/client-sdk/webpack.config.js:10 — source maps in a production build |
| web/vite.config.ts | web/vite.config.ts:64 — source maps in a production build |
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 credential-shaped string exists in the history
adequateMatches for JWT were committed at some point across 2,404 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. 5 other matchs 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 | JWT 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.
2 environment files are committed
adequateweb/.env, web/.env.production are tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| web/.env | web/.env — committed environment file |
| web/.env.production | web/.env.production — committed environment file |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
The build runs third-party code it does not pin
adequate9 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. 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/build-sealos-cluster-image.yml | .github/workflows/build-sealos-cluster-image.yml:118 — action pinned by tag |
| .github/workflows/dockerize-runtime-exporter.yml | .github/workflows/dockerize-runtime-exporter.yml:75 — action pinned by tag |
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 shell commands built from strings
adequate5 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. 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.
| runtimes/nodejs/src/init.ts | runtimes/nodejs/src/init.ts:39 — command run through a shell |
| runtimes/nodejs/src/support/module-hot-reload.ts | runtimes/nodejs/src/support/module-hot-reload.ts:94 — command run through a shell |
| runtimes/nodejs/src/support/module-hot-reload.ts | runtimes/nodejs/src/support/module-hot-reload.ts:108 — command run through 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: BSD-3-Clause → SSPL-1.0 with additional terms (2021-08-27) → Apache-2.0 (2022-05-01)
adequateThe root licence changed 2 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".
| e1974c04e | LICENSE — BSD-3-Clause from 2021-08-19 |
| 23fc5cd70 | LICENSE — SSPL-1.0 with additional terms from 2021-08-27 |
| 458fca5ca | LICENSE — Apache-2.0 from 2022-05-01 |
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 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 1,138 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.
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
7 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 tree carries design documentation (docs/en/architecture.md). Does it match what the team believes today? Ask them to walk through it against the code.
- 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?
- Is that code finished, or abandoned, and who still knows how it works?
- 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.
- measured No threat model is in the tree of what looks like a running service. Does one exist elsewhere, and who owns it?
- measured Infrastructure code (build/charts/kube-prometheus-stack/Chart.yaml and 9 more) last changed 35 months before the newest commit, while 373 commits landed. Is the infrastructure now changed by hand? Compare the live account with the code.
- 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?
- measured Service-level objectives are defined in the tree (build/charts/kube-prometheus-stack/templates/prometheus/rules-1.14/kube-apiserver-slos.yaml). Are they met? The repository holds the target, not the measurement.
- Are the dashboards opened, the alerts acknowledged and the pages answered?
- 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 TypeScript codebase. Does your engineering organisation already run TypeScript in production, or would this be the first?
- The bulk of this system sits in packages/, web/, server/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (runtimes/nodejs/Dockerfile and 4 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/labring/laf/16aa482)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 — 87 signals that ran and did not fire
Appendix: rejection log — 87 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 — 58
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 8,271 · top5 share 0.031 |
| 04.debt_markers | debt markers are sparsemarkers 19 · per kloc 0.15 · lines read 123,588 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.163 · early delete per insert 0.647 |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 864 · compat files 0 |
| 04.dependency_redundancy | one library per job, mostly |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 20 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.telemetry_depth | the service is visible in more than one way |
| 06.correlation_ids | a request can be followed through the logstracing False · request id sites 34 |
| 06.error_reporting | an error reporter is initialisedinitialised 1 · config files 0 |
| 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 3 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.knowledge_silos | withheld: this check's result would describe one person |
| 03.drive_by_contributors | withheld: this check's result would describe one person |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 76 · window all history · with tracked 1 |
| 02.ci_presence | CI configuration is present in the working treecount 14 |
| 02.release_cadence | tags are presenttags 167 |
| 02.conventional_commits | commit subjects generally carry contentsampled 2,431 · low content share 0.04 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 14 · with tests 1 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 4 · test files 99 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 14 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 16 · commits since 0 · days since lockfile changed 0 |
| 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 14 · ci configs 14 · product files 864 |
| 01.burst_import | the largest burst was merged pull requests, each developed and reviewed on its own branch (100% of it), which explains the rate: translations arrive from a vendor in bulk, dependencies and generated code are committed whole, a merged pull request is dated when it merged, not when it was written, a branch merged by a merge commit was reviewed as one piece, and an export or mirror tool dates history when it replays itlargest commits 7ff4fbd..9c4a57a · bursts explained 1 · largest net added 2,404 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 1 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 17.97 · repeat share 0.059 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 995 · write once share 0.349 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0212 · product files 859 · distinct blocks 55,814 |
| 01.swallowed_errors | errors are rarely thrown awayloc 124,612 · files 8 · per kloc 0.1 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 4 |
| 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 1,138 |
| 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.sql_from_strings | no SQL is assembled from strings in product codefiles 0 · sites 0 · value interpolated 0 |
| 05.unsafe_deserialization | no code-executing deserialiser in product codesites 0 |
| 05.tls_verification_off | no TLS verification is switched off in product codefiles 0 · sites 0 · pinned instead 0 |
| 05.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.public_env_secret | only publishable values carry a public prefixnames 0 · sites 0 · not secrets 0 |
| 05.unsafe_html | raw HTML is rare, literal or sanitisedsites 3 |
| 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 335 · 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 22.0 · days since last tag 946 · commits last 90 days 0 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 1 · on branch 141 · tags in window 142 |
Could not conclude, or did not apply — 29
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.fixes_with_tests | too few fixes in 24 months to judge |
| 04.fix_share_trend | fewer than six busy quarters to compare |
| 04.schema_churn | no schema migrations to read |
| 06.print_logging | a frontend: console output is the browser's, not the server's |
| 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.release_markers | fewer than 100 commits in the last year |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.critical_path_ownership | withheld: this check's result would describe one person |
| 03.second_contributor_attrition | withheld: this check's result would describe one person |
| 03.bus_factor_trend | withheld: this check's result would describe one person |
| 03.joiners_and_leavers | withheld: this check's result would describe one person |
| 02.revert_share | too few recent commits to judge how often change is undone |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 02.commit_size | too few recent commits |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.outbound_timeouts | not assessed for TypeScript, the language the product is written in: this check's patterns read other languages only |
| 05.migration_reversibility | too few migrations to judge |
| 05.resource_limits | no Kubernetes workload manifests |
| 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 | one API version is served, or none |
| 05.advisory_record | record incomplete: no advisory against the project in the last 24 months; OSV npm laf-cli (an empty record for a package published here), OSV npm laf-client-sdk (an empty record for a package published here), OSV npm @lafjs/cloud (an empty record for a package published here), OSV npm database-proxy (an empty record for a package published here), OSV npm database-ql (an empty record for a package published here) did not answer |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited list |
Anyone can check this report against the authoritative record — click the stamp, or enter 6KTG-433G-YVAV 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/6KTG433GYVAV?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: 83.8authenticated: False |
| 9.6s | cloned the repository to a temporary directory | depth: full |
| 18.6s | read the git history | commits: 2507tracked files: 1705 |
| 160.8s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 160.8s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 227.1s | kept the facts, never the source, for re-reading under new checks | |
| 227.1s | deleting the working copy |
Total 227.1s ·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).