55d258b · 35,977 commits · 5,541 files
Issued 2026-09-24
Nothing significant. Questions worth asking about Security & Reliability Posture, Product & Engineering Maturity.
39 checks ran across 6 assessable dimensions. 2 findings are worth checking first. 6 findings, each with evidence. One dimension cannot be assessed without an acquirer.
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.
- Words about people are today's: bands rather than exact shares, dates or day counts, and what the history measured rather than why.
- 2 findings rated significant by a check that has not yet held up in Borehole's calibration are now worth checking first.
- 4 findings from checks Borehole's calibration found wrong more often than right are no longer published.
- The file and line of 5 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 | strong | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | strong | |
| 07 | Fit with the Acquirer | not assessable |
- 3% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- 20% of commits show author/committer date divergence, which is the shape of replayed history that can drop trailers
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑internal/terraform/node_resource_abstract_instance.go is 3,491 lines, 22× this codebase's median file
adequateThe median source file here is 152 lines. 9 files exceed 1,520 lines, the largest being 3,491. 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 | internal/terraform/node_resource_abstract_instance.go:1 — 3,491 lines (22× median) |
| line-count | internal/command/meta_backend.go:1 — 3,265 lines (21× median) |
| line-count | internal/cloud/tfe_client_mock.go:1 — 2,611 lines (17× median) |
| line-count | internal/plugin6/grpc_provider.go:1 — 2,115 lines (13× median) |
| line-count | internal/legacy/helper/schema/schema.go:1 — 1,780 lines (11× 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. 11 checks ran and none fired; the rejection log below says why each did not.
Organization & Key-Person Risk
03 · strong · ratings ↑No finding. 5 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · adequate · ratings ↑314 direct dependencies in a single manifest
adequate worth checking firstgo.mod declares 314 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.
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 go.mod and the 3 other files it cites settles it. If it holds when someone checks it, this finding is significant.
| direct-dependencies | go.mod — 314 declared |
| direct-dependencies | internal/backend/remote-state/gcs/go.mod — 78 declared |
| direct-dependencies | internal/backend/remote-state/s3/go.mod — 73 declared |
| direct-dependencies | internal/backend/remote-state/kubernetes/go.mod — 69 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.
Effort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.80 to 1.93 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.
| deletions-per-insertion | first half 0.80, second half 1.93 (split 2020-07-23) |
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 ↑9 credential-shaped strings committed to the tree
adequate worth checking firstMatches for private key block appear in tracked files outside test and fixture paths. Whether these are live is not something a repository can settle, and they may well be rotated already — but they are in the history permanently, and the question a buyer must ask is what the rotation process was, not whether one string still works.
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. If it holds when someone checks it, this finding is significant.
| private key block | 5 cited: private key block pattern matched |
| 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 | 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.
Licence text does not match a standard licence
adequateLICENSE exists but its text does not match any standard licence. A bespoke or hand-edited licence is not wrong, but it cannot be cleared by recognising its name: counsel has to read it, and until they do neither side knows precisely what rights transfer with the code.
| LICENSE | LICENSE:1 — 92 lines, BUSL-1.1 |
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 ↑No finding. 3 checks ran and none fired; the rejection log below says why each did not.
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
2 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.md). 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 2,318 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.1 and 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?
- 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?
- 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 vendor/, internal/, builtin/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (Dockerfile and 267 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/hashicorp/terraform/55d258b)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 — 33 signals that ran and did not fire
Appendix: rejection log — 33 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 — 30
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 37,544 · top5 share 0.015 |
| 04.debt_markers | debt markers are sparsemarkers 384 · per kloc 0.51 · lines read 760,035 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.915 · early test per code 0.639 |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 34 |
| 06.structured_logging | a structured logging library is referencedmatches 3 |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 12.3 · window last 24 months · authors 2,318 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 2,325 · active 12mo 67 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 2,325 · directories 39 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 2,325 · one off share 0.61 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 2,325 · top share less than a quarter · top contributor last committed more than three years ago |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 302 · window last 24 months · with tracked 10 |
| 02.ci_presence | CI configuration is present in the working treecount 11 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 684 · source 2,016 · test ratio 0.339 |
| 02.release_cadence | tags are presenttags 476 |
| 02.conventional_commits | commit subjects generally carry contentsampled 28,890 · low content share 0.018 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 11 · with tests 2 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 36 · test files 1,479 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 11 |
| 02.revert_share | change is rarely undoneshare 0.004 · reverts 9 · recent commits 2,278 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 11 · commits since 21 · days since lockfile changed 5 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 8 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 21.97 · repeat share 0.166 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 37,698 · write once share 0.32 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0281 · product files 1,301 · distinct blocks 398,545 |
| 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 48 · pipe to shell 0 · unpinned third party 0 |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
Could not conclude, or did not apply — 3
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.eol_runtime | no pinned runtime version to check |
| 05.dependency_pinning | no manifest whose pinning can be read without a lockfile |
| 05.license_manifest_conflict | no packaging manifest states a licence |
Anyone can check this report against the authoritative record — click the stamp, or enter GZ78-XMK2-4A2B at borehole.dev/verify.
The code commits to the 43 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/GZ78XMK24A2B?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-24 · shown | borehole 0.4.0.dev2 | 10 | adequate |
19 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 9 | strong |
| 2026-10-03 | borehole 0.7.12 | 9 | strong |
| 2026-10-03 | borehole 0.7.11 | 9 | strong |
| 2026-10-02 | borehole 0.7.10 | 9 | strong |
| 2026-10-01 | borehole 0.7.9 | 8 | significant findings |
| 2026-09-30 | borehole 0.7.8 | 7 | adequate |
| 2026-09-29 | borehole 0.7.6 | 7 | adequate |
| 2026-09-28 | borehole 0.7.5 | 7 | adequate |
| 2026-09-28 | borehole 0.7.4 | 7 | significant findings |
| 2026-09-27 | borehole 0.7.3 | 7 | significant findings |
| 2026-09-27 | borehole 0.7.2 | 8 | significant findings |
| 2026-09-27 | borehole 0.7.1 | 8 | significant findings |
| 2026-09-26 | borehole 0.7.0 | 9 | significant findings |
| 2026-09-26 | borehole 0.6.3 | 6 | adequate |
| 2026-09-26 | borehole 0.6.2 | 6 | adequate |
| 2026-09-25 | borehole 0.6.1 | 5 | adequate |
| 2026-09-25 | borehole 0.6.0 | 16 | adequate |
| 2026-09-24 | borehole 0.4.0 | 15 | adequate |
| 2026-09-24 | borehole 0.4.0.dev1 | 10 | 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 — 6 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.4s | read repository metadata from the GitHub API | size mb: 350.9authenticated: False |
| 29.8s | cloned the repository to a temporary directory | depth: full |
| 58.9s | read the git history | commits: 35977tracked files: 5541 |
| 88.8s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 88.8s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 88.8s | deleting the working copy |
Total 88.8s ·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).