keb ee688c6c9b
CI / Checks (pull_request) Successful in 37s
PR title / Conventional title (pull_request) Successful in 1s
fix: decrypt SOPS .env keys written with export or spaces
sops keeps everything before the = in a dotenv key, so `export TOKEN=…`
is the key `export TOKEN`. lazysecrets asked sops for `TOKEN` and the
value couldn't be decrypted, from the list or a link.

- The sops path is the key as written; names and links are unchanged.
- A link finds its key's path in the file, as the list does, instead of
  rebuilding it from the name.
2026-10-15 12:16:47 +02:00
2026-10-12 15:40:46 +02:00
2026-10-15 10:49:28 +02:00
2026-10-12 15:40:46 +02:00
2026-10-12 15:40:46 +02:00
2026-10-12 15:40:46 +02:00
2026-10-15 10:52:09 +02:00
2026-10-13 17:19:14 +02:00
2026-10-13 17:19:14 +02:00
2026-10-12 15:40:46 +02:00
2026-10-12 15:40:46 +02:00

lazysecrets

A terminal UI for finding, reading and sharing secrets. Inspired by the fantastic lazygit.

lazysecrets

Main features

  • Read-only: lazysecrets never creates, changes or deletes a secret.
  • Zero setup: uses the logins you already have (az, the Databricks CLI, sops, git). No config file needed.
  • Search everything: ctrl+s searches every source at once, with fzf-style matching.
  • Share links: Share lazysecrets:// links with colleagues.
  • Careful with values: values stay hidden until you reveal them, and copied values are cleared from the clipboard after 30 seconds.
  • Scriptable: get, list and open for scripts, fzf and editor pickers; lazysecrets.nvim for Neovim.
  • Favourites: star the secrets you use most for easy access.
  • Expiry warnings: secrets, keys and certificates that expire soon are marked, listed together in the status pane.
  • Your way: rebind any key, pick a theme, and add custom commands to run on a secret.
  • Try it first: lazysecrets --demo runs on built-in sample data.
  • Sources: Azure Key Vault, Databricks secret scopes, and SOPS and .env files in your git repos.

Early development: expect rough edges. See CHANGELOG.md for what's new.

Install

On macOS or Linux (arm64 or x86_64):

curl -fsSL https://raw.githubusercontent.com/karleinarb/lazysecrets/main/install.sh | sh

Or

curl -fsSL https://git.kebcloud.no/keb/lazysecrets/raw/branch/main/install.sh | sh

Both approaches will install the latest release from GitHub with fallback to git.kebcloud.no, into ~/.local/bin after checking it against the release's checksums. sh -s -- v0.2.0 installs a given version, LAZYSECRETS_INSTALL_DIR somewhere else.

U (or lazysecrets update) updates in place when there's a newer release.

Or build it yourself: go install git.kebcloud.no/keb/lazysecrets/cmd/lazysecrets@latest.

Get started

az login            # login with azure cli
lazysecrets         # start lazysecrets
lazysecrets --demo  # test with demo data

Pick a source on the left, then a vault, then a secret. With nothing signed in yet, the right pane says how to get started. The keys you'll use most:

Key Action
j/k, enter, esc move, drill in, back
l / h the details of what's selected / back
/ filter the list you're in
space reveal / hide the value
y copy the value
ctrl+s Go to: search everything and jump there
f / F star / your favourites
s copy a link to share
? every key, searchable
q quit

Integration

lazysecrets list, get and open plug lazysecrets into fzf, editor pickers and scripts: see Integration.

fzf-example

Docs

  • Keys: every key, Go to, the layout, and rebinding keys
  • Azure Key Vault: accounts, permissions, pinned vaults
  • Databricks: profiles and Key Vault-backed scopes
  • SOPS and .env files: which repos and files, decrypting
  • Sharing: links to secrets, encrypted env files, and opening links, also from the browser and chat
  • Integration: how lazysecrets can integrate into other systems
  • Custom commands: run your own commands on a secret
  • Config: every option, themes, layered configs, the state file
  • Development: building, tests, how changes land and releasing

Privacy

lazysecrets never stores, caches or sends your secret values. It keeps the names and metadata of what you've loaded in a cache file readable only by you, to show it at once next time (storage.cache: false turns it off). It talks only to the services you use it with, and collects no usage data. The one call of its own is a daily check for a new release, on GitHub or else git.kebcloud.no, which updates.autoCheck: false turns off.

Repositories

The main repo of this codebase is at git.kebcloud.no. The GitHub mirror is for discoverability, issue-tracking and releases. It also makes it possible to give a ⭐ if you like lazysecrets!

Contributing

I don't take pull requests as I don't have time to review and test them. But bug reports and ideas are very welcome! Open an issue on GitHub and I'll have a look.

AI disclosure

Built with help from an agentic coding assistant. Every change is requested, reviewed and tested by me before it's merged.

License

Copyright © 2026 Karl-Einar Bergstrøm.

lazysecrets is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. See LICENSE.

v0.2.1
Latest
2026-10-15 10:52:43 +02:00
Languages
Go 99.1%
Shell 0.6%
JavaScript 0.3%