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

The median source file here is 50 lines. 5 files exceed 1,000 lines, the largest being 3,411. 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.

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 2025-07-02. 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 2.4.9. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 3 records name vagrant with nothing tying them to this repository (CVE-2022-25962, CVE-2025-34075, CVE-2026-7373).