087d6c4 · 5,095 commits · 5,980 files
Issued 2026-11-03
Significant: one contributor carries the recent work.
1 of 6 assessable dimensions carries significant findings, 4 are adequate and 1 is strong. 17 findings, each with its evidence: the commit, path and lines it rests on, or, when something is missing, what was looked for. One dimension cannot be assessed without an acquirer. Last commit 3 November 2026.
- 03.1 Significant: Bus factor 1: recent work is concentrated in one contributor
- 05.61 Part of the code is under a separate licence: ee/ ee/LICENSE
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 03 | Organization & Key-Person Risk | significant findings | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 56% of non-merge commits carry any trailer at all
- no widespread author/committer date divergence
- the declared share is neither decisive nor negligible, so the true figure is more sensitive to undeclared work
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑apps/api/src/routes/admin.ts is 20,498 lines, 189× this codebase's median file
adequateThe median source file here is 108 lines. 96 files exceed 1,080 lines, the largest being 20,498. 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. Measured against its own codebase's median, it is larger than 90% of 382 surveyed projects' largest files.
A note that does not affect this rating: notes like it are common in well-run projects.
| line-count | apps/api/src/routes/admin.ts:1 — 20,498 lines (189× median) |
| line-count | apps/gateway/src/chat/chat.ts:1 — 16,376 lines (151× median) |
| line-count | packages/db/src/schema.ts:1 — 8,156 lines (75× median) |
| line-count | apps/gateway/src/videos/videos.ts:1 — 6,067 lines (56× median) |
| line-count | apps/api/src/stripe.ts:1 — 5,952 lines (55× 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 ↑9% of recent commits change more than 2,000 lines
adequate393 of 4457 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| git log --numstat | 393 commits over 2,000 lines |
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.
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/actions/src/prepare-request-body.spec.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
A note that does not affect this rating: notes like it are common in well-run projects.
| packages/actions/src/prepare-request-body.spec.ts | packages/actions/src/prepare-request-body.spec.ts:5749 — test retry |
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 · significant findings · ratings ↑Bus factor 1: recent work is concentrated in one contributor
significant findingsIn the last 24 months, one contributor authored more than half of 4,694 non-merge commits among 36 authors; across all history, more than half of 4,694. This is the single most expensive thing to discover after closing, and the repository cannot tell you whether that person is part of the transaction.
| git shortlog -sn | last 24 months: top author more than half of 4,694 commits; bus factor 1; 36 authors |
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 of 7 major areas has only ever had one author
adequateAcross 36 contributors, 1 substantial top-level area has been touched by exactly one person. The headline bus factor does not show this: a team can look well spread in aggregate and still have subsystems that stop moving the day one person stops working on them. For these areas, ask who else can change them today.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| sole-author | sql/ — 544 lines added |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Product & Engineering Maturity
04 · adequate · ratings ↑81 direct dependencies in a single manifest
adequateapps/ui/package.json declares 81 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
| direct-dependencies | apps/ui/package.json — 81 declared |
| direct-dependencies | ee/admin/package.json — 53 declared |
| direct-dependencies | apps/api/package.json — 50 declared |
| direct-dependencies | apps/code/package.json — 50 declared |
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 ↑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.
| apps/airside/next.config.ts | apps/airside/next.config.ts:10 — source maps in a production build |
| apps/code/next.config.ts | apps/code/next.config.ts:12 — source maps in a production build |
| apps/ui/next.config.ts | apps/ui/next.config.ts:17 — 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.
Licence text does not match a standard licence
adequateLICENSE exists but its text does not match any standard licence. A bespoke or hand-edited licence is not wrong, but it cannot be cleared by recognising its name: counsel has to read it, and until they do neither side knows precisely what rights transfer with the code.
| LICENSE | LICENSE:1 — 9 lines, unrecognised |
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.
Part of the code is under a separate licence: ee/
adequateA directory named for a paid edition carries its own licence. That code is usually not open source even where the rest is; what the buyer may do with each part differs.
| ee/LICENSE | ee/LICENSE — licence: unrecognised |
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
adequate10 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/autofix.yml | .github/workflows/autofix.yml:20 — action pinned by tag |
| .github/workflows/autofix.yml | .github/workflows/autofix.yml:25 — 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.
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.
| packages/db/src/migrate.ts | packages/db/src/migrate.ts:398 — 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.
3 locked dependencies have published vulnerabilities
adequate3 of 2,622 locked dependencies match 3 published advisories in OSV. 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.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| pnpm-lock.yaml | pnpm-lock.yaml — minimatch 3.1.5: GHSA-g3hv-75wg-m249 (moderate), fixed in 11.0.1 |
| pnpm-lock.yaml | pnpm-lock.yaml — minimatch 5.1.9: GHSA-g3hv-75wg-m249 (moderate), fixed in 11.0.1 |
| pnpm-lock.yaml | pnpm-lock.yaml — deepmerge 4.3.1: GHSA-gcqx-w48m-w2h4 (low) |
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.
56 places insert HTML from a variable without sanitising it
adequate56 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| apps/airside/src/app/resources/page.tsx | apps/airside/src/app/resources/page.tsx:72 — HTML from a variable |
| apps/airside/src/components/ResourcePage.tsx | apps/airside/src/components/ResourcePage.tsx:74 — HTML from a variable |
| apps/code/src/app/claude-code-alternative/page.tsx | apps/code/src/app/claude-code-alternative/page.tsx:163 — HTML from a variable |
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.
18 advisories against this project in the last 24 months, 9 high or critical
adequateThe newest was published on 2026-10-22. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 2 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 1.24.0. Answer lives in: the release you run, set against each fixed version.
A note that does not affect this rating: it describes the project's advisory record, and no advisory in it is known to affect the surveyed commit.
| GHSA-33vh-h489-26cq | 2026-10-22: GHSA-33vh-h489-26cq (moderate), fixed in 31d7199 (#4775): DNS-rebinding SSRF in video generation endpoints: tenant base-URL guard not applied |
| CVE-2026-108719 | 2026-10-11: CVE-2026-108719 (moderate): LLMGateway through 1.20.0 contains a blind server-side request forgery vulnerability that allows API key holders to reach internal hosts via the video-generatio |
| GHSA-jv5c-wm2x-qxj6 | 2026-09-12: GHSA-jv5c-wm2x-qxj6 (low): Password updates returned server errors for invalid input |
| GHSA-w845-x732-gj6p | 2026-09-12: GHSA-w845-x732-gj6p (low): Chat sharing defaulted to public visibility and allowed copying |
| GHSA-v789-xg97-vg68 | 2026-09-12: GHSA-v789-xg97-vg68 (low): Organization member responses disclosed account registration |
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 ↑Readiness and liveness probes are identical in 6 of 11 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
| infra/helm/llmgateway/templates/admin-deployment.yaml | infra/helm/llmgateway/templates/admin-deployment.yaml — same probe endpoint twice |
| infra/helm/llmgateway/templates/airside-deployment.yaml | infra/helm/llmgateway/templates/airside-deployment.yaml — same probe endpoint twice |
| infra/helm/llmgateway/templates/code-deployment.yaml | infra/helm/llmgateway/templates/code-deployment.yaml — same probe endpoint twice |
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 12 deployments run a single replica
adequate3 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| infra/helm/llmgateway/templates/postgresql-statefulset.yaml | infra/helm/llmgateway/templates/postgresql-statefulset.yaml — replicas: 1 |
| infra/helm/llmgateway/templates/redis-statefulset.yaml | infra/helm/llmgateway/templates/redis-statefulset.yaml — replicas: 1 |
| infra/helm/llmgateway/templates/storage-redis-statefulset.yaml | infra/helm/llmgateway/templates/storage-redis-statefulset.yaml — replicas: 1 |
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 code branches on the environment's name at 26 places
adequate26 places outside configuration test whether they are running in production or staging. Staging then does not exercise production's code, and each deploy is the first run of those branches. Differences belong in configuration the code reads, not in the code.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| apps/api/src/routes/referral.ts | apps/api/src/routes/referral.ts:12 — branch on the environment name |
| apps/api/src/routes/referral.ts | apps/api/src/routes/referral.ts:62 — branch on the environment name |
| apps/gateway/src/images/images.ts | apps/gateway/src/images/images.ts:1256 — branch on the environment name |
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
5 checks against the running system follow from the findings above: what a buyer's engineer will try, how to run it first, and what to have ready. A paid survey of this repository includes them.
A paid survey of a public repository is also reviewed: a language model reads each finding against the code and withdraws only findings it judges the code contradicts, each listed with its reason. The review is a language model's reading of the findings against the code, and it can be wrong. It never adds a finding, never raises a band, and never removes a finding from a proven check or an advisory that affects the surveyed version.
What a person adds
The survey reads what the repository can show. The code cannot settle these questions, and on them this report states nothing. Each says where its answer lives: your own engineer, the company, or an assessor you choose can settle it. Questions marked measured open with something this repository shows.
Architecture & Codebase — including AI provenance
01 · full coverage- measured No architecture or design document is in the tree, across 4,094 product files. Where does the design live, and who holds it?
- Is the architecture right for the next three years of the product?
- Were the home-grown components reasonable choices when they were made, and are they now?
Engineering Process & SDLC Maturity
02 · high coverage- Is review real or a rubber stamp? Comment depth and time to approve need the pull request history.
- Is delivery planned and measured, or heroic?
- How are incidents run, reviewed and learned from?
Organization & Key-Person Risk
03 · partial coverage- measured One contributor authored more than half of the commits in this history. Is that person 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- 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 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 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/, apps/, ee/. Which of your existing systems would each of those have to absorb or replace?
- 64% of added lines came through AI-declared commits. Does your organisation have a policy on inheriting and maintaining that code, and does your engineering team's tooling match how it was produced?
- The repository carries deployment configuration (docker-compose.yml and 35 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/theopenco/llmgateway/087d6c4)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 — 74
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 7,886 · top5 share 0.056 |
| 04.debt_markers | debt markers are sparsemarkers 4 · per kloc 0.0 · lines read 2,601,632 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.331 · early test per code 0.05 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.303 · early delete per insert 0.289 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fixes_with_tests | fixes usually come with a testfixes 1,788 · share 0.385 · with tests 689 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.schema_churn | columns, once added, staydropped within 90 days 22 · columns added last year 687 |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 2,662 · 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 81 |
| 06.structured_logging | a structured logging library is referencedmatches 2 |
| 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 True · request id sites 90 |
| 06.error_reporting | an error reporter is initialisedinitialised 0 · config files 6 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 1 |
| 06.deployed_image_floats | every deployed image names a versionimages 3 · floating 0 |
| 06.release_markers | releases are markedtags last year 620 · release commits 0 · changelog commits 6 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.active_contributors | more than one contributor active in the trailing yearall time 36 · active 12mo 30 |
| 03.drive_by_contributors | a healthy share of contributors committed more than onceshare 0.5 · authors 36 · one commit authors 18 |
| 03.contributor_attrition | the dominant contributor is still activeauthors 36 · top share more than half · top contributor last committed within the last three months |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 36 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 4 · window last 24 months · with tracked 19 |
| 02.ci_presence | CI configuration is present in the working treecount 14 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 810 · source 3,472 · test ratio 0.233 |
| 02.release_cadence | tags are presenttags 623 |
| 02.conventional_commits | commit subjects generally carry contentsampled 5,091 · low content share 0.0 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 14 · with tests 4 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 4 · test files 893 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 14 |
| 02.revert_share | change is rarely undoneshare 0.003 · reverts 16 · recent commits 4,694 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 1 · commits since 2 · days since lockfile changed 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 42 · ci configs 14 · product files 2,662 |
| 01.burst_import | the largest burst was data and assets (96% 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 7acf631..6c36454 · bursts explained 1 · largest net added 44,103 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 4,312 · share of insertions 0.0004 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 10.54 · repeat share 0.005 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 3,450 · write once share 0.442 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0279 · product files 2,662 · distinct blocks 437,257 |
| 01.swallowed_errors | errors are rarely thrown awayloc 2,605,977 · files 2 · per kloc 0.0 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 24 |
| 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 4,794 |
| 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 pathspatterns 8 · truncated False · added lines 11,005,439 |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.shell_from_strings | product code does not build shell commands from stringssites 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.resource_limits | every workload declares limitsworkloads 12 · without limits 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.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.cleartext_traffic | plain HTTP is not allowed app-widesites 0 |
| 05.license_copyleft_inherited | every licence found in vendored code is permissive or weak-copyleftvendored paths 2 |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.api_versions_coexisting | the newer API version is recent; the old one may be on its way outmonths together 2 |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 0 · files with deprecations 5 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 326 · added in two years 326 · removed within 60 days 14 |
| 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 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 0.0 · days since last tag 0 · commits last 90 days 1,301 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 0 · on branch 25 · tags in window 25 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 15
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 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.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.bus_factor_trend | fewer than three active years to compare |
| 03.joiners_and_leavers | too few regular contributors to see a trend |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.container_runs_as_root | no Dockerfile outside development, test and example paths |
| 05.outbound_timeouts | not assessed for TSX or TypeScript, the languages the product is written in: this check's patterns read other languages only |
| 05.migration_reversibility | too few migrations to judge |
| 05.dataset_provenance | not a data or machine-learning repository |
| 05.license_manifest_conflict | no licence file could be identified to compare the manifest against |
| 04.flags_accumulating | few or no feature flags in the history |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; OSV npm @llmgateway/models (an empty record for a package published here) did not |
| 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 CVT0-SN3Q-VWSY 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/CVT0SN3QVWSY?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: 690.1authenticated: False |
| 38.3s | cloned the repository to a temporary directory | depth: full |
| 57.9s | read the git history | commits: 5095tracked files: 5980 |
| 398.2s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 398.3s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 673.1s | kept the facts, never the source, for re-reading under new checks | |
| 673.1s | deleting the working copy |
Total 673.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).