b6282f6 · 12,558 commits · 5,551 files
Issued 2026-10-01
1 advisory against this project is on CISA's known-exploited list; whether it affects the surveyed commit could not be told.
103 checks ran across 6 assessable dimensions. 2 findings are worth checking first. 13 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 05.65 1 advisory against this project is on CISA's known-exploited list; whether it affects the surveyed commit could not be told
- 04.62 Releases are cut from another branch than the one surveyed
Borehole's proprietary scoring is calibrated across hundreds of repositories. Each finding here reads significant, but its check has not yet held up often enough in that calibration to rate significant on its own. If one holds when someone checks it, it is significant.
- 3 findings from checks Borehole's calibration found wrong more often than right are no longer published.
- The file and line of 1 credential-shaped match is withheld. File and line are shown to whoever GitHub says controls this repository, signed in, and to a buyer of this report.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | 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 |
- 24% 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 ↑ui/packages/design-system/src/components/Data/KsDataTable/KsFilter.locale.ts is 5,216 lines, 77× this codebase's median file
adequateThe median source file here is 67 lines. 19 files exceed 1,000 lines, the largest being 5,216. 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 305 surveyed projects' largest files, where this check begins to count.
| line-count | ui/packages/design-system/src/components/Data/KsDataTable/KsFilter.locale.ts:1 — 5,216 lines (77× median) |
| line-count | webserver/src/main/java/io/kestra/webserver/controllers/api/ExecutionController.java:1 — 3,012 lines (44× median) |
| line-count | executor/src/main/java/io/kestra/executor/ExecutorService.java:1 — 1,889 lines (28× median) |
| line-count | core/src/main/java/io/kestra/core/services/ExecutionService.java:1 — 1,473 lines (21× median) |
| line-count | ui/src/components/inputs/LowCodeEditor.vue:1 — 1,452 lines (21× median) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Engineering Process & SDLC Maturity
02 · adequate · ratings ↑Tests are retried until they pass
adequateThe suite is configured to retry failing tests (e2e/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.
| e2e/playwright.config.ts | e2e/playwright.config.ts:38 — test retry |
| core/src/test/java/io/kestra/core/models/tasks/retrys/RandomTest.java | core/src/test/java/io/kestra/core/models/tasks/retrys/RandomTest.java:32 — test retry |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Organization & Key-Person Risk
03 · strong · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · adequate · ratings ↑Releases are cut from another branch than the one surveyed
adequateThe newest release, v2.0.4, is not on the branch this survey read; the newest release on it is v0.19.0. The shipped product may differ from what this report describes. Survey the release branch too.
| d97ca6738 | tag v2.0.4 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Security & Reliability Posture
05 · adequate · ratings ↑1 credential-shaped string in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| private key block | private key block, where fakes are usual |
| File and line are shown to whoever GitHub says controls this repository, signed in, and to a buyer of this report. |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
The build runs third-party code it does not pin
adequate18 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
| .github/workflows/e2e-scheduling.yml | .github/workflows/e2e-scheduling.yml:23 — action pinned by tag |
| .github/workflows/e2e-scheduling.yml | .github/workflows/e2e-scheduling.yml:39 — action pinned by tag |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
8 locked dependencies have published vulnerabilities, 15 high or critical in what ships
adequate worth checking first8 of 766 locked dependencies match 41 published advisories in OSV, 21 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 ui/package-lock.json settles it. If it holds when someone checks it, this finding is significant.
| ui/package-lock.json | ui/package-lock.json — axios 1.18.1: GHSA-3pq3-5fj3-cg6v (high), fixed in 1.20.0 |
| ui/package-lock.json | ui/package-lock.json — brace-expansion 5.0.9: GHSA-6j4f-fj2g-mc7p (high), fixed in 5.0.10 |
| ui/package-lock.json | ui/package-lock.json — fast-uri 3.1.5: GHSA-5jgf-p345-68v8 (high), fixed in 3.1.6 |
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 workload settings give a container the host
adequate worth checking first3 places in the deployment configuration run a container privileged or in the host's network, process or IPC namespace. A compromise of that container is a compromise of the machine, and most acquirers' security reviews block it. Node agents (network, storage, monitoring) are excluded.
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 charts/kestra/values.yaml:344 and the 1 other file it cites settles it. If it holds when someone checks it, this finding is significant.
| charts/kestra/values.yaml | charts/kestra/values.yaml:344 — privileged or host namespace |
| charts/kestra/values.yaml | charts/kestra/values.yaml:358 — privileged or host namespace |
| docker-compose-dind.yml | docker-compose-dind.yml:33 — privileged or host namespace |
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.
32 advisories against this project in the last 24 months, 18 high or critical, 1 on CISA's known-exploited list
adequate1 of them is on CISA's known-exploited list: check first whether the release you run has the fix. The newest was published on 2026-09-29. 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-5vc5-wxxq-3fjx | 2026-06-03: GHSA-5vc5-wxxq-3fjx (critical; on CISA's Known Exploited list), fixed in 1.0.45: Unauthenticated Remote Code Execution via Authentication Bypass in `AuthenticationFilter` |
| GHSA-xh2h-59mw-8qr2 | 2026-09-29: GHSA-xh2h-59mw-8qr2 (moderate), fixed in 1.3.40: Deleted namespace file content remains readable via the revision parameter |
| GHSA-hrr4-xg8h-5p6f | 2026-09-29: GHSA-hrr4-xg8h-5p6f (high), fixed in 2.0.3: Unauthenticated gRPC control plane on port 50051 exposes and mutates KV/namespace metadata and worker jobs |
| GHSA-g769-pv29-qhff | 2026-09-29: GHSA-g769-pv29-qhff (moderate), fixed in 2.0.2: Possible HTTP allowed-list regression introduced in commit 0354ddf8 |
| GHSA-9gp7-896w-m3r7 | 2026-09-29: GHSA-9gp7-896w-m3r7 (low), fixed in 2.0.1: Content-Disposition filename parameter injection in Kestra via an unvalidated `namespace` path segment on the namespace-files export endpoint |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
1 of 1 Kubernetes workloads declare no resource limits
adequate1 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| charts/kestra-starter/templates/statefulset.yaml | charts/kestra-starter/templates/statefulset.yaml — workload with no limits |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
54 places insert HTML from a variable without sanitising it
adequate54 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.
| ui/packages/design-system/src/components/Data/KsDataTable/KsBulkSelect.vue | ui/packages/design-system/src/components/Data/KsDataTable/KsBulkSelect.vue:8 — HTML from a variable |
| ui/packages/design-system/src/components/Data/KsDataTable/KsBulkSelect.vue | ui/packages/design-system/src/components/Data/KsDataTable/KsBulkSelect.vue:16 — HTML from a variable |
| ui/packages/design-system/src/components/Data/KsEmpty.vue | ui/packages/design-system/src/components/Data/KsEmpty.vue:9 — HTML from a variable |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Observability & Operations
06 · adequate · ratings ↑No structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| logging-scan | searched 5,237 files for 10 structured logging 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.
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| error reporting | no error reporter initialised |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
2 of 6 deployed images carry no version, or `latest`
adequate2 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-ci.yml | docker-compose-ci.yml:3 — image without a version |
| docker-compose-dind.yml | docker-compose-dind.yml:45 — 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
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 (docs/architecture/METRICS_GUIDELINES.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 571 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 Java codebase, with TypeScript alongside (21% of source files). Does your engineering organisation already run Java in production, or would this be the first?
- The bulk of this system sits in ui/, core/, webserver/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (Dockerfile and 5 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/kestra-io/kestra/b6282f6)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.
- d97ca67 2026-10-03 · adequate
Rejection log — 90 signals that ran and did not fire
Appendix: rejection log — 90 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 — 75
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 10,987 · top5 share 0.034 |
| 04.debt_markers | debt markers are sparsemarkers 88 · per kloc 0.14 · lines read 645,251 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.493 · early test per code 0.232 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.573 · early delete per insert 0.507 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fixes_with_tests | fixes usually come with a testfixes 3,808 · share 0.364 · with tests 1,386 |
| 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 48 |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 2,770 · compat files 0 |
| 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 51 |
| 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 47 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 3 · settings off 2 |
| 06.probes_identical | readiness and liveness are distinct, or not both setidentical 0 · workloads with both 1 |
| 06.single_replica | an autoscaler or disruption budget is definedworkloads 1 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 226 · release commits 0 · changelog commits 10 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 7.1 · window last 24 months · authors 571 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 571 · active 12mo 403 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 571 · directories 20 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 571 · one off share 0.581 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 571 · 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 533 |
| 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 23 · joined 74 · regular last year 95 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 12 · window last 24 months · with tracked 1,429 |
| 02.ci_presence | CI configuration is present in the working treecount 27 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 1,643 · source 4,378 · test ratio 0.375 |
| 02.release_cadence | tags are presenttags 603 |
| 02.conventional_commits | commit subjects generally carry contentsampled 12,382 · low content share 0.001 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 27 · with tests 3 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 7 · test files 2,210 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 27 |
| 02.revert_share | change is rarely undoneshare 0.005 · reverts 36 · recent commits 7,350 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 2 · commits since 2 · days since lockfile changed 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 9 · ci configs 27 · product files 2,770 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.013 · commits 6,818 · over 2000 lines 91 |
| 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 2,124 · share of insertions 0.0012 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 18.48 · repeat share 0.041 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 3,090 · write once share 0.247 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0074 · product files 2,735 · distinct blocks 203,707 |
| 01.swallowed_errors | errors are rarely thrown awayloc 649,805 · files 8 · per kloc 0.02 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 1 |
| 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.container_runs_as_root | every shipped Dockerfile drops to a non-root user or builds on a non-root base imagedockerfiles 1 |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.sql_from_strings | no SQL is assembled from strings in product codefiles 0 · sites 0 · value interpolated 0 |
| 05.shell_from_strings | product code does not build shell commands from stringssites 0 |
| 05.unsafe_deserialization | no code-executing deserialiser in product codesites 0 |
| 05.tls_verification_off | no TLS verification is switched off in product codefiles 0 · sites 0 · pinned instead 0 |
| 05.credentials_in_deploy_config | deployment configuration references secrets, never holds themfiles 0 · sites 0 |
| 05.source_maps_shipped | production builds do not publish source mapssites 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.license_grant_unclear | the licence is recognisable as Apache-2.0class permissive · license Apache-2.0 |
| 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 2 · files with deprecations 106 |
| 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 1.0 · days since last tag 0 · commits last 90 days 1,464 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
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.feature_flags | no feature-flag service; flags may live elsewhere |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.outbound_timeouts | not assessed for Java, the language the product is written in: this check's patterns read other languages only |
| 05.migration_reversibility | too few migrations to judge |
| 05.public_env_secret | not assessed for Java, 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_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 |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | one API version is served, or none |
| 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 XMWP-TDDA-D8FW 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/XMWPTDDAD8FW?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-01 · shown | borehole 0.7.9 | 16 | adequate |
5 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 16 | strong |
| 2026-10-03 | borehole 0.7.12 | 16 | strong |
| 2026-10-03 | borehole 0.7.11 | 16 | strong |
| 2026-10-02 | borehole 0.7.10 | 16 | strong |
| 2026-09-30 | borehole 0.7.8 | 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 — 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: 9308f48b62c9dddf |
| 12.9s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 12.9s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
Total 12.9s ·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).