# Install vault-cli with Homebrew

Subversion-like utility to work with Jackrabbit FileVault. Version 4.2.0 via Homebrew; verified 2026-06-22.

## Install

```sh
sudo av install brew:vault-cli
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install vault-cli
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:vault-cli
- **Package manager:** Homebrew
- **Version:** 4.2.0
- **Source summary:** Subversion-like utility to work with Jackrabbit FileVault
- **Homepage:** <https://jackrabbit.apache.org/filevault/index.html>
- **Repository:** <https://github.com/apache/jackrabbit-filevault>
- **Last updated:** 2026-06-22T14:06:34-07:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- vlt (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 4.2.0
## Project history and usage

`vault-cli` in Homebrew packages the `vlt` command from Apache Jackrabbit FileVault. FileVault maps Java Content Repository content to a filesystem representation and uses that mapping for portable content packages; `vlt` is the Subversion-like CLI for working with repository content.

### Project history

Apache Jackrabbit FileVault entered the Apache Jackrabbit project as a donated repository-content synchronization tool. The Jackrabbit news archive records FileVault 3.0.0 as the first release of the recently donated tool in September 2013, and the release notes identify version 3.0.0 as the initial version of the contribution to Apache Jackrabbit, with the improvement ticket noting Adobe's FileVault contribution to the ASF.

The project then became part of the Apache Jackrabbit ecosystem around JCR, Oak, Sling, and content packages. The official FileVault page describes it as an Apache Software Foundation project and presents the CLI, API, and content-package tooling as pieces of the same repository-to-filesystem mapping system.

### Adoption history

FileVault is most visible in Adobe Experience Manager and Apache Jackrabbit/Sling development workflows, where repository content has to move between a running JCR repository and source-controlled project files. Adobe's AEM documentation points developers at the VLT tool for synchronizing a FileVault checkout with a local repository, including checkout, status, diff, and commit-style workflows.

### How it is used

The `vlt` CLI exposes commands such as `checkout`, `status`, `update`, `commit`, `revert`, `diff`, `import`, `export`, `rcp`, and `sync`. It accepts repository credentials, can update `~/.vault/auth.xml`, and can install or control the Vault Sync service for local filesystem and repository synchronization.

In package-manager terms this formula is valuable because it gives non-Maven users the same `vlt` executable used by JCR/AEM developers. Typical users are not managing HashiCorp Vault; they are treating repository nodes as versionable files, exporting/importing content packages, or bridging a local IDE checkout with a running content repository.

### Why package nerds care

The name is easy to confuse with HashiCorp Vault, but the executable `vlt` and the Apache Jackrabbit coordinates make it a Java content-repository tool. Its niche is narrow, yet important for teams that package CMS or JCR repository content as deployable artifacts.

### Timeline

- 2013-09: Apache Jackrabbit FileVault 3.0.0 is released as the first release of the recently donated repository content synchronization tool.
- 2017: Apache Jackrabbit FileVault Package Maven Plugin 1.0.0 is released for content-package builds.
- 2026: Official FileVault documentation is published for version 4.2.0.

### Related projects

- Apache Jackrabbit and Jackrabbit Oak provide the surrounding JCR ecosystem.
- Apache Sling and Adobe Experience Manager are common environments where FileVault/VLT workflows appear.
- The FileVault Package Maven Plugin complements `vlt` by building deployable content package artifacts.

### Sources

- Adobe AEM VLT tool guide: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/developing/devtools/ht-vlttool
- Apache FileVault release notes: https://github.com/apache/jackrabbit-filevault/blob/master/RELEASE-NOTES.txt
- Apache Jackrabbit news archive: https://jackrabbit.apache.org/jcr/news-archive.html
- Official FileVault page: https://jackrabbit.apache.org/filevault/
- Official VLT usage guide: https://jackrabbit.apache.org/filevault/usage.html


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Credential files

- Unix: ~/.vault/auth.xml

## Combined YAML source

View the package source record on GitHub. [combined/vault-cli.yml](https://github.com/mxcl/pkgdb/blob/main/combined/vault-cli.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph