pass-code VS kbs2

There's the pass-code extension for that:

https://github.com/alpernebbi/pass-code

> A pass extension that obscures the filenames and folder hierarchy within your password store.

> pass-code generates random filenames for each file in the password store and keeps the mapping in an encrypted file. This way, no valuable information is accessible even if your password store is leaked to the public (unless your GPG private keys were also leaked). Nevertheless, you should always ensure proper protection of your password store.

I don't use pass myself (I have severe NIH[1]), but its design has inspired me many times over: very, very few tools rise to the challenge of adhering to the Unix philosophy without cargo-culting it, and pass is one of them. I highly recommend that people looking to write engineer-friendly tools study its manpage[2].

[1]: https://github.com/woodruffw/kbs2

[2]: https://git.zx2c4.com/password-store/about/

Two things:

* (Yet another) password and secret manager, using modern cryptographic libraries (age) and with a strong emphasis on customizability[1]. I personally use it as a general purpose secret store for everything from passwords to command snippets.

* A tool that runs commands when USB devices are inserted or removed, allowing a user to write filters against a variety of device metadata. The end goal is something similar to udev rules, but much nicer to configure and cross-platform. Still unreleased.

[1]: https://github.com/woodruffw/kbs2