Borehole · Project · free tier
hashicorp/terraform
Free reading: not for reliance
55d258b · 35,977 commits · 5,541 files
Read 2026-10-04

hashicorp/terraform: technical due diligence, read from its repository

What Borehole read in hashicorp/terraform's code and history at 55d258b: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturitystrong
Security & Reliability Postureadequate
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

What the repository says

  • Releases are cut from another branch than the one surveyed
  • LICENSE:1: The licence is BUSL-1.1: source available, not open source
  • LICENSE: Relicensed: MPL-2.0 → BUSL-1.1 (2023-08-10)
  • .github/CONTRIBUTING.md:316: states a policy on AI-generated contributions

Architecture & Codebase — including AI provenance

strong
01.6

internal/terraform/node_resource_abstract_instance.go is 3,491 lines, 151× this codebase's median file

adequate

The median source file here is 23 lines. 28 files exceed 1,000 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.

Evidence
internal/terraform/node_resource_abstract_instance.go:1 — 3,491 lines (151× median)
internal/command/meta_backend.go:1 — 3,265 lines (141× median)
internal/cloud/tfe_client_mock.go:1 — 2,611 lines (113× median)
internal/plugin6/grpc_provider.go:1 — 2,115 lines (91× median)
internal/legacy/helper/schema/schema.go:1 — 1,780 lines (77× median)

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

strong
04.38

19 files still carry code deprecated more than two years ago

adequate

19 files were marked deprecated over two years ago and still are, the oldest since Dec 2020. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.

Evidence
internal/tfplugin5/tfplugin5.pb.go — deprecated since Dec 2020
internal/legacy/helper/schema/resource_data.go — deprecated since Dec 2020
internal/tfplugin6/tfplugin6.pb.go — deprecated since Feb 2021
internal/backend/remote-state/oss/backend.go — deprecated since Oct 2021
internal/backend/remote-state/azure/backend.go — deprecated since Apr 2022
04.62

Releases are cut from another branch than the one surveyed

adequate

The newest release, v1.16.5, is not on the branch this survey read; the newest release on it is v0.13.2. The shipped product may differ from what this report describes. Survey the release branch too.

Evidence
tag v1.16.5

Security & Reliability Posture

adequate
05.1

5 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings

adequate

Strings 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.

Evidence
5 cited: private key block, where fakes are usual
05.6

1 Dockerfile runs the application as root

adequate

No 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.

Evidence
Dockerfile — runs as root
05.66

The licence is BUSL-1.1: source available, not open source

adequate

LICENSE grants BUSL-1.1: source available, not open source; production use restricted until the change date. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.

Evidence
LICENSE:1 — 92 lines, BUSL-1.1
05.60

Relicensed: MPL-2.0 → BUSL-1.1 (2023-08-10)

adequate

The root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.

Evidence
LICENSE — MPL-2.0 from 2014-07-28
LICENSE — BUSL-1.1 from 2023-08-10
05.65

6 advisories against this project in the last 24 months, 5 high or critical

adequate

The newest was published on 2026-07-28. 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 6 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 0.13.2. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 21 records name terraform with nothing tying them to this repository (CVE-2023-30618, CVE-2023-34236, CVE-2024-47083, …).

Evidence
2026-07-28: CVE-2026-14869 (high): The terraform-mcp-server before version 1.1.0 is vulnerable to a server-side request forgery issue in the streamable-HTTP transport that may allow an unauthenti
2026-07-28: CVE-2026-16496 (high): The terraform-mcp-server before version 1.1.0 is vulnerable to an authorization bypass in the streamable-HTTP stateful transport mode that may allow a user who
2026-07-28: CVE-2026-16498 (critical): The terraform-mcp-server before version 1.1.0 is vulnerable to a cross-tenant credential reuse issue in the streamable-HTTP stateless transport mode that may al
2026-07-06: CVE-2026-14468 (high): HashiCorp Terraform Enterprise contained an issue in its version control system (VCS) ingestion of registry modules that did not correctly enforce the intended
2025-11-21: CVE-2025-13357 (high): Vault’s Terraform Provider incorrectly set the default deny_null_bind parameter for the LDAP auth method to false by default, potentially resulting in an insecu

Observability & Operations

not assessable

Not rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on hashicorp/terraform: every dimension, the questions for the room, and the audit log.

Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.