Repo brief: hashicorp/vagrant

Generated by RepoPilot · document generated 2026-09-17 · concise human review Evidence snapshot · analyzed 2026-09-17T03:46:18.380Z · commit dc55920a2845

Verdict

Mixed — Evidence incomplete — review before adopting

• Last commit today
• 19 active contributors
• Distributed ownership (top contributor 35% of recent commits)
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

Vagrant is a command-line tool that creates and manages reproducible development environments by provisioning and configuring virtual machines (VirtualBox, VMware, AWS, Docker, etc.) from declarative Vagrantfiles. It solves the 'works on my machine' problem by distributing portable, version-controlled dev environments across Windows, macOS, and Linux. Monolithic Ruby application structured around an action-based pipeline architecture. Core logic lives in lib/vagrant/action/ (Builder, Runner, Warden classes orchestrate workflows). Builtin actions in lib/vagrant/action/builtin/ handle provisioning, synced folders, SSH, box management, and provisioner lifecycle. Config loading via…

Start here

Open these first:

• lib/vagrant.rb — Main entry point that loads and orchestrates the entire Vagrant framework and plugin system.
• lib/vagrant/environment.rb — Core environment manager that tracks machine state, configuration, and provides the context for all operations.
• lib/vagrant/machine.rb — Represents a single VM instance and coordinates provisioning, communication, and lifecycle management.
• lib/vagrant/action/builder.rb — Constructs middleware chains that execute VM operations through a composable middleware pattern.
• lib/vagrant/plugin/v2/plugin.rb — Base plugin class that defines the extension interface for providers, provisioners, and guests.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone and verify manifest first: No Gemfile, package.json, or Makefile excerpt provided in repository_data. Before running any commands, verify the repository's actual package manager manifest (check for Gemfile, Ra…

Daily commands:

Setup unverified (no manifest in repository_data): Likely bundle install && bundle exec vagrant --version to validate installation. To run Vagrant against a test VM: vagrant init <box> (creates Vagrantfile), the…

…shortened for this brief.

Key cautions & unknowns

• Could not verify license from the available repository evidence
• (1) Action Middleware Chain: Warden pattern requires understanding call/return ordering—actions must yield to next middleware or chain breaks; (2) Config Merging: Vagrantfile config is merged across layers…
• License evidence is incomplete or ambiguous.
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.