macOS
Homebrewverified · 100%
brew install gopassprovider-native install command
brew / rank 2260
Install gopass with Homebrew
Slightly more awesome Standard Unix Password Manager for Teams. Version 1.16.1 via Homebrew; verified 2026-06-22.
install
Additional install commands
overview
Package summary
Slightly more awesome Standard Unix Password Manager for Teams
Project links
Commands and aliases
- gopass
history
Project history and usage
gopass is a command-line password manager positioned as a more team-oriented take on the standard Unix password manager, pass. By default it encrypts secrets with GPG and versions the store in git, while also supporting other crypto and storage backends.
Project history
The gopasspw/gopass repository was created in February 2017 and published a v1.0.0 release the same day. Its README describes the project as a drop-in replacement for pass, built from experience with globally distributed development teams.
The early 1.x release line moved quickly through setup, team, mount, sync, and browser-oriented workflows. The README shows the project broadening from a Unix-style password-store clone into a cross-platform secrets manager with Linux, macOS, BSD, and Windows installation paths.
Adoption history
gopass adoption is strongly tied to package managers and team workflows. The README documents Homebrew, MacPorts, Debian-style packages from the gopass package repository, Fedora, Arch, WinGet, Chocolatey, Scoop, FreeBSD, OpenBSD, Alpine, source builds, and manual release downloads.
The project also grew a browser-integration side through gopass-jsonapi and gopassbridge, letting users avoid the command line for routine website logins while keeping the git/GPG-backed store model.
How it is used
A typical user runs `gopass setup` to create a root store, choose encryption, optionally configure a git remote, and write configuration under the user's gopass config directory. Daily commands include `gopass create`, `gopass ls`, `gopass show -c`, `gopass rm`, `gopass sync`, and `gopass mounts`.
The default store path documented by the README is `$HOME/.local/share/gopass/stores/root`, with GPG encryption and git storage. The README also notes that age encryption and fossil storage are available alternatives.
Why package nerds care
gopass is significant to package nerds because it preserves the Unix password-store mental model while making it more installable and cross-platform for teams. It is a CLI-first security tool whose real-world value depends on package-manager trust, GPG/git availability, shell completion, and browser-native messaging helpers.
It is also a case study in a project name colliding with distro namespaces: the README warns Debian and Ubuntu users not to install an unrelated `gopass` package from official repositories, then points them to the gopass project's own apt repository.
Timeline
- 2017: GitHub repository created under gopasspw/gopass.
- 2017: v1.0.0 release published on GitHub Releases.
- 2017: v1.1.0 and v1.2.0 releases followed during the first months of public development.
- 2017: v1.3.x releases continued the early stable CLI line.
- 2020s: README documents broad package-manager installation across Unix-like systems and Windows, plus browser integration through gopass-jsonapi.
Related projects
- The README relates gopass to pass, GPG, git, age, fossil, gopass-jsonapi, gopassbridge, gpg4win, package managers such as Homebrew and Scoop, and browser integrations.
Sources
security posture
Risk level: green
narrow executable package without higher-risk signals.
Risk classifier
green risk · low confidence · appliance
Why
- narrow executable package without higher-risk signals
Signals
- metadata:no-higher-risk-signals
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
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.
Configuration files
Config paths the tool may read or write during local use.
- Unix
~/.config/gopass/config/etc/gopass/config<STORE_DIR>/config<STORE_DIR>/config.worktree- Windows
%APPDATA%\gopass\config
Credential files
Credential-bearing paths to review before unattended agent runs.
- Unix
~/.local/share/gopass/stores/root~/.password-store
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
gopass | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-08-03
manager version1.16.1
manager updated2026-06-22
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:gopass |
|---|---|
| Version | 1.16.1 |
| Package manager | Homebrew |
| Homepage | https://www.gopass.pw/ |
| Repository | https://github.com/gopasspw/gopass |
| Last updated | 2026-06-22T14:03:38-07:00 |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- Nucleus package database
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation