9ab67e9 · 7,637 commits · 2,805 files
Issued 2026-10-28
Nothing significant. Questions worth asking about Security & Reliability Posture, Observability & Operations.
105 checks ran across 6 assessable dimensions. None found a significant problem; 4 raised something worth a question. 12 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 03.60 The project says one person maintains it SECURITY-SELF-ASSESSMENT.md:452
- 04.62 Releases are cut from another branch than the one surveyed
- names OpenSSF README.md:5
- names CNCF README.md:36
- names Cloud Native Computing Foundation README.md:169
- 1 finding from checks Borehole's calibration found wrong more often than right is no longer published.
- The file and line of 3 credential-shaped matches are withheld. File and line are shown to whoever GitHub says controls this repository, signed in, and to a buyer of this report.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | adequate | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 74% of non-merge commits carry any trailer at all
- no widespread author/committer date divergence
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑11 base images float: no version, or `latest`
adequate11 of 11 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
| docker-images/base/Dockerfile | docker-images/base/Dockerfile:4 — base image without a version |
| docker-images/base/Dockerfile | docker-images/base/Dockerfile:9 — base image without a version |
| docker-images/base/Dockerfile | docker-images/base/Dockerfile:78 — base 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.
operator-common/src/main/java/io/strimzi/operator/common/ReconciliationLogger.java is 8,459 lines, 83× this codebase's median file
adequateThe median source file here is 101 lines. 7 files exceed 1,010 lines, the largest being 8,459. 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 | operator-common/src/main/java/io/strimzi/operator/common/ReconciliationLogger.java:1 — 8,459 lines (83× median) |
| line-count | cluster-operator/src/main/java/io/strimzi/operator/cluster/model/KafkaCluster.java:1 — 2,115 lines (20× median) |
| line-count | cluster-operator/src/main/java/io/strimzi/operator/cluster/operator/assembly/KafkaRebalanceAssemblyOperator.java:1 — 1,473 lines (14× median) |
| line-count | crd-generator/src/main/java/io/strimzi/crdgenerator/CrdGenerator.java:1 — 1,329 lines (13× median) |
| line-count | cluster-operator/src/main/java/io/strimzi/operator/cluster/operator/assembly/AbstractConnectOperator.java:1 — 1,295 lines (12× 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 ↑No finding. 16 checks ran and none fired; the rejection log below says why each did not.
Organization & Key-Person Risk
03 · adequate · ratings ↑The project says one person maintains it
adequateIts own files say so. Whatever the commit counts show, the project describes itself as depending on one person.
| SECURITY-SELF-ASSESSMENT.md | SECURITY-SELF-ASSESSMENT.md:452 — says it has a single maintainer |
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 · strong · ratings ↑Effort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.49 to 0.76 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| deletions-per-insertion | first half 0.49, second half 0.76 (split 2021-08-01) |
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.
Releases are cut from another branch than the one surveyed
adequateThe newest release, 1.3.0, is not on the branch this survey read; the newest pre-release on it is 0.1.0-rc3. The shipped product may differ from what this report describes. Survey the release branch too.
A note that does not affect this rating: notes like it are common in well-run projects.
| 0d138c48b | tag 1.3.0 |
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 ↑3 credential-shaped strings 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 | 3 cited: 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.
1 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
| no-USER-instruction | docker-images/base/Dockerfile — runs as root |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
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/osps-baseline.yml | .github/workflows/osps-baseline.yml:54 — action pinned by tag |
| .github/workflows/github-actions-integration.yml | .github/workflows/github-actions-integration.yml:56 — 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.
5 advisories against this project in the last 24 months, 3 high or critical
adequateThe newest was published on 2026-06-17. 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 3 of them are fixed in the code you ship could not be told from this history. 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-r427-j2h7-wv3m | 2026-06-17: GHSA-r427-j2h7-wv3m (moderate), fixed in 1.0.1: Unrestricted access to all Secrets within namespace watched by the Topic operator |
| GHSA-mw9r-p8xp-wx96 | 2026-06-17: GHSA-mw9r-p8xp-wx96 (high), fixed in 1.0.1: Cross-namespace privilege escalation via `Kafka.spec.entityOperator` |
| GHSA-2qwx-rq6j-8r6j | 2026-02-19: GHSA-2qwx-rq6j-8r6j (high), fixed in 0.50.1: All CAs from a custom CA chain consisting of multiple CAs are trusted for mTLS user authentication |
| GHSA-6x85-j2f7-4xc5 | 2026-02-19: GHSA-6x85-j2f7-4xc5 (moderate), fixed in 0.50.1: All CAs from CA chain will be trusted in Kafka Connect and Kafka MirrorMaker 2 target clusters |
| GHSA-xrhh-hx36-485q | 2025-12-05: GHSA-xrhh-hx36-485q (high), fixed in 0.49.1: Unrestricted access to all Secrets in the same Kubernetes namespace from Kafka Connect and MirrorMaker 2 operands |
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 2,233 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.
Readiness and liveness probes are identical in 6 of 16 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
| install/drain-cleaner/certmanager/060-Deployment.yaml | install/drain-cleaner/certmanager/060-Deployment.yaml — same probe endpoint twice |
| install/drain-cleaner/kubernetes/060-Deployment.yaml | install/drain-cleaner/kubernetes/060-Deployment.yaml — same probe endpoint twice |
| install/drain-cleaner/openshift/060-Deployment.yaml | install/drain-cleaner/openshift/060-Deployment.yaml — same probe endpoint twice |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
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.
A note that does not affect this rating: notes like it are common in well-run projects.
| 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.
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
7 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 (operator-common/src/main/java/io/strimzi/operator/common/controller/DESIGN.md and 4 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 355 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 05.5 found credential-shaped strings in this repository. Was each one revoked at the provider? Deleting it from the code revokes nothing; only the provider's audit log shows that it was.
- measured No threat model is in the tree of what looks like a running service. Does one exist elsewhere, and who owns it?
- measured Infrastructure code (helm-charts/helm3/strimzi-kafka-operator/Chart.yaml and 1 more) last changed 15 months before the newest commit, while 899 commits landed. Is the infrastructure now changed by hand? Compare the live account with the code.
- 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 Alert rules are defined in the repository. 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. Does your engineering organisation already run Java in production, or would this be the first?
- The bulk of this system sits in cluster-operator/, systemtest/, packaging/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (cluster-operator/src/main/java/io/strimzi/operator/cluster/model/KafkaConnectDockerfile.java 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/strimzi/strimzi-kafka-operator/9ab67e9)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 — 93 signals that ran and did not fire
Appendix: rejection log — 93 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 10,641 · top5 share 0.031 |
| 04.debt_markers | debt markers are sparsemarkers 32 · per kloc 0.06 · lines read 519,489 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 1.716 · early test per code 1.179 |
| 04.fixes_with_tests | fixes usually come with a testfixes 188 · share 0.356 · with tests 67 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 889 · compat files 0 |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 160 |
| 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 1 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.alert_rules | alert rules are defined as codealert files 18 |
| 06.deployed_image_floats | every deployed image names a versionimages 2 · floating 0 |
| 06.single_replica | an autoscaler or disruption budget is definedworkloads 16 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 26 · release commits 0 · changelog commits 113 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 10.5 · window last 24 months · authors 355 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 355 · active 12mo 82 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 355 · directories 17 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 355 · one off share 0.631 |
| 03.contributor_attrition | the dominant contributor is still activeauthors 355 · top share a quarter or more · top contributor last committed within the last three months |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 117 |
| 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 2 · joined 9 · regular last year 21 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 0 |
| 02.ci_presence | CI configuration is present in the working treecount 12 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 440 · source 1,314 · test ratio 0.335 |
| 02.release_cadence | tags are presenttags 184 |
| 02.conventional_commits | commit subjects generally carry contentsampled 7,494 · low content share 0.006 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 12 · with tests 3 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 2 · test files 677 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 12 |
| 02.revert_share | change is rarely undoneshare 0.0 · reverts 0 · recent commits 1,258 |
| 02.flaky_test_markers | tests are not retried until they passtest retries 1 · suite retries 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 23 · ci configs 12 · product files 889 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.036 · commits 1,095 · over 2000 lines 39 |
| 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 215 · share of insertions 0.0001 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 25.32 · repeat share 0.011 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 1,270 · write once share 0.233 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0133 · product files 874 · distinct blocks 66,110 |
| 01.swallowed_errors | errors are rarely thrown awayloc 521,445 · 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.license_present | a licence file is presentfound True |
| 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.resource_limits | every workload declares limitsworkloads 16 · without limits 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.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 96 |
| 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 4.0 · days since last tag 19 · commits last 90 days 190 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 24
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.dependency_sprawl | no recognised dependency manifest found |
| 04.eol_runtime | no pinned runtime version to check |
| 04.schema_churn | no schema migrations to read |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.print_logging | not assessed for Java: its logger calls are not read |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 02.dependency_update_cadence | no lockfile to date |
| 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.dependency_pinning | no manifest whose pinning can be read without a lockfile |
| 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.known_vulnerabilities | not assessed for Maven: this survey does not read their dependency files |
| 05.public_env_secret | not a frontend |
| 05.unsafe_html | not a frontend |
| 05.source_maps_shipped | not a frontend |
| 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 |
| 04.dependency_churn | few dependencies were added and dropped within 60 days |
| 05.project_advisories | could not tell whether 3 published advisories affect the surveyed code: its version could not be placed |
Anyone can check this report against the authoritative record — click the stamp, or enter NHM2-KHHF-2E84 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/NHM2KHHF2E84?via=badge)
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: 92.0authenticated: False |
| 13.3s | cloned the repository to a temporary directory | depth: full |
| 26.3s | read the git history | commits: 7637tracked files: 2805 |
| 189.2s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 189.2s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 294.5s | kept the facts, never the source, for re-reading under new checks | |
| 294.5s | deleting the working copy |
Total 294.5s ·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).