> - It doesn't use a structural language for the password files, so additional information like username has to be stored in the path of the password You can u

> - It doesn't use a structural language for the password files, so additional information like username has to be stored in the path of the password You can use multi-line passwords with the -m flag without leaking any information in the path. You can put whatever you want in the password entry, in whatever text format you want. So you can save an entry like this: areallygoodstrongpassword Username: someusername Secret API key: abc123 It's also really smart about what happens when you copy that entry to your clipboard. It will copy just the first line for easy password pasting. There's a demo of me using it to store AWS credentials in this write up: https://nickjanetakis.com/blog/managing-your-passwords-on-the-command-line-in-linux-with-pass https://nickjanetakis.com/blog/managing-your-passwords-on-th... > - It doesn't encrypt the paths to the passwords Yep, but the upside is you have tab complete in your terminal for accessing your passwords. If you planned to put it up on github you could always encrypt the folder / file names using https://github.com/cryptomator/cryptomator https://github.com/cryptomator/cryptomator or a comparable tool. I don't publish my pass fields on my public github account, so I never ran into this problem.