# Installer vaulted avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de vaulted pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:vaulted
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install vaulted
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:vaulted
- **Gestionnaire de paquets:** Homebrew
- **Version:** 3.0.0
- **Résumé source:** Allows the secure storage and execution of environments
- **Page d'accueil:** <https://github.com/miquella/vaulted>
- **Dépôt:** <https://github.com/miquella/vaulted>
- **Dernière mise à jour:** 2026-07-26T00:30:00+02:00
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- vaulted (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 3.0.0
## Historique du projet et usages

`vaulted` is a small Go CLI for creating named vaults of secrets and spawning commands or shells with those secrets loaded into an isolated environment.

### Historique du projet

The public project history is sparse, but the official README defines the core idea clearly: users create vaults of related secrets, then spawn sessions from them. Vaults may hold environment variables, AWS credentials, and SSH keys, and spawned environments get temporary AWS credentials and a new SSH agent.

### Historique d'adoption

The tool belongs to the family of local developer-secret wrappers that reduce the need to keep credentials permanently exported in a shell. Its adoption appears niche and centered on users who want one command to switch AWS, SSH, and arbitrary environment-variable contexts.

### Modes d'utilisation

Typical usage starts with `vaulted add my-vault`, editing a vault interactively, then running `vaulted -n my-vault -- aws s3 ls` or `vaulted shell my-vault`. The README also documents an `env` subcommand intended for machine-readable integration with shells and utilities.

Vault files follow the XDG Base Directory Specification, with user-written vault data stored under `$XDG_DATA_HOME/vaulted/`, typically `~/.local/share/vaulted/`, and session caches under `$XDG_CACHE_HOME/vaulted/`.

### Pourquoi les passionnés de paquets s'y intéressent

For package users, `vaulted` is notable less for a large ecosystem and more for being a compact Unix-style credential context switcher. It is adjacent to tools such as `aws-vault`, but broader in that it also handles arbitrary environment variables and SSH keys.

### Chronologie

- 2019 or earlier: Repository history and Go module packaging indicate an established Go CLI project.
- Current README: Documents Homebrew installation, Go 1.12+ manual installation, XDG storage, AWS credentials, SSH-agent isolation, and spawned command workflows.

### Related projects

- AWS CLI is a common consumer of spawned temporary AWS credentials.
- SSH agent tooling is part of the spawned-environment model.

### Sources

- Official GitHub README: https://github.com/miquella/vaulted


## Notes de sécurité

narrow executable package without higher-risk signals.

- **Risque Geiger:** vert / faible
- 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: $XDG_DATA_HOME/vaulted/, ~/.local/share/vaulted/

## Combined YAML source

View the package source record on GitHub. [combined/vaulted.yml](https://github.com/mxcl/pkgdb/blob/main/combined/vaulted.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