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

The median source file here is 84 lines. 68 files exceed 1,000 lines, the largest being 7,965. 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.

The suite is configured to retry failing tests (ui/playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.

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

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

ui/.env is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.

1 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; 2 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.

3 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.

24 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.

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.

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.

The newest was published on 2026-10-01. 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 25 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.2.0. Answer lives in: the release you run, set against each fixed version. GHSA-9g4h-h484-3578 (high), GHSA-8f82-53h8-2p34 (high), GHSA-g233-2p4r-3q7v (high) are fixed in the surveyed commit; which release carries them cannot be told from this history, which does not place the release users run. Answer lives in: the version you run. The record is incomplete: NVD: 116 records name vault with nothing tying them to this repository (CVE-2004-2777, CVE-2007-4785, CVE-2010-4449, …).

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