Read 2026-10-22
hashicorp/packer: technical due diligence, read from its repository
What Borehole read in hashicorp/packer's code and history at bc68036: 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.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | adequate |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not 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 sourceLICENSE: Relicensed: MPL-2.0 → BUSL-1.1 (2023-08-10)
Architecture & Codebase — including AI provenance
adequatecommand/hcl2_upgrade.go is 1,488 lines, 27× this codebase's median file
adequateThe median source file here is 55 lines. 4 files exceed 1,000 lines, the largest being 1,488. 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.
command/hcl2_upgrade.go:1 — 1,488 lines (27× median) |
packer/core.go:1 — 1,066 lines (19× median) |
hcl2template/types.packer_config.go:1 — 1,052 lines (19× median) |
packer/plugin-getter/plugins.go:1 — 1,025 lines (18× median) |
2 base images float: no version, or `latest`
adequate2 of 4 `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.
Dockerfile:22 — base image without a version |
Dockerfile:34 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.44 to 1.31 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.
| first half 0.44, second half 1.31 (split 2020-01-06) |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v1.16.2, is not on the branch this survey read; the newest release on it is v1.16.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.16.2 |
Security & Reliability Posture
adequate1 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.
Dockerfile — runs as root |
The licence is BUSL-1.1: source available, not open source
adequateLICENSE 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.
LICENSE:1 — 92 lines, BUSL-1.1 |
Relicensed: MPL-2.0 → BUSL-1.1 (2023-08-10)
adequateThe 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.
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-08-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 1 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 1.16.0. Answer lives in: the release you run, set against each fixed version.
| 2026-08-17: CVE-2026-19589 (high): Packer up to 1.15.4 is vulnerable to an issue in the third-party plugin installer that may allow unintended file system modification and could lead to code exec |
Observability & Operations
not assessableNot 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 assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on hashicorp/packer: 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.