0f33b90 · 31,536 commits · 5,282 files
Issued 2026-10-02
Reads strong. FSL-1.1-MIT since 2024-03-12: source available, not open source; a competing commercial product or service is not allowed; each version becomes MIT two years after its release.
105 checks ran across 6 assessable dimensions. 4 of 5 rated dimensions are strong, 1 is adequate and none is significant. Security & Reliability Posture is adequate. 1 finding is worth checking first. 11 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 05.60 FSL-1.1-MIT since 2024-03-12: source available, not open source; a competing commercial product or service is not allowed; each version becomes MIT two years after its release
- 05.66 The licence is FSL-1.1-MIT: source available, not open source LICENSE.md:1
- 05.60 Relicensed: FSL-1.0-MIT → FSL-1.1-MIT (2024-03-12) LICENSE.md
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.
- 05.26 46 locked dependencies have published vulnerabilities, 31 high or critical in what ships
- 1 finding from checks Borehole's calibration found wrong more often than right is 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 | strong | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | not assessable | |
| 07 | Fit with the Acquirer | not assessable |
- 5% 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 ↑crates/but-forge/src/review.rs is 4,740 lines, 58× this codebase's median file
adequateThe median source file here is 81 lines. 60 files exceed 1,000 lines, the largest being 4,740. 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 | crates/but-forge/src/review.rs:1 — 4,740 lines (58× median) |
| line-count | crates/but/src/id/tests.rs:1 — 4,135 lines (51× median) |
| line-count | apps/lite/ui/src/routes/project/$id/workspace/Details.tsx:1 — 3,926 lines (48× median) |
| line-count | crates/but-github/src/client.rs:1 — 3,556 lines (43× median) |
| line-count | crates/but/src/command/legacy/status/tui/cursor/tests.rs:1 — 2,844 lines (35× 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 (apps/web/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.
| apps/web/playwright.config.ts | apps/web/playwright.config.ts:10 — 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 · strong · ratings ↑No finding. 19 checks ran and none fired; the rejection log below says why each did not.
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.
| GitHub token | GitHub token, 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.
46 locked dependencies have published vulnerabilities, 31 high or critical in what ships
adequate worth checking first46 of 3,221 locked dependencies match 132 published advisories in OSV, 53 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 — axios 1.13.5: GHSA-35jp-ww65-95wh (high), fixed in 1.16.0 |
| pnpm-lock.yaml | pnpm-lock.yaml — brace-expansion 1.1.14: GHSA-3jxr-9vmj-r5cp (high), fixed in 1.1.16 |
| pnpm-lock.yaml | pnpm-lock.yaml — brace-expansion 5.0.6: GHSA-3jxr-9vmj-r5cp (high), fixed in 5.0.7 |
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/desktop/vite.config.ts | apps/desktop/vite.config.ts:66 — source maps in a production build |
| apps/lite/electron/vite.config.ts | apps/lite/electron/vite.config.ts:25 — source maps in a production build |
| apps/web/vite.config.ts | apps/web/vite.config.ts:39 — 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.
3 environment files are committed
adequateapps/desktop/.env.nightly, apps/desktop/.env.production, apps/web/.env are tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| apps/desktop/.env.nightly | apps/desktop/.env.nightly — committed environment file |
| apps/desktop/.env.production | apps/desktop/.env.production — committed environment file |
| apps/web/.env | apps/web/.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
adequate1 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.
| scripts/install.sh | scripts/install.sh:6 — 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.
40 places insert HTML from a variable without sanitising it
adequate40 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| apps/desktop/src/components/branch/CreateBranchModal.svelte | apps/desktop/src/components/branch/CreateBranchModal.svelte:173 — HTML from a variable |
| apps/desktop/src/components/branch/CreateBranchModal.svelte | apps/desktop/src/components/branch/CreateBranchModal.svelte:175 — HTML from a variable |
| apps/desktop/src/components/branch/CreateBranchModal.svelte | apps/desktop/src/components/branch/CreateBranchModal.svelte:208 — 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 licence is FSL-1.1-MIT: source available, not open source
adequateLICENSE.md grants FSL-1.1-MIT: source available, not open source; a competing commercial product or service is not allowed; each version becomes MIT two years after its release. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
A note that does not affect this rating: it names the project's licence, a fact for the first screen rather than a weakness.
| LICENSE.md | LICENSE.md:1 — 110 lines, FSL-1.1-MIT |
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: FSL-1.0-MIT → FSL-1.1-MIT (2024-03-12)
adequateThe root licence changed 1 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
A note that does not affect this rating: a licence change is a fact for the first screen, and only a narrowing of rights within two years of the surveyed commit costs "strong".
| 6bdf27493 | LICENSE.md — FSL-1.0-MIT from 2024-01-11 |
| 95fdf64db | LICENSE.md — FSL-1.1-MIT from 2024-03-12 |
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 2026-05-08. 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 0.22.3. Answer lives in: the release you run, set against each fixed version.
A note that does not affect this rating: it describes the project's advisory record, and no advisory in it is known to affect the surveyed commit.
| GHSA-xpmj-536r-9fc6 | 2026-05-08: GHSA-xpmj-536r-9fc6 (critical), fixed in 0.19.7: Link injection via forge integration enables arbitrary script execution |
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 · not assessable · ratings ↑Not rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it. What a person adds here.
Fit with the Acquirer
07 · not assessable · ratings ↑Not rated: structurally not assessable from a repository. What a person adds here.
Check it on the running system
5 checks against the running system follow from the findings above: what a buyer's engineer will try, how to run it first, and what to have ready. A paid survey of this repository includes them.
A paid survey of a public repository is also reviewed: a language model reads each finding against the code and withdraws only findings it judges the code contradicts, each listed with its reason. The review is a language model's reading of the findings against the code, and it can be wrong. It never adds a finding, never raises a band, and never removes a finding from a proven check or an advisory that affects the surveyed version.
What a person adds
The survey reads what the repository can show. The code cannot settle these questions, and on them this report states nothing. Each says where its answer lives: your own engineer, the company, or an assessor you choose can settle it. Questions marked measured open with something this repository shows.
Architecture & Codebase — including AI provenance
01 · full coverage- measured The tree carries design documentation (apps/lite/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 162 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 9,924 commits landed in the last year, against 5,883 the year before (+69%). 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- 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 coverageNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
- 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, with Rust alongside (47% of source files). Does your engineering organisation already run TypeScript in production, or would this be the first?
- The bulk of this system sits in crates/, apps/, packages/. Which of your existing systems would each of those have to absorb or replace?
- Nothing in the repository says how this is deployed. Is it shipped as a library, a binary or a service, and if it runs somewhere, who owns that environment?
- 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/gitbutlerapp/gitbutler/0f33b90)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 — 94 signals that ran and did not fire
Appendix: rejection log — 94 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 — 66
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 19,076 · top5 share 0.018 |
| 04.debt_markers | debt markers are sparsemarkers 311 · per kloc 0.45 · lines read 685,998 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.667 · early delete per insert 0.803 |
| 04.fixes_with_tests | fixes usually come with a testfixes 2,611 · share 0.219 · with tests 571 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.06 · code files 1,972 · compat files 118 |
| 04.dependency_redundancy | one library per job, mostly |
| 06.telemetry_presence | this repository does not deploy a running service, so instrumentation is not expected of itbasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere · files read 3,390 |
| 06.structured_logging | not a running service; structured logging is not expected of a librarybasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.healthcheck_presence | not a running service, so a health endpoint is not expectedbasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 5 · settings off 5 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 3.7 · window last 24 months · authors 162 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 162 · active 12mo 63 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 162 · directories 5 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 162 · one off share 0.451 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 162 · 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 110 |
| 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 13 · joined 17 · regular last year 28 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 6,314 · window last 24 months · with tracked 16 |
| 02.ci_presence | CI configuration is present in the working treecount 15 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 1,293 · source 3,089 · test ratio 0.419 |
| 02.release_cadence | tags are presenttags 2,410 |
| 02.conventional_commits | commit subjects generally carry contentsampled 23,322 · low content share 0.053 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 14 · with tests 3 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 6 · test files 1,910 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 15 |
| 02.revert_share | change is rarely undoneshare 0.003 · reverts 42 · recent commits 15,816 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 2 · commits since 42 · days since lockfile changed 1 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 8 · ci configs 15 · product files 1,972 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.003 · merges 6,207 · long lived 16 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.013 · commits 14,384 · over 2000 lines 191 |
| 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 5,292 · share of insertions 0.002 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 21.33 · repeat share 0.077 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 2,313 · write once share 0.212 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0062 · product files 1,955 · distinct blocks 291,057 |
| 01.swallowed_errors | errors are rarely thrown awayloc 689,361 · files 0 · per kloc 0.0 |
| 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.shell_from_strings | product code does not build shell commands from stringssites 0 |
| 05.unsafe_deserialization | no code-executing deserialiser in product codesites 0 |
| 05.tls_verification_off | no TLS verification is switched off in product codefiles 0 · sites 0 · pinned instead 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 0 |
| 05.credentials_in_deploy_config | deployment configuration references secrets, never holds themfiles 0 · sites 0 |
| 05.public_env_secret | only publishable values carry a public prefixnames 0 · sites 0 · not secrets 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_copyleft_inherited | every licence found in vendored code is permissive or weak-copyleftvendored paths 41 |
| 05.license_vendored_unlicensed | all 1 vendored components state their terms, in a licence file, their own headers or a notices filecomponents 1 · stated in headers or notices 1 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 0 · files with deprecations 29 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 358 · added in two years 257 · removed within 60 days 16 |
| 04.ci_platforms_dropped | no platform was dropped from CI in the last two years |
| 04.repository_status | the README's first screen states no end, move or freezestatements 0 |
| 02.development_elsewhere | nothing says development happens elsewhereno pr statements 0 · mirror statements 0 · replayed commit share 0.0 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 0.5 · days since last tag -1 · commits last 90 days 3,858 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 10 · on branch 239 · tags in window 249 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 28
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.telemetry_depth | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.print_logging | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.correlation_ids | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.error_reporting | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.alert_rules | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.deployed_image_floats | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.environment_branching | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.release_markers | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 01.build_reproducibility | no product Dockerfile to read |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.container_runs_as_root | no Dockerfile outside development, test and example paths |
| 05.outbound_timeouts | not a running service |
| 05.migration_reversibility | too few migrations to judge |
| 05.sql_from_strings | not a running service; a library that builds SQL is doing its job |
| 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_manifest_conflict | no packaging manifest states a licence |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | not a running service |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; OSV npm @gitbutler/no-relative-imports (an empty record for a package published here), OSV npm @gitbutler/svelte-comment-injector (an empty record for a package published here) did not |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited list |
Anyone can check this report against the authoritative record — click the stamp, or enter 738P-834J-FKXV 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/738P834JFKXV?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-10-02 · shown | borehole 0.7.10 | 12 | strong |
4 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 12 | strong |
| 2026-10-03 | borehole 0.7.12 | 12 | strong |
| 2026-10-03 | borehole 0.7.11 | 12 | strong |
| 2026-10-01 | borehole 0.7.9 | 10 | strong |
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: 312.7authenticated: False |
| 24.5s | cloned the repository to a temporary directory | depth: full |
| 44.3s | read the git history | commits: 31536tracked files: 5282 |
| 232.1s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 232.1s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 311.0s | kept the facts, never the source, for re-reading under new checks | |
| 311.0s | deleting the working copy |
Total 311.0s ·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).