6959dc8 · 15,977 commits · 33,890 files
Issued 2026-09-26
Nothing significant. Questions worth asking about Security & Reliability Posture, Observability & Operations.
92 checks ran across 6 assessable dimensions. 3 findings are worth checking first. 16 findings, each with evidence. One dimension cannot be assessed without an acquirer.
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.
- 3 findings rated significant by a check that has not yet held up in Borehole's calibration are now worth checking first.
- 2 findings from checks Borehole's calibration found wrong more often than right are no longer published.
- The file and line of 5 credential-shaped matches are withheld. File and line are shown to whoever GitHub says controls this repository, signed in, and to a buyer of this report.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | adequate | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 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 |
- 34% 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 · adequate · ratings ↑packages/twenty-server/src/engine/workspace-manager/dev-seeder/data/constants/person-data-seeds.constant.ts is 20,496 lines, 602× this codebase's median file
adequateThe median source file here is 34 lines. 46 files exceed 1,000 lines, the largest being 20,496. 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.
| line-count | packages/twenty-server/src/engine/workspace-manager/dev-seeder/data/constants/person-data-seeds.constant.ts:1 — 20,496 lines (602× median) |
| line-count | packages/twenty-server/src/utils/email-providers.ts:1 — 16,349 lines (480× median) |
| line-count | packages/twenty-ui/src/icon/providers/internal/AllIcons.ts:1 — 8,382 lines (246× median) |
| line-count | packages/twenty-server/src/engine/workspace-manager/dev-seeder/data/constants/company-data-seeds.constant.ts:1 — 7,937 lines (233× median) |
| line-count | packages/twenty-front/src/modules/onboarding/components/WelcomeOverlay/welcomeHalftoneDots.ts:1 — 2,905 lines (85× 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 are retried until they pass
adequateThe suite is configured to retry failing tests (packages/twenty-apps/examples/media-notes/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.
| packages/twenty-apps/examples/media-notes/playwright.config.ts | packages/twenty-apps/examples/media-notes/playwright.config.ts:12 — 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.
7% of recent commits change more than 2,000 lines
adequate657 of 9130 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 | 657 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.
Organization & Key-Person Risk
03 · strong · ratings ↑No finding. 9 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · adequate · ratings ↑155 direct dependencies in a single manifest
adequate worth checking firstpackages/twenty-server/package.json declares 155 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 packages/twenty-server/package.json and the 3 other files it cites settles it. If it holds when someone checks it, this finding is significant.
| direct-dependencies | packages/twenty-server/package.json — 155 declared |
| direct-dependencies | packages/twenty-front/package.json — 120 declared |
| direct-dependencies | packages/twenty-server/src/engine/core-modules/application/application-package/constants/seed-dependencies/package.json — 41 declared |
| direct-dependencies | packages/twenty-website/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.
3 jobs are each done by more than one library
adequateWithin a single package: CSS-in-JS: emotion, styled-components; HTTP clients: axios, node-fetch; UI component kits: chakra, mui. Each duplicate is bundle size, two ways of doing the same thing in one codebase, and two upgrade paths to maintain. It is usually the residue of a migration that stopped halfway.
| packages/twenty-apps/public/call-recorder/package.json | packages/twenty-apps/public/call-recorder/package.json — several libraries per job |
| packages/twenty-apps/public/fireflies/package.json | packages/twenty-apps/public/fireflies/package.json — several libraries per job |
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 ↑23 credential-shaped strings committed to the tree
adequate worth checking firstMatches for JWT appear in tracked files outside test and fixture paths. Whether these are live is not something a repository can settle, and they may well be rotated already — but they are in the history permanently, and the question a buyer must ask is what the rotation process was, not whether one string still works.
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. If it holds when someone checks it, this finding is significant.
| JWT | 5 cited: JWT pattern matched |
| File and line are shown to whoever GitHub says controls this repository, signed in, and to a buyer of this report. |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
1 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
| no-USER-instruction | packages/twenty-docker/twenty-postgres-spilo/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.
2 environment files are committed
adequatepackages/twenty-server/.env.e2e-testing-server, packages/twenty-server/.env.test 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.
| packages/twenty-server/.env.e2e-testing-server | packages/twenty-server/.env.e2e-testing-server — committed environment file |
| packages/twenty-server/.env.test | packages/twenty-server/.env.test — 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
adequate3 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.
| packages/twenty-apps/examples/hello-world/.github/workflows/cd.yml | packages/twenty-apps/examples/hello-world/.github/workflows/cd.yml:33 — action pinned by tag |
| packages/twenty-apps/examples/hello-world/.github/workflows/cd.yml | packages/twenty-apps/examples/hello-world/.github/workflows/cd.yml:39 — 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.
78 SQL statements built from strings
adequate worth checking first78 places in product code build SQL by formatting or joining strings rather than passing parameters. Where any part of the string comes from a request, it is an injection point. Each site needs a look; the fix, parameters, is small.
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 packages/twenty-server/src/database/commands/agent-history/agent-history-migration-data.service.ts:29 and the 1 other file it cites settles it. If it holds when someone checks it, this finding is significant.
| packages/twenty-server/src/database/commands/agent-history/agent-history-migration-data.service.ts | packages/twenty-server/src/database/commands/agent-history/agent-history-migration-data.service.ts:29 — SQL built from a string |
| packages/twenty-server/src/database/commands/agent-history/agent-history-migration-data.service.ts | packages/twenty-server/src/database/commands/agent-history/agent-history-migration-data.service.ts:90 — SQL built from a string |
| packages/twenty-server/src/database/commands/agent-history/agent-history-migration-validation.service.ts | packages/twenty-server/src/database/commands/agent-history/agent-history-migration-validation.service.ts:43 — SQL built from a string |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
5 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.
| packages/twenty-sdk/src/cli/commands/docker/index.ts | packages/twenty-sdk/src/cli/commands/docker/index.ts:52 — command run through a shell |
| packages/twenty-sdk/src/cli/commands/docker/index.ts | packages/twenty-sdk/src/cli/commands/docker/index.ts:128 — command run through a shell |
| packages/twenty-sdk/src/cli/commands/docker/index.ts | packages/twenty-sdk/src/cli/commands/docker/index.ts:132 — 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.
6 locked dependencies have published vulnerabilities, 4 high or critical
adequate6 of 5,295 locked dependencies match 9 published advisories in OSV, 4 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.
| yarn.lock | yarn.lock — adm-zip 0.6.0: GHSA-7q85-xj36-vmfc (high), fixed in 0.6.1 |
| yarn.lock | yarn.lock — brace-expansion 5.0.8: GHSA-rgw5-rvv9-x895 (high), fixed in 5.0.9 |
| yarn.lock | yarn.lock — extract-zip 2.0.1: GHSA-7pqw-9j4j-h8q3 (high) |
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 places insert HTML from a variable without sanitising it
adequate6 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.
| packages/twenty-emails/src/utils/email-renderer/email-renderer.tsx | packages/twenty-emails/src/utils/email-renderer/email-renderer.tsx:49 — HTML from a variable |
| packages/twenty-emails/src/utils/email-renderer/nodes/html.tsx | packages/twenty-emails/src/utils/email-renderer/nodes/html.tsx:11 — HTML from a variable |
| packages/twenty-front/src/modules/support/hooks/useInstantiateSupportChat.ts | packages/twenty-front/src/modules/support/hooks/useInstantiateSupportChat.ts:31 — 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.
Observability & Operations
06 · adequate · ratings ↑4 of 5 deployed images carry no version, or `latest`
adequate4 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
| packages/twenty-docker/helm/twenty/values.yaml | packages/twenty-docker/helm/twenty/values.yaml:146 — image without a version |
| packages/twenty-docker/k8s/manifests/deployment-db.yaml | packages/twenty-docker/k8s/manifests/deployment-db.yaml:30 — image without a version |
| packages/twenty-docker/k8s/manifests/deployment-redis.yaml | packages/twenty-docker/k8s/manifests/deployment-redis.yaml:26 — image without a version |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Readiness and liveness probes are identical in 1 of 1 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.
| packages/twenty-docker/helm/twenty/values.yaml | packages/twenty-docker/helm/twenty/values.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.
6 of 8 deployments run a single replica
adequate6 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.
| packages/twenty-docker/helm/twenty/templates/deployment-db-internal.yaml | packages/twenty-docker/helm/twenty/templates/deployment-db-internal.yaml — replicas: 1 |
| packages/twenty-docker/helm/twenty/templates/deployment-redis-internal.yaml | packages/twenty-docker/helm/twenty/templates/deployment-redis-internal.yaml — replicas: 1 |
| packages/twenty-docker/k8s/manifests/deployment-db.yaml | packages/twenty-docker/k8s/manifests/deployment-db.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
8 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 26,578 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 739 people have committed here. Which of them are you acquiring, and which are you replacing?
- Who mentors whom, and would that survive a departure?
- Can the team grow, and who stands behind the top three contributors?
- Is the seniority mix sound, and will pay survive your salary bands?
- Is the pace sustainable? Commit times cannot say: git keeps no reliable local time.
- Does the team want to stay after close?
- How are decisions made and disagreements resolved?
Product & Engineering Maturity
04 · minimal coverage- measured 6,237 commits landed in the last year, against 3,740 the year before (+67%). What drove it: new people, a deadline, or code produced faster than before?
- 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.1 and 05.5 found credential-shaped strings in this repository. Was each one revoked at the provider? Deleting it from the code revokes nothing; only the provider's audit log shows that it was.
- measured No threat model is in the tree of what looks like a running service. Does one exist elsewhere, and who owns it?
- What has actually broken, how often, and how badly?
- What did external testing find, and was it fixed?
- What is the SOC 2, ISO 27001 or GDPR status, and where is the evidence?
Observability & Operations
06 · partial coverage- measured Nothing in the tree backs up or restores data. How is data backed up, and has a restore ever been rehearsed?
- measured No alert rule is defined in the repository. Where are alerts defined, who receives them, and when did one last fire?
- Are the dashboards opened, the alerts acknowledged and the pages answered?
- Are the service-level objectives actually met?
- Who carries the pager, and how often does it go off?
- What does it cost to run, and how much headroom is there?
Fit with the Acquirer
07 · none coverageNot rated: structurally not assessable from a repository.
- This is primarily a 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/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (packages/twenty-docker/docker-compose.yml and 74 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/twentyhq/twenty/6959dc8)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 — 76 signals that ran and did not fire
Appendix: rejection log — 76 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 — 54
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few files, in the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026)files 99,652 · top5 share 0.013 · history read the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026) |
| 04.debt_markers | debt markers are sparsemarkers 276 · per kloc 0.15 · lines read 1,802,559 |
| 04.test_growth | test effort kept pace with code written, in the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026)history read the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026) · late test per code 0.286 · early test per code 0.163 |
| 04.churn_trend | rework is not rising against new work, in the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026)history read the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026) · late delete per insert 0.62 · early delete per insert 0.638 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fixes_with_tests | fixes usually come with a testfixes 3,632 · share 0.338 · with tests 1,228 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.012 · code files 21,993 · compat files 272 |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 62 |
| 06.structured_logging | a structured logging library is referencedmatches 1 |
| 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 33 |
| 06.error_reporting | an error reporter is initialisedinitialised 1 · config files 0 |
| 06.environment_branching | environment differences live in configurationsites 2 |
| 06.release_markers | releases are markedtags last year 189 · release commits 38 · changelog commits 64 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthswindow last 24 months · authors 739 · top share less than a quarter |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 494 |
| 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 41 · joined 33 · regular last year 56 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 816 |
| 02.ci_presence | CI configuration is present in the working treecount 54 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 5,553 · source 28,783 · test ratio 0.193 |
| 02.conventional_commits | commit subjects generally carry content, in the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026)sampled 15,909 · history read the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026) · low content share 0.003 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 54 · with tests 10 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 6,621 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 54 |
| 02.revert_share | change is rarely undoneshare 0.003 · reverts 27 · recent commits 9,988 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 23 · commits since 53 · days since lockfile changed 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 9 · ci configs 54 · product files 21,993 |
| 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 it, in the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026)history read the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026) · largest commits 7ec5643..ff1a870 · bursts explained 1 |
| 01.message_uniformity | commit subjects vary in wording and length, in the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026)history read the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026) · length stdev 20.77 · repeat share 0.005 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0174 · product files 21,796 · distinct blocks 950,151 |
| 01.swallowed_errors | errors are rarely thrown awayloc 1,827,730 · files 17 · per kloc 0.02 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 14 |
| 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.outbound_timeouts | outbound calls set timeouts, or are fewcalls without timeout 0 |
| 05.unsafe_deserialization | no code-executing deserialiser in product codesites 0 |
| 05.resource_limits | every workload declares limitsworkloads 8 · without limits 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 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.source_maps_shipped | production builds do not publish source mapssites 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_manifest_conflict | manifest and licence file agree on AGPL-3.0license AGPL-3.0 |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.license_grant_unclear | the licence is recognisable as AGPL-3.0class network-copyleft · license AGPL-3.0 |
Could not conclude, or did not apply — 22
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.schema_churn | columns, once added, stay |
| 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.active_contributors | not assessed: this check needs the whole history, and only the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026) were read |
| 03.knowledge_silos | not assessed: this check needs the whole history, and only the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026) were read |
| 03.drive_by_contributors | not assessed: this check needs the whole history, and only the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026) were read |
| 03.contributor_attrition | not assessed: this check needs the whole history, and only the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026) were read |
| 02.release_cadence | not assessed: this check needs the whole history, and only the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026) were read |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.initial_dump | not assessed: this check needs the whole history, and only the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026) were read |
| 01.revision_depth | not assessed: this check needs the whole history, and only the most recent 15,977 commits (1 Dec 2022 to 25 Sep 2026) were read |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.migration_reversibility | too few migrations to judge |
| 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 |
| 04.flags_accumulating | the history scanned covers 6 months, less than the 12 this question needs |
| 04.api_versions_coexisting | the history scanned covers 6 months, less than the 18 this question needs |
| 04.deprecations_lingering | the history scanned covers 6 months, less than the 24 this question needs |
| 04.dependency_churn | the history scanned covers 6 months, less than the 24 this question needs |
| 04.ci_platforms_dropped | the history scanned covers 6 months, less than the 24 this question needs |
Anyone can check this report against the authoritative record — click the stamp, or enter K28P-W0PS-7EW6 at borehole.dev/verify.
The code commits to the 94 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/K28PW0PS7EW6?via=badge)
A survey is a reading by a particular version of the assessor. Older readings are kept rather than replaced, because a verification mark attests to the survey it was issued for — overwriting one would make every code already in circulation read as tampered.
| Read | Assessor | Findings | Band |
|---|---|---|---|
| 2026-09-26 · shown | borehole 0.6.3 | 18 | adequate |
12 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 19 | adequate |
| 2026-10-03 | borehole 0.7.12 | 19 | adequate |
| 2026-10-03 | borehole 0.7.11 | 19 | adequate |
| 2026-10-01 | borehole 0.7.9 | 19 | adequate |
| 2026-09-30 | borehole 0.7.8 | 18 | adequate |
| 2026-09-29 | borehole 0.7.5 | 20 | adequate |
| 2026-09-27 | borehole 0.7.3 | 19 | adequate |
| 2026-09-27 | borehole 0.7.2 | 18 | adequate |
| 2026-09-27 | borehole 0.7.1 | 18 | adequate |
| 2026-09-26 | borehole 0.7.0 | 18 | adequate |
| 2026-09-26 | borehole 0.6.2 | 18 | adequate |
| 2026-09-25 | borehole 0.6.1 | 18 | adequate |
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: 1968.6authenticated: False |
| 171.0s | cloned the repository to a temporary directory | depth: 20,000 commits |
| 360.1s | read the git history | commits: 15977tracked files: 33890 |
| 1086.0s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 1086.1s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 1539.8s | kept the facts, never the source, for re-reading under new checks | |
| 1539.8s | deleting the working copy |
Total 1539.8s ·source content sent off this machine: none · calls to a language model: 0 · the clone was deleted when the survey ended
An automated reading of a repository's code and its history up to one commit, with public advisory records. It may be wrong, it is not legal, financial, investment or security advice, and it does not replace diligence by a qualified person. It is provided for information: nobody may rely on it (Borehole's terms, section 3).