df02939 · 3,635 commits · 4,968 files
Issued 2026-10-04
Nothing significant. Questions worth asking about Security & Reliability Posture, Engineering Process & SDLC Maturity.
102 checks ran across 6 assessable dimensions. 1 finding is worth checking first. 15 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- states a policy on AI-generated contributions .github/pull_request_template.md:45
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 47 locked dependencies have published vulnerabilities, 11 high or critical in what ships
- 4 findings from checks Borehole's calibration found wrong more often than right are no longer published.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | strong | |
| 07 | Fit with the Acquirer | not assessable |
- 30% 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 · strong · ratings ↑sdks/python/hatchet_sdk/clients/rest/api/workflow_api.py is 8,243 lines, 94× this codebase's median file
adequateThe median source file here is 87 lines. 86 files exceed 1,000 lines, the largest being 8,243. 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 | sdks/python/hatchet_sdk/clients/rest/api/workflow_api.py:1 — 8,243 lines (94× median) |
| line-count | sdks/python/hatchet_sdk/clients/rest/api/tenant_api.py:1 — 5,619 lines (64× median) |
| line-count | pkg/repository/task.go:1 — 5,345 lines (61× median) |
| line-count | pkg/client/cloud/rest/gen.go:1 — 4,983 lines (57× median) |
| line-count | pkg/repository/sqlcv1/olap.sql.go:1 — 4,659 lines (53× 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 ↑6% of recent commits change more than 2,000 lines
adequate114 of 1920 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 | 114 commits over 2,000 lines |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (sdks/typescript/src/v1/client/worker/batch.test.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.
| sdks/typescript/src/v1/client/worker/batch.test.ts | sdks/typescript/src/v1/client/worker/batch.test.ts:84 — 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 · adequate · ratings ↑Bus factor 1: recent work is concentrated in one contributor
adequateIn the last 24 months, one contributor authored more than half of 2,057 non-merge commits among 72 authors; across all history, more than half of 2,685. This is the single most expensive thing to discover after closing, and the repository cannot tell you whether that person is part of the transaction.
| git shortlog -sn | last 24 months: top author more than half of 2,057 commits; bus factor 1; 72 authors |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Product & Engineering Maturity
04 · adequate · ratings ↑102 direct dependencies in a single manifest
adequatego.mod declares 102 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 | go.mod — 102 declared |
| direct-dependencies | frontend/app/package.json — 66 declared |
| direct-dependencies | sdks/typescript/package.json — 15 declared |
| direct-dependencies | sdks/python/pyproject.toml — 12 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.
19% of bug fixes add or change a test
adequateOf 1075 fixes in the last 24 months, 206 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| fix commits touching tests | 206 of 1075 |
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 ↑47 locked dependencies have published vulnerabilities, 11 high or critical in what ships
adequate worth checking first47 of 2,325 locked dependencies match 153 published advisories in OSV, 78 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.
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 sdks/python/poetry.lock settles it. If it holds when someone checks it, this finding is significant.
| sdks/python/poetry.lock | sdks/python/poetry.lock — anyio 4.13.0: GHSA-82r6-8w77-94w6 (critical), fixed in 4.14.2; an optional extra |
| sdks/python/poetry.lock | sdks/python/poetry.lock — pyjwt 2.13.0: GHSA-ffc3-869f-jxw9 (critical), fixed in 2.14.0; an optional extra |
| sdks/python/poetry.lock | sdks/python/poetry.lock — aiohttp 3.14.1: GHSA-cq5v-8q36-5273 (high), fixed in 3.14.3 |
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.
| frontend/app/vite.config.ts | frontend/app/vite.config.ts:53 — 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.
8 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-09-04. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries.
| GHSA-992g-9cr3-vm5x | 2026-09-04: GHSA-992g-9cr3-vm5x (moderate), fixed in 0.106.1: Hatchet DurableTask WorkerStatus gRPC resolves caller-supplied durable-task UUIDs via ListSatisfiedEntries with no tenant_id filter |
| GHSA-9q4h-f4x5-ffq8 | 2026-09-04: GHSA-9q4h-f4x5-ffq8 (low), fixed in 0.95.3: Hatchet: Cross-tenant durable callback payload disclosure in Hatchet V1 Dispatcher |
| GHSA-6rg8-xpvg-m49w | 2026-08-03: GHSA-6rg8-xpvg-m49w (low), fixed in 0.101.0: Authentication rate-limit bypass via spoofed proxy headers enables unlimited password attempts |
| GO-2026-6535 | 2026-06-30: GO-2026-6535 (high): Hatchet - Unauthenticated OAuth state CSRF / login-CSRF via empty-state collision in ValidateOAuthState in hatchet in github.com/hatchet-dev/hatchet |
| GO-2026-6565 | 2026-06-30: GO-2026-6565 (moderate): Hatchet: SSRF via Unsigned UnsubscribeURL in SNS UnsubscribeConfirmation Handler in hatchet-dev/hatchet |
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 third-party CI action is referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 4 steps pipe a download straight into a shell. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
A note that does not affect this rating: notes like it are common in well-run projects.
| .github/workflows/sdk-ruby.yml | .github/workflows/sdk-ruby.yml:299 — action pinned by tag |
| .github/workflows/cli-release.yaml | .github/workflows/cli-release.yaml:68 — 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.
10 outbound calls can wait forever
adequate10 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| api/v1/server/handlers/slack-app/oauth_callback.go | api/v1/server/handlers/slack-app/oauth_callback.go:47 — outbound call without a timeout |
| api/v1/server/handlers/users/google_oauth_callback.go | api/v1/server/handlers/users/google_oauth_callback.go:157 — outbound call without a timeout |
| internal/integrations/ingestors/sns/sns.go | internal/integrations/ingestors/sns/sns.go:123 — outbound call without a timeout |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
12 SQL statements built from strings
adequate12 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| pkg/repository/olap.go | pkg/repository/olap.go:547 — SQL built from a string |
| pkg/repository/olap.go | pkg/repository/olap.go:563 — SQL built from a string |
| pkg/repository/olap.go | pkg/repository/olap.go:574 — 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.
4 shell commands built from strings
adequate4 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.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| sdks/typescript/jest.e2e-global-setup.ts | sdks/typescript/jest.e2e-global-setup.ts:14 — command run through a shell |
| sdks/typescript/jest.e2e-global-setup.ts | sdks/typescript/jest.e2e-global-setup.ts:16 — command run through a shell |
| sdks/typescript/jest.e2e-global-teardown.ts | sdks/typescript/jest.e2e-global-teardown.ts:14 — 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.
1 vendored component with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| hack/proto/vendor/google | hack/proto/vendor/google — 1 tracked files, no licence file |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Observability & Operations
06 · strong · ratings ↑3 of 11 deployed images carry no version, or `latest`
adequate3 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.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| docker-compose.infra.yml | docker-compose.infra.yml:3 — image without a version |
| docker-compose.infra.yml | docker-compose.infra.yml:21 — image without a version |
| docker-compose.infra.yml | docker-compose.infra.yml:37 — 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.
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
6 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 2,728 product files. Where does the design live, and who holds it?
- Is the architecture right for the next three years of the product?
- Were the home-grown components reasonable choices when they were made, and are they now?
Engineering Process & SDLC Maturity
02 · high coverage- Is review real or a rubber stamp? Comment depth and time to approve need the pull request history.
- Is delivery planned and measured, or heroic?
- How are incidents run, reviewed and learned from?
Organization & Key-Person Risk
03 · partial coverage- measured One contributor authored more than half of the commits in this history. Is that person part of the transaction, and for how long after it?
- Who mentors whom, and would that survive a departure?
- Can the team grow, and who stands behind the top three contributors?
- Is the seniority mix sound, and will pay survive your salary bands?
- Is the pace sustainable? Commit times cannot say: git keeps no reliable local time.
- Does the team want to stay after close?
- How are decisions made and disagreements resolved?
Product & Engineering Maturity
04 · minimal coverage- measured 1,294 commits landed in the last year, against 761 the year before (+70%). 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 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 Go codebase, with TypeScript alongside (29% of source files). Does your engineering organisation already run Go in production, or would this be the first?
- The bulk of this system sits in pkg/, frontend/, sdks/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (docker-compose.infra.yml and 2 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/hatchet-dev/hatchet/df02939)If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
Rejection log — 87 signals that ran and did not fire
Appendix: rejection log — 87 signals that ran and did not fire
Published on purpose. A signal that looked and decided not to fire has told you something, and this is the calibration data behind every threshold above.
Looked, and found nothing — 69
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 11,603 · top5 share 0.021 |
| 04.debt_markers | debt markers are sparsemarkers 339 · per kloc 0.39 · lines read 871,235 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.184 · early test per code 0.025 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.662 · early delete per insert 0.232 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.schema_churn | columns, once added, staydropped within 90 days 0 · columns added last year 81 |
| 04.compat_layers | little code is kept for the old wayshare 0.008 · code files 2,479 · compat files 20 |
| 04.dependency_redundancy | one library per job, mostly |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 223 |
| 06.structured_logging | a structured logging library is referencedmatches 221 |
| 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 45 |
| 06.error_reporting | an error reporter is initialisedinitialised 1 · config files 0 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 6 · settings off 4 |
| 06.environment_branching | environment differences live in configurationsites 1 |
| 06.release_markers | releases are markedtags last year 792 · release commits 1 · changelog commits 190 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.active_contributors | more than one contributor active in the trailing yearall time 85 · active 12mo 50 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 85 · directories 10 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 85 · one off share 0.612 |
| 03.contributor_attrition | the dominant contributor is still activeauthors 85 · top share more than half · top contributor last committed within the last three months |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 72 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.bus_factor_trend | the team has not narrowed to one person |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 4 · window last 24 months · with tracked 7 |
| 02.ci_presence | CI configuration is present in the working treecount 33 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 553 · source 2,977 · test ratio 0.186 |
| 02.release_cadence | tags are presenttags 1,412 |
| 02.conventional_commits | commit subjects generally carry contentsampled 3,625 · low content share 0.004 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 33 · with tests 16 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 7 · test files 561 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 33 |
| 02.revert_share | change is rarely undoneshare 0.007 · reverts 14 · recent commits 2,057 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 13 · commits since 17 · days since lockfile changed 2 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 11 · ci configs 33 · product files 2,479 |
| 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 42,884 · share of insertions 0.0137 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 19.47 · repeat share 0.007 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 2,530 · write once share 0.368 |
| 01.swallowed_errors | errors are rarely thrown awayloc 875,785 · files 4 · per kloc 0.01 |
| 01.unfinished_migration | no language migration is stalled halfway |
| 01.weights_in_git | no model weights are committedfiles 0 |
| 05.committed_secrets | no credential-shaped strings outside test and fixture pathsnote the working tree only; the history is 05.5 · patterns 8 · files read 4,560 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.dependency_pinning | a lockfile is committed, so builds are reproduciblelockfile True |
| 05.license_present | a licence file is presentfound True |
| 05.secrets_in_history | no credential-shaped string was ever added outside test and fixture pathspatterns 8 · truncated False · added lines 2,772,497 |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.unsafe_deserialization | no code-executing deserialiser in product codesites 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 0 |
| 05.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 1 |
| 05.license_grant_unclear | the licence is recognisable as MITclass permissive · license MIT |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.api_versions_coexisting | one API version is served, or none |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 3 · files with deprecations 107 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 378 · added in two years 324 · removed within 60 days 3 |
| 04.ci_platforms_dropped | no platform was dropped from CI in the last two years |
| 04.repository_status | the README's first screen states no end, move or freezestatements 0 |
| 02.development_elsewhere | nothing says development happens elsewhereno pr statements 0 · mirror statements 0 · replayed commit share 0.0 |
| 05.licence_changes | the root licence has not changed in the history readlicence versions 1 · unreleased changes 0 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 0.0 · days since last tag -3 · commits last 90 days 482 |
| 04.release_branch | the newest release, v0.110.2, was made after the surveyed commit on the branch surveyedelsewhere 334 · on branch 1,002 · tags in window 1,345 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 18
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.joiners_and_leavers | too few regular contributors to see a trend |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.build_reproducibility | no product Dockerfile to read |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.container_runs_as_root | no Dockerfile to read |
| 05.migration_reversibility | too few migrations to judge |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.public_env_secret | not assessed for Go, the language the product is written in: this check's patterns read other languages only |
| 05.unsafe_html | not assessed for Go, the language the product is written in: this check's patterns read other languages only |
| 05.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 |
Anyone can check this report against the authoritative record — click the stamp, or enter 4MDQ-7C2H-6QHF 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/4MDQ7C2H6QHF?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-04 · shown | borehole 0.7.13 | 19 | adequate |
5 earlier (show)
| 2026-10-03 | borehole 0.7.12 | 19 | adequate |
| 2026-10-03 | borehole 0.7.11 | 19 | adequate |
| 2026-10-02 | borehole 0.7.10 | 19 | adequate |
| 2026-10-01 | borehole 0.7.9 | 19 | adequate |
| 2026-09-30 | borehole 0.7.8 | 19 | 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 — 3 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 | re-read from the facts kept at the last survey; nothing was cloned | facts version: 1d7c04ef8dca7905 |
| 22.6s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 22.6s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
Total 22.6s ·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).