pacvamp / documentation
Know what you install.
One command line for pacman repositories and the AUR. Preview package changes, review the recipes you build, and keep a record of your choices.
Proof of concept
pacvamp is experimental, unsupported, and not ready for real use. Try it on a disposable machine. Read the status and limitations before installing.
Start with a preview
After installing pacvamp, inspect a package and the transaction it would require:
pacvamp search helix
pacvamp info helix
pacvamp install helix --dry-runThe preview shows the affected packages, their origin, and the pacman command. It does not install anything. The first steps guide walks through installation, checks, and your first package choice.
Find your next step
Use packages
Install and remove, declare packages in a manifest, or import an existing machine. Learn when a command changes your declarations and when it changes installed packages.
Review and update
Review an AUR recipe, understand a blocked update, or check active protections. Policy and evidence depend on your configuration and publisher.
Publish and integrate
Run a registry or follow the OPR, Omarchy, and mise adoption guides. These are separate operator workflows.
How pacvamp fits
pacvamp reads pacman’s databases and delegates package transactions to pacman. It adds manifests, commit-bound AUR approval, build confinement, and checks for signed repository evidence. It does not make arbitrary packages safe, and a repository name alone does not establish provenance.
User-scoped development tools stay with mise. Repositories can publish verified vendor releases through the tool channel; packslip supplies the external signed release format.
For command details, use the client reference or repository reference. To work on pacvamp, start with development and architecture. The roadmap tracks remaining work.
