69ec5df · 2,701 commits · 679 files
Issued 2026-09-27
Reads strong: 3 of 5 rated dimensions are strong, 2 are adequate and none is significant.
99 checks ran across 6 assessable dimensions. Architecture & Codebase — including AI provenance and Security & Reliability Posture are adequate. 2 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- The project does not take pull requests .github/CONTRIBUTING.md:171
- states a policy on AI-generated contributions .github/CONTRIBUTING.md:28
- 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 | adequate | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | strong | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | not assessable | |
| 07 | Fit with the Acquirer | not assessable |
- 18% 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
- deep scan blamed 677 of 678 counted files
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑caddyconfig/httpcaddyfile/httptype.go is 1,931 lines, 11× this codebase's median file
adequateThe median source file here is 164 lines. 4 files exceed 1,640 lines, the largest being 1,931. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
| line-count | caddyconfig/httpcaddyfile/httptype.go:1 — 1,931 lines (11× median) |
| line-count | modules/caddyhttp/reverseproxy/reverseproxy.go:1 — 1,903 lines (11× median) |
| line-count | modules/caddyhttp/matchers.go:1 — 1,796 lines (10× median) |
| line-count | modules/caddyhttp/reverseproxy/caddyfile.go:1 — 1,702 lines (10× 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 · strong · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · strong · ratings ↑No finding. 19 checks ran and none fired; the rejection log below says why each did not.
Security & Reliability Posture
05 · adequate · ratings ↑5 locked dependencies have published vulnerabilities
adequate5 of 169 locked dependencies match 5 published advisories in OSV. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
| go.mod | go.mod — go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc v0.20.0: GHSA-w34q-cm8f-9c5x (moderate), fixed in 0.21.0 |
| go.mod | go.mod — go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.44.0: GHSA-8wmf-6v46-5gfg (low), fixed in 1.45.0 |
| go.mod | go.mod — go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.44.0: GHSA-8wmf-6v46-5gfg (low), fixed in 1.45.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.
Observability & Operations
06 · not assessable · ratings ↑Not rated: only 4 of 15 checks could reach a conclusion here; the rest do not apply to this repository or could not read it. What a person adds here.
Fit with the Acquirer
07 · not assessable · ratings ↑Not rated: structurally not assessable from a repository. What a person adds here.
Check it on the running system
1 check 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 241 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 a quarter or more 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- 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.
- What has actually broken, how often, and how badly?
- What did external testing find, and was it fixed?
- What is the SOC 2, ISO 27001 or GDPR status, and where is the evidence?
Observability & Operations
06 · partial coverageNot rated: only 4 of 15 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
- Are the dashboards opened, the alerts acknowledged and the pages answered?
- Are the service-level objectives actually met?
- Who carries the pager, and how often does it go off?
- What does it cost to run, and how much headroom is there?
Fit with the Acquirer
07 · none coverageNot rated: structurally not assessable from a repository.
- This is primarily a Go codebase. Does your engineering organisation already run Go in production, or would this be the first?
- The bulk of this system sits in modules/, caddytest/, caddyconfig/. Which of your existing systems would each of those have to absorb or replace?
- Nothing in the repository says how this is deployed. Is it shipped as a library, a binary or a service, and if it runs somewhere, who owns that environment?
- What is your tolerance for the findings above remaining unaddressed for the first two quarters after close, given everything else that will compete for this team's time?
- Which of these systems duplicate yours, and which get retired?
- What will integration cost, and in what order?
- Where does the team land in your organisation, and who reports to whom?
- Are there earn-outs, retention packages or contractor IP to assign?
- Do customer contracts limit hosting, regions or vendors?
A human assessment is Borehole's own paid service, €12,000+ (total price is determined per engagement; travel billed at cost). It is not independent of this report: the same business produced both. It is a separate contract, with its own scope, terms and reliance.
Embed the badge
Tied to this commit and this date, and it fades after 90 days — an honest badge is one that expires. A repository with significant findings gets a neutral "read" badge rather than a red one: the library is where the range is visible, not someone else's README.
[](/r/caddyserver/caddy/69ec5df)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 — 97 signals that ran and did not fire
Appendix: rejection log — 97 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 — 65
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 952 · top5 share 0.133 |
| 04.debt_markers | debt markers are sparsemarkers 85 · per kloc 0.74 · lines read 115,619 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.741 · early test per code 0.21 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.388 · early delete per insert 0.36 |
| 04.fixes_with_tests | fixes usually come with a testfixes 119 · share 0.454 · with tests 54 |
| 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 222 · compat files 0 |
| 06.telemetry_presence | this repository does not deploy a running service, so instrumentation is not expected of itbasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere · files read 428 |
| 06.structured_logging | not a running service; structured logging is not expected of a librarybasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.healthcheck_presence | not a running service, so a health endpoint is not expectedbasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 7.5 · window last 24 months · authors 442 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 442 · active 12mo 123 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 442 · directories 5 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 442 · one off share 0.744 |
| 03.contributor_attrition | the dominant contributor is still activeauthors 442 · top share a quarter or more · top contributor last committed between three and six months ago |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 183 |
| 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 12 · regular last year 19 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 17 |
| 02.ci_presence | CI configuration is present in the working treecount 8 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 140 · source 362 · test ratio 0.387 |
| 02.release_cadence | tags are presenttags 154 |
| 02.conventional_commits | commit subjects generally carry contentsampled 2,683 · low content share 0.003 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 8 · with tests 1 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 423 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 8 |
| 02.revert_share | change is rarely undoneshare 0.005 · reverts 3 · recent commits 579 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 1 · commits since 12 · days since lockfile changed 9 |
| 02.flaky_test_markers | tests are not retried until they passtest retries 0 · suite retries 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 2 · ci configs 8 · product files 222 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.002 · commits 509 · over 2000 lines 1 |
| 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 360 · share of insertions 0.0018 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 16.3 · repeat share 0.024 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 238 · write once share 0.164 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0062 · product files 222 · distinct blocks 41,216 |
| 01.swallowed_errors | errors are rarely thrown awayloc 116,020 · 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.committed_secrets | no credential-shaped strings outside test and fixture pathsnote the working tree only; the history is 05.5 · patterns 8 · files read 428 |
| 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.supply_chain_pinning | third-party build steps are pinned, or fewaction refs 47 · pipe to shell 0 · unpinned third party 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.privileged_workloads | no workload runs privileged or in the host's namespacessites 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 |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 0 · files with deprecations 8 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 263 · added in two years 49 · removed within 60 days 0 |
| 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 |
| 05.licence_changes | the root licence has not changed in the history readlicence versions 1 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 23.0 · days since last tag 115 · commits last 90 days 87 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 9 · on branch 98 · tags in window 107 |
| 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 — 32
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 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.telemetry_depth | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.print_logging | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.correlation_ids | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.error_reporting | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.alert_rules | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.deployed_image_floats | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.environment_branching | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.release_markers | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 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.dependency_pinning | no manifest whose pinning can be read without a lockfile |
| 05.container_runs_as_root | no Dockerfile to read |
| 05.outbound_timeouts | not a running service |
| 05.migration_reversibility | too few migrations to judge |
| 05.sql_from_strings | not a running service; a library that builds SQL is doing its job |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.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 | not a running service |
Anyone can check this report against the authoritative record — click the stamp, or enter 4D2R-JS5M-9PMH at borehole.dev/verify.
The code commits to the 103 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/4D2RJS5M9PMH?via=badge)
A survey is a reading by a particular version of the assessor. Older readings are kept rather than replaced, because a verification mark attests to the survey it was issued for — overwriting one would make every code already in circulation read as tampered.
| Read | Assessor | Findings | Band |
|---|---|---|---|
| 2026-09-27 · shown | borehole 0.7.2 | 6 | strong |
12 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 6 | strong |
| 2026-10-03 | borehole 0.7.12 | 6 | strong |
| 2026-10-03 | borehole 0.7.11 | 6 | strong |
| 2026-10-02 | borehole 0.7.10 | 6 | strong |
| 2026-10-01 | borehole 0.7.9 | 6 | strong |
| 2026-09-30 | borehole 0.7.8 | 6 | strong |
| 2026-09-29 | borehole 0.7.6 | 6 | strong |
| 2026-09-28 | borehole 0.7.5 | 6 | strong |
| 2026-09-28 | borehole 0.7.4 | 6 | strong |
| 2026-09-27 | borehole 0.7.3 | 5 | strong |
| 2026-09-27 | borehole 0.7.1 | 6 | strong |
| 2026-09-26 | borehole 0.7.0 | 6 | strong |
Where this scan ran
This scan ran on ordinary cloud infrastructure (cloud-run), not in a hardware-isolated confidential VM. Nothing about it is attested by Google.
What an attested survey proves, and what it does not.
What this scan did with the repository — 7 steps
Written by the steps themselves as they ran, not described afterwards. A hand-written account of a data flow drifts the first time somebody changes the flow and not the account.
| At | Step | Detail |
|---|---|---|
| 0.0s | read repository metadata from the GitHub API | authenticated: False |
| 4.0s | cloned the repository to a temporary directory | depth: full |
| 5.4s | read the git history | commits: 2701tracked files: 679 |
| 41.8s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 41.8s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 54.0s | kept the facts, never the source, for re-reading under new checks | |
| 54.0s | deleting the working copy |
Total 54.0s ·source content sent off this machine: none · calls to a language model: 0 · the clone was deleted when the survey ended
An automated reading of a repository's code and its history up to one commit, with public advisory records. It may be wrong, it is not legal, financial, investment or security advice, and it does not replace diligence by a qualified person. It is provided for information: nobody may rely on it (Borehole's terms, section 3).