1283425 · 27,925 commits · 15,153 files
Issued 2026-10-22
AGPL-3.0 since 2023-12-01: open source; offering it over a network counts as distributing it, so a hosted product's changes must be published.
104 checks ran across 6 assessable dimensions. 2 findings are worth checking first. 17 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 05.60 AGPL-3.0 since 2023-12-01: open source; offering it over a network counts as distributing it, so a hosted product's changes must be published
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.
- 2 findings from checks Borehole's calibration found wrong more often than right are no longer published.
- 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 | strong | |
| 03 | Organization & Key-Person Risk | strong | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 15% 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
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑lib/auth/auth_with_roles.go is 9,386 lines, 89× this codebase's median file
adequateThe median source file here is 105 lines. 121 files exceed 1,050 lines, the largest being 9,386. 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 | lib/auth/auth_with_roles.go:1 — 9,386 lines (89× median) |
| line-count | lib/auth/auth.go:1 — 9,259 lines (88× median) |
| line-count | integrations/terraform/tfschema/scopes/joining/v1/token_terraform.go:1 — 8,283 lines (78× median) |
| line-count | lib/service/service.go:1 — 8,011 lines (76× median) |
| line-count | lib/auth/grpcserver.go:1 — 7,000 lines (66× median) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Engineering Process & SDLC Maturity
02 · strong · ratings ↑Tests are retried until they pass
adequateThe suite is configured to retry failing tests (e2e/playwright.config.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.
| e2e/playwright.config.ts | e2e/playwright.config.ts:37 — 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 · strong · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · adequate · ratings ↑280 direct dependencies in a single manifest
adequate worth checking firstgo.mod declares 280 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.
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 go.mod and the 3 other files it cites settles it. If it holds when someone checks it, this finding is significant.
| direct-dependencies | go.mod — 280 declared |
| direct-dependencies | package.json — 37 declared |
| direct-dependencies | api/go.mod — 28 declared |
| direct-dependencies | web/packages/teleport/package.json — 23 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.
Releases are cut from another branch than the one surveyed
adequateThe newest release, v18.11.1, is not on the branch this survey read; the newest release on it is v2.6.0. The shipped product may differ from what this report describes. Survey the release branch too.
A note that does not affect this rating: notes like it are common in well-run projects.
| 27eb07217 | tag v18.11.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.
Security & Reliability Posture
05 · adequate · ratings ↑1 credential-shaped string in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key. 2 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.
| private key block | private key block, where fakes are usual |
| File and line are shown to whoever GitHub says controls this repository, signed in, and to a buyer of this report. |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
5 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 | build.assets/charts/Dockerfile — runs as root |
| no-USER-instruction | integrations/access/Dockerfile — runs as root |
| no-USER-instruction | integrations/event-handler/Dockerfile — runs as root |
| no-USER-instruction | integrations/kube-agent-updater/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.
43 locked dependencies have published vulnerabilities, 13 high or critical in what ships
adequate worth checking first43 of 2,715 locked dependencies match 117 published advisories in OSV, 48 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
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 pnpm-lock.yaml settles it. If it holds when someone checks it, this finding is significant.
| pnpm-lock.yaml | pnpm-lock.yaml — @storybook/addon-vitest 10.5.7: GHSA-f2ph-cmg5-wxc8 (critical), fixed in 10.6.2; a development dependency |
| pnpm-lock.yaml | pnpm-lock.yaml — storybook 10.5.7: GHSA-f2ph-cmg5-wxc8 (critical), fixed in 10.6.2; a development dependency |
| pnpm-lock.yaml | pnpm-lock.yaml — tinypool 2.1.0: GHSA-5gmw-xhrv-c9v3 (critical), fixed in 2.1.1; a development dependency |
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
adequate2 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 1 step pipes a download straight into a shell. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
A note that does not affect this rating: notes like it are common in well-run projects.
| .github/workflows/assign.yaml | .github/workflows/assign.yaml:39 — action pinned by tag |
| .github/workflows/post-release.yaml | .github/workflows/post-release.yaml:50 — action pinned by tag |
| build.assets/Dockerfile | build.assets/Dockerfile:206 — download piped into a shell |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
2 outbound calls can wait forever
adequate2 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.
| lib/accessgraph/apiclient/client.gen.go | lib/accessgraph/apiclient/client.gen.go:709 — outbound call without a timeout |
| lib/srv/app/cloud.go | lib/srv/app/cloud.go:283 — 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 SQL statements built from strings
adequate6 places in product code build SQL by formatting or joining strings rather than passing parameters. 2 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. 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.
| lib/events/auditqueue/sqlite.go | lib/events/auditqueue/sqlite.go:756 — SQL built from a string |
| lib/events/auditqueue/sqlite.go | lib/events/auditqueue/sqlite.go:763 — SQL built from a string |
| lib/backend/pgbk/common/utils.go | lib/backend/pgbk/common/utils.go:321 — 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 of 3 Kubernetes workloads declare no resource limits
adequate3 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| assets/loadtest/helm/node-agent/templates/deployment.yaml | assets/loadtest/helm/node-agent/templates/deployment.yaml — workload with no limits |
| assets/loadtest/helm/resources/templates/tbot.yaml | assets/loadtest/helm/resources/templates/tbot.yaml — workload with no limits |
| assets/loadtest/helm/trusted-cluster/templates/deployment.yaml | assets/loadtest/helm/trusted-cluster/templates/deployment.yaml — workload with no limits |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
5 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| docs/pages/connect-your-client/third-party/ansible.mdx | docs/pages/connect-your-client/third-party/ansible.mdx — 1 tracked files, no licence file |
| docs/pages/connect-your-client/third-party/gui-clients.mdx | docs/pages/connect-your-client/third-party/gui-clients.mdx — 1 tracked files, no licence file |
| docs/pages/connect-your-client/third-party/jetbrains-sftp.mdx | docs/pages/connect-your-client/third-party/jetbrains-sftp.mdx — 1 tracked files, no licence file |
| docs/pages/connect-your-client/third-party/putty-winscp.mdx | docs/pages/connect-your-client/third-party/putty-winscp.mdx — 1 tracked files, no licence file |
| docs/pages/connect-your-client/third-party/vscode.mdx | docs/pages/connect-your-client/third-party/vscode.mdx — 1 tracked files, no licence file |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Relicensed: Apache-2.0 → AGPL-3.0 (2023-12-01)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
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".
| 03161e511 | LICENSE — Apache-2.0 from 2015-10-31 |
| b178b8b73 | LICENSE — AGPL-3.0 from 2023-12-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.
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2025-06-16. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 2.6.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 4 records name teleport with nothing tying them to this repository (CVE-2018-19301, CVE-2018-19555, CVE-2022-38599, …).
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-8cqv-pj7f-pwpc | 2025-06-16: GHSA-8cqv-pj7f-pwpc (critical), fixed in 12.4.35: Teleport allows remote authentication bypass |
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 ↑Sends usage data to usage.teleport.dev by default
adequateweb/packages/teleterm/csp.ts sends to usage.teleport.dev, and lib/autoupdate/agent/setup.go leaves reporting on as shipped. Every installation reports to the vendor unless its operator turns this off. For a buyer running it inside their own product, that is an outbound data flow to a third party: ask what is sent, how often, and whether the buyer's customers were told.
| web/packages/teleterm/csp.ts | web/packages/teleterm/csp.ts:23 — reports to usage.teleport.dev |
| lib/autoupdate/agent/setup.go | lib/autoupdate/agent/setup.go:728 — the reporting setting is on by default |
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.
1 of 3 deployments run a single replica
adequate1 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.
| assets/loadtest/helm/resources/templates/tbot.yaml | assets/loadtest/helm/resources/templates/tbot.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.
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
11 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 (integrations/terraform/ARCHITECTURE.md). Does it match what the team believes today? Ask them to walk through it against the code.
- 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 361 people have committed here. Which of them are you acquiring, and which are you replacing?
- Who mentors whom, and would that survive a departure?
- Can the team grow, and who stands behind the top three contributors?
- Is the seniority mix sound, and will pay survive your salary bands?
- Is the pace sustainable? Commit times cannot say: git keeps no reliable local time.
- Does the team want to stay after close?
- How are decisions made and disagreements resolved?
Product & Engineering Maturity
04 · minimal coverage- Can this team deliver the stated roadmap on the stated timeline?
- Does leadership know about the debt, and is time budgeted to repay it?
- Is the engineering shape consistent with the commercial story?
Security & Reliability Posture
05 · partial coverage- measured 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 Backup or restore tooling is in the tree (assets/loadtest/control-plane/teleport/gen-firestore-teleport.sh). Has a restore ever been rehearsed, and how long did it take?
- 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 Go codebase, with TypeScript alongside (37% of source files). Does your engineering organisation already run Go in production, or would this be the first?
- The bulk of this system sits in web/, api/, lib/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (assets/loadtest/helm/.gitignore and 252 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/gravitational/teleport/1283425)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 — 67
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 46,117 · top5 share 0.022 |
| 04.debt_markers | debt markers are sparsemarkers 1,669 · per kloc 0.73 · lines read 2,300,223 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.426 · early delete per insert 0.427 |
| 04.fixes_with_tests | fixes usually come with a testfixes 1,099 · share 0.502 · with tests 552 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.008 · code files 6,419 · compat files 53 |
| 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 246 |
| 06.structured_logging | a structured logging library is referencedmatches 819 |
| 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 185 |
| 06.environment_branching | environment differences live in configurationsites 3 |
| 06.release_markers | releases are markedtags last year 1,563 · release commits 2 · changelog commits 45 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 11.5 · window last 24 months · authors 361 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 361 · active 12mo 105 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 361 · directories 17 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 361 · one off share 0.382 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 361 · top share less than a quarter · top contributor last committed within the last three months |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 127 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.bus_factor_trend | the team has not narrowed to one person |
| 03.joiners_and_leavers | the team is not shrinkingleft 2 · joined 34 · regular last year 93 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 350 |
| 02.ci_presence | CI configuration is present in the working treecount 51 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 2,857 · source 8,630 · test ratio 0.331 |
| 02.release_cadence | tags are presenttags 7,117 |
| 02.conventional_commits | commit subjects generally carry contentsampled 26,529 · low content share 0.011 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 51 · with tests 15 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 3,493 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 51 |
| 02.revert_share | change is rarely undoneshare 0.002 · reverts 13 · recent commits 8,105 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 24 · commits since 0 · days since lockfile changed 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 12 · ci configs 51 · product files 6,419 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.017 · commits 7,483 · over 2000 lines 125 |
| 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 e6951df..76b1f4e · bursts explained 1 · largest net added 4,324 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 26 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 19.16 · repeat share 0.025 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 7,391 · write once share 0.228 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0084 · product files 5,780 · distinct blocks 734,495 |
| 01.swallowed_errors | errors are rarely thrown awayloc 2,308,336 · files 1 · per kloc 0.0 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 20 |
| 01.unfinished_migration | no language migration is stalled halfway |
| 01.weights_in_git | no model weights are committedfiles 0 |
| 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_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.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.source_maps_shipped | production builds do not publish source mapssites 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 6 |
| 05.license_manifest_conflict | manifest and licence file agree on AGPL-3.0license AGPL-3.0 |
| 05.license_grant_unclear | the licence is recognisable as AGPL-3.0class network-copyleft · license AGPL-3.0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 1 |
| 04.api_versions_coexisting | the newer API version is recent; the old one may be on its way outmonths together 10 |
| 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 0.0 · days since last tag 36 · commits last 90 days 381 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 20
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.test_growth | tests are kept inside the files they test, which a count by file name cannot see |
| 04.eol_runtime | no pinned runtime version to check |
| 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.feature_flags | no feature-flag service; flags may live elsewhere |
| 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.migration_reversibility | too few migrations to judge |
| 05.public_env_secret | not assessed for Go, the language the product is written in: this check's patterns read other languages only |
| 05.unsafe_html | not assessed for Go, the language the product is written in: this check's patterns read other languages only |
| 05.dataset_provenance | not a data or machine-learning repository |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.deprecations_lingering | the history scanned covers 18 months, less than the 24 this question needs |
| 04.dependency_churn | the history scanned covers 18 months, less than the 24 this question needs |
| 04.ci_platforms_dropped | the history scanned covers 18 months, less than the 24 this question needs |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; NVD: 4 records name teleport with nothing tying them to this repository (CVE-2018-19301, CVE-2018-19555, CVE-2022-38599, …); 4 are fixed in the surveyed commit, and the release users run is not placed by this history |
| 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 QBVY-AMT9-663E 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/QBVYAMT9663E?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: 1514.0authenticated: False |
| 213.8s | cloned the repository to a temporary directory | depth: full |
| 327.2s | read the git history | commits: 27925tracked files: 15153 |
| 953.0s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 953.1s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 1445.2s | kept the facts, never the source, for re-reading under new checks | |
| 1445.2s | deleting the working copy |
Total 1445.2s ·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).