libreseal — LibreSeal CLI

libreseal is the command-line client for LibreSeal, a free, self-hosted secrets manager. It authenticates against your own LibreSeal server, manages secrets per app and environment, and injects them into processes without writing them to disk.

LibreSeal CLI is an independent fork of the Phase CLI. It is not affiliated with or endorsed by Phase / Phi Security Inc. It has no default cloud host and never downloads installers from third-party infrastructure.

Each release has one binary per platform (libreseal_<version>_<os>_<arch>, .exe on Windows), checksums.txt, its keyless cosign signature checksums.txt.sigstore.json (made by this repository's release workflow) and LICENSE. Verify before installing (needs cosign); replace X.Y.Z and the platform:

base=https://github.com/Dos2Locos/libreseal-cli/releases/download/vX.Y.Z
bin=libreseal_X.Y.Z_linux_amd64                  # or darwin_arm64, windows_amd64.exe, …
curl -fLO "$base/$bin" -fLO "$base/checksums.txt" -fLO "$base/checksums.txt.sigstore.json"
cosign verify-blob checksums.txt --bundle checksums.txt.sigstore.json \
  --certificate-identity-regexp '^https://github.com/Dos2Locos/libreseal-cli/.github/workflows/release.yml@refs/tags/v' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com
sha256sum -c checksums.txt --ignore-missing      # macOS: shasum -a 256 -c checksums.txt --ignore-missing
install -m 0755 "$bin" ~/.local/bin/libreseal    # or /usr/local/bin with sudo
libreseal --version

You need Go 1.25 or newer.

git clone https://github.com/Dos2Locos/libreseal-cli.git
cd libreseal-cli
./scripts/install-from-source.sh                 # installs /usr/local/bin/libreseal (sudo if needed)
# or, without sudo:
PREFIX="$HOME/.local" ./scripts/install-from-source.sh
libreseal --version

Container image (built locally):

docker build -t libreseal-cli .
docker run --rm -e LIBRESEAL_HOST -e LIBRESEAL_SERVICE_TOKEN libreseal-cli apps list

libreseal update only prints instructions; it never fetches, runs or replaces anything. Install a newer release binary as above, or check out a newer tag and rerun the installer:

cd libreseal-cli && git fetch --tags
git checkout <tag>
./scripts/install-from-source.sh

libreseal auth                    # prompts for your server URL, then opens the browser (webauth)
libreseal auth --mode token       # paste a personal access token instead
libreseal users whoami

Create a service account in the LibreSeal UI (Access → Service Accounts) with access only to the apps and environments it needs, generate a token, and provide it through the environment:

export LIBRESEAL_HOST=https://secrets.example.lan
export LIBRESEAL_SERVICE_TOKEN='pss_service:v2:...'   # never commit or echo this
libreseal apps list

libreseal apps list                                   # apps, IDs and environments
libreseal init --app-id <APP_ID> --env development    # link this directory (.phase.json)

libreseal secrets create DB_PASSWORD --random base64url --length 48 --type sealed
echo "8080" | libreseal secrets create PORT --type config
libreseal secrets list
libreseal secrets get PORT
libreseal secrets update DB_PASSWORD --random hex --length 64
libreseal secrets delete PORT

libreseal secrets import .env --env development
libreseal secrets export --env development --format json

libreseal run 'npm start'                             # inject secrets into a process
libreseal run --env production --tags backend './start.sh'

Run libreseal <command> --help for all flags.

libreseal ai enable (run by a human) installs a skill document for Claude Code, Cursor, Copilot, Codex or OpenCode; libreseal ai skill prints it. When the CLI detects an AI agent it blocks printenv/env/export/set/declare/compgen inside libreseal run and disables libreseal shell. Detection relies on agent-set environment variables and is defence in depth only: give agents a least-privilege service account token and store sensitive values as sealed. See also libreseal-skills.

The server API and token formats are unchanged. libreseal is verified against LibreSeal servers; using it against Phase servers (or phase against LibreSeal) is expected to work but is not tested.

See the LibreSeal README for the server / CLI / skills versions verified together.

cd src
go vet ./...
go test ./...
go build -o libreseal .

Versions are vX.Y.Z (vX.Y.Z-rc.N for release candidates), starting at v0.1.0; the tags inherited from the Phase CLI were removed from this fork. Only admins can create, move or delete v* tags (ruleset release-tags, managed by scripts/github/protect-main.sh in libreseal). Pushing a tag on a commit of main runs .github/workflows/release.yml: it checks the tag, runs the tests and GoReleaser, and opens a draft release for a maintainer to review and publish.

To keep a local clone free of the old upstream tags: git fetch --prune --prune-tags origin and, if you added the Phase CLI as a remote, git config remote.upstream.tagOpt --no-tags.

GPL-3.0, see LICENSE. Copyright of the original work belongs to Phase and its contributors; LibreSeal modifications are also released under GPL-3.0.