opv

opv keeps your app's secrets and settings in 1Password and syncs them to where your apps run (Fly.io, GitHub Actions, Azure Key Vault + Container Apps, Kubernetes) or into a local command, without ever printing, logging or writing a value.

npm i -g @matthew-cochran/opv
opv --version

npm picks the prebuilt opv binary for your operating system and CPU through a per-platform optional dependency. A postinstall script also copies it to ~/.local/bin/opv (%LOCALAPPDATA%\Programs\opv\opv.exe on Windows), the same place the install script uses, and registers the agent skill for this user (opv skill install --user --target all); it never replaces a file that is not an opv binary. Set OPV_NO_SKILL=1 or CI to skip skill registration in automation. The skill is refreshed only by the installers and opv skill install; no other opv command writes your home directory. opv doctor and opv skill status report a copy older than the binary. Run npm i -g without sudo. npm 12 and newer run install scripts only when allowed: npm i -g --allow-scripts=@matthew-cochran/opv @matthew-cochran/opv (without it, opv still works through npm's own link, and the first run copies the new binary to ~/.local/bin/opv when npm placed the old one there; or run node "$(npm root -g)/@matthew-cochran/opv/install.js"). If your shell then says ~/.local/bin/opv: No such file or directory, run hash -r.

• Website: opv.dev
• Documentation and source: github.com/matt-cochran/1password-vault
• Changes: CHANGELOG

opv is an independent project, not affiliated with or endorsed by 1Password.