54343aa · 5,000 commits · 7,702 files
Issued 2026-09-25
Nothing significant. Questions worth asking about Security & Reliability Posture, Product & Engineering Maturity.
92 checks ran across 6 assessable dimensions. 2 findings are worth checking first. 18 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.
- Words about people are today's: bands rather than exact shares, dates or day counts, and what the history measured rather than why.
- 1 finding that needed more history than this survey read is no longer published.
- 2 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.
| 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 |
- 41% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- no widespread author/committer date divergence
- the declared share is neither decisive nor negligible, so the true figure is more sensitive to undeclared work
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑packages/features/watchlist/lib/freeEmailDomainCheck/freeEmailDomains.ts is 4,769 lines, 110× this codebase's median file
adequateThe median source file here is 43 lines. 28 files exceed 1,000 lines, the largest being 4,769. 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/features/watchlist/lib/freeEmailDomainCheck/freeEmailDomains.ts:1 — 4,769 lines (110× median) |
| line-count | apps/api/v2/src/platform/event-types/event-types_2024_06_14/controllers/event-types.controller.e2e-spec.ts:1 — 3,193 lines (74× median) |
| line-count | packages/features/bookings/lib/service/RegularBookingService.ts:1 — 2,691 lines (62× median) |
| line-count | packages/testing/src/lib/bookingScenario/bookingScenario.ts:1 — 2,447 lines (56× median) |
| line-count | packages/features/bookings/repositories/BookingRepository.ts:1 — 2,174 lines (50× median) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Engineering Process & SDLC Maturity
02 · adequate · ratings ↑Tests cover a thin slice of the codebase
adequate499 test files against 5,057 source files (9.9%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| test-file-ratio | 499 test files / 5,057 source files |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/platform/examples/base/playwright.config.ts); 1 test is individually marked to retry. 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/platform/examples/base/playwright.config.ts | packages/platform/examples/base/playwright.config.ts:16 — test retry |
| apps/api/v2/test/jest.setup-e2e.ts | apps/api/v2/test/jest.setup-e2e.ts:1 — 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. 9 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · adequate · ratings ↑117 direct dependencies in a single manifest
adequateapps/web/package.json declares 117 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/web/package.json — 117 declared |
| direct-dependencies | apps/api/v2/package.json — 48 declared |
| direct-dependencies | packages/ui/package.json — 38 declared |
| direct-dependencies | packages/features/package.json — 25 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.
Effort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.31 to 1.22 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| deletions-per-insertion | first half 0.31, second half 1.22 (split 2025-11-02) |
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.
Node.js 20 is past end of life
adequateThe code is pinned to Node.js 20 (end of life 2026-04-30). None of these receives security fixes any more; the first stopped on 2026-04-30. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
| Dockerfile | Dockerfile — Node.js 20, end of life 2026-04-30 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Fixes are 70% of recent work, up from 46%
adequateIn the last two quarters 70% of commits were fixes, against 46% in the quarters before. Rising fix work usually means quality debt is coming due, and it takes time that new work would have had.
| fix share by quarter | 72%, 67%, 44%, 46%, 45%, 46%, 48%, 46% |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Security & Reliability Posture
05 · adequate · ratings ↑2 Dockerfiles run the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
| no-USER-instruction | Dockerfile — runs as root |
| no-USER-instruction | apps/api/v2/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.
1 environment file is committed
adequatepackages/prisma/.env is 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/prisma/.env | packages/prisma/.env — 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
adequate11 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.
| .github/workflows/changesets.yml | .github/workflows/changesets.yml:36 — action pinned by tag |
| .github/workflows/e2e-api-v2.yml | .github/workflows/e2e-api-v2.yml:72 — action pinned by tag |
| scripts/vercel.sh | scripts/vercel.sh:7 — 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.
14 SQL statements built from strings
adequate worth checking first14 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/app-store/salesforce/lib/CrmService.ts:291 settles it. If it holds when someone checks it, this finding is significant.
| packages/app-store/salesforce/lib/CrmService.ts | packages/app-store/salesforce/lib/CrmService.ts:291 — SQL built from a string |
| packages/app-store/salesforce/lib/CrmService.ts | packages/app-store/salesforce/lib/CrmService.ts:302 — SQL built from a string |
| packages/app-store/salesforce/lib/CrmService.ts | packages/app-store/salesforce/lib/CrmService.ts:853 — 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.
1 deserialiser that can run code
adequate1 places read data with a deserialiser that executes what it reads (pickle, `yaml.load` without a safe loader, object streams, `unserialize`). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
| apps/web/lib/apps/[slug]/getStaticProps.ts | apps/web/lib/apps/[slug]/getStaticProps.ts:35 — code-executing deserialiser |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
71 locked dependencies have published vulnerabilities, 85 high or critical
adequate71 of 3,815 locked dependencies match 171 published advisories in OSV, 85 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 — next 15.5.15: GHSA-2xp9-vwfh-vxw4 (critical), fixed in 15.5.24 |
| yarn.lock | yarn.lock — next 16.2.3: GHSA-2xp9-vwfh-vxw4 (critical), fixed in 16.3.3 |
| yarn.lock | yarn.lock — next-auth 4.24.13: GHSA-7rqj-j65f-68wh (critical), fixed in 4.24.15 |
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.
17 places insert HTML from a variable without sanitising it
adequate worth checking first17 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.
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 apps/web/app/(use-page-wrapper)/layout.tsx:33 and the 2 other files it cites settles it. If it holds when someone checks it, this finding is significant.
| apps/web/app/(use-page-wrapper)/layout.tsx | apps/web/app/(use-page-wrapper)/layout.tsx:33 — HTML from a variable |
| apps/web/app/SpeculationRules.tsx | apps/web/app/SpeculationRules.tsx:28 — HTML from a variable |
| apps/web/components/PageWrapper.tsx | apps/web/components/PageWrapper.tsx:87 — 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.
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/web/next.config.ts | apps/web/next.config.ts:239 — 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.
Observability & Operations
06 · adequate · ratings ↑No telemetry or error reporting is wired in anywhere
adequateNone of 6,682 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| telemetry-scan | searched 6,682 tracked text files for 16 known instrumentation libraries; 0 matched |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
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.
| docker-compose.yml | docker-compose.yml:28 — image without a version |
| packages/prisma/docker-compose.yml | packages/prisma/docker-compose.yml:21 — image without a version |
| docker-compose.yml | docker-compose.yml:122 — 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.
The code branches on the environment's name at 17 places
adequate17 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.
| apps/api/v2/src/app.module.ts | apps/api/v2/src/app.module.ts:38 — branch on the environment name |
| apps/api/v2/src/lib/logger.ts | apps/api/v2/src/lib/logger.ts:25 — branch on the environment name |
| apps/api/v2/src/lib/logger.ts | apps/api/v2/src/lib/logger.ts:25 — 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
9 checks against the running system follow from the findings above: what a buyer's engineer will try, how to run it first, and what to have ready. A paid survey of this repository includes them.
A paid survey of a public repository is also reviewed: a language model reads each finding against the code and withdraws only findings it judges the code contradicts, each listed with its reason. The review is a language model's reading of the findings against the code, and it can be wrong. It never adds a finding, never raises a band, and never removes a finding from a proven check or an advisory that affects the surveyed version.
What a person adds
The survey reads what the repository can show. The code cannot settle these questions, and on them this report states nothing. Each says where its answer lives: your own engineer, the company, or an assessor you choose can settle it. Questions marked measured open with something this repository shows.
Architecture & Codebase — including AI provenance
01 · full coverage- measured The tree carries design documentation (specs/_templates/design.md and 1 more). Does it match what the team believes today? Ask them to walk through it against the code.
- Is the architecture right for the next three years of the product?
- Were the home-grown components reasonable choices when they were made, and are they now?
Engineering Process & SDLC Maturity
02 · high coverage- Is review real or a rubber stamp? Comment depth and time to approve need the pull request history.
- Is delivery planned and measured, or heroic?
- How are incidents run, reviewed and learned from?
Organization & Key-Person Risk
03 · partial coverage- measured 314 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 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/, companion/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (Dockerfile and 6 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/calcom/cal.com/54343aa)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 — 74 signals that ran and did not fire
Appendix: rejection log — 74 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 — 59
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 16,067 · top5 share 0.023 |
| 04.debt_markers | debt markers are sparsemarkers 366 · per kloc 0.48 · lines read 764,764 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.239 · early test per code 0.169 |
| 04.fixes_with_tests | fixes usually come with a testfixes 2,171 · share 0.207 · with tests 449 |
| 04.schema_churn | columns, once added, staydropped within 90 days 2 · columns added last year 30 |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 4,445 · compat files 0 |
| 04.dependency_redundancy | one library per job, mostly |
| 06.structured_logging | a structured logging library is referencedmatches 9 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.telemetry_depth | the service is visible in more than one way |
| 06.correlation_ids | a request can be followed through the logstracing False · request id sites 28 |
| 06.error_reporting | an error reporter is initialisedinitialised 4 · config files 4 |
| 06.release_markers | releases are markedtags last year 77 · release commits 0 · changelog commits 2 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 1.8 · window last 24 months · authors 314 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 321 · active 12mo 204 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 321 · one off share 0.567 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 321 · top share less than a quarter · top contributor last committed between three and six months ago |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 314 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.joiners_and_leavers | the team is not shrinkingleft 25 · joined 30 · regular last year 59 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 47 |
| 02.ci_presence | CI configuration is present in the working treecount 50 |
| 02.release_cadence | tags are presenttags 260 |
| 02.conventional_commits | commit subjects generally carry contentsampled 5,000 · 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 50 · with tests 5 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 35 · test files 505 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 50 |
| 02.revert_share | change is rarely undoneshare 0.012 · reverts 57 · recent commits 4,654 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 2 · commits since 33 · days since lockfile changed 85 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 14 · ci configs 50 · product files 4,445 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.034 · commits 4,177 · over 2000 lines 143 |
| 01.burst_import | no commit run met both the rate and the net-addition thresholdgap seconds 180 · min add ratio 3.0 · min net added 2,000 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 667,401 · share of insertions 0.3219 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 20.63 · repeat share 0.009 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 16,076 · write once share 0.443 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0182 · product files 4,456 · distinct blocks 315,016 |
| 01.swallowed_errors | errors are rarely thrown awayloc 771,363 · files 11 · per kloc 0.02 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 4 |
| 01.unfinished_migration | no language migration is stalled halfway |
| 01.weights_in_git | no model weights are committedfiles 0 |
| 05.committed_secrets | no credential-shaped strings outside test and fixture pathsnote the working tree only; the history is 05.5 · patterns 7 · files read 6,682 |
| 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 7 · truncated False · added lines 1,018,795 |
| 05.outbound_timeouts | outbound calls set timeouts, or are fewcalls without timeout 0 |
| 05.shell_from_strings | product code does not build shell commands from stringssites 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 |
| 05.public_env_secret | only publishable values carry a public prefixnames 0 · sites 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.license_grant_unclear | the licence is recognisable as MITclass permissive · license MIT |
| 04.flags_accumulating | flags are retired about as fast as they are addedlive 0 · retired 6 · flags seen 6 |
| 04.api_versions_coexisting | one API version is served, or none |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 0 · files with deprecations 55 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 318 · added in two years 318 · removed within 60 days 12 |
| 04.ci_platforms_dropped | no platform was dropped from CI in the last two years |
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.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.bus_factor_trend | fewer than three active years to compare |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.migration_reversibility | too few migrations to judge |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.cleartext_traffic | not a mobile app |
| 05.dataset_provenance | not a data or machine-learning repository |
| 05.license_copyleft_inherited | no third-party code is committed to this repository, so the licences it depends on are resolved at build time and are not readable here |
| 05.license_manifest_conflict | no packaging manifest states a licence |
| 03.knowledge_silos | not assessed: this check needs the whole history, and only the most recent 5,000 commits were read |
Anyone can check this report against the authoritative record — click the stamp, or enter JKXK-8TVJ-TH83 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/JKXK8TVJTH83?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-25 · shown | borehole 0.6.0 | 21 | adequate |
16 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 18 | strong |
| 2026-10-03 | borehole 0.7.12 | 18 | strong |
| 2026-10-03 | borehole 0.7.11 | 18 | strong |
| 2026-10-02 | borehole 0.7.10 | 18 | strong |
| 2026-10-01 | borehole 0.7.9 | 18 | adequate |
| 2026-09-30 | borehole 0.7.8 | 18 | adequate |
| 2026-09-29 | borehole 0.7.6 | 18 | adequate |
| 2026-09-28 | borehole 0.7.5 | 18 | adequate |
| 2026-09-28 | borehole 0.7.4 | 18 | adequate |
| 2026-09-27 | borehole 0.7.3 | 17 | adequate |
| 2026-09-27 | borehole 0.7.2 | 17 | adequate |
| 2026-09-27 | borehole 0.7.1 | 17 | adequate |
| 2026-09-26 | borehole 0.7.0 | 17 | adequate |
| 2026-09-26 | borehole 0.6.3 | 17 | adequate |
| 2026-09-26 | borehole 0.6.2 | 17 | adequate |
| 2026-09-25 | borehole 0.6.1 | 15 | 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 — 6 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: 1130.3authenticated: False |
| 42.8s | cloned the repository to a temporary directory | depth: 5,000 commits |
| 59.6s | read the git history | commits: 5000tracked files: 7702 |
| 185.2s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 185.2s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 185.2s | deleting the working copy |
Total 185.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).