I imagine it might be obvious for most users and potential users of pass, and being in line with the unix philosophy, it might be by design, but still, since I

I imagine it might be obvious for most users and potential users of pass, and being in line with the unix philosophy, it might be by design, but still, since I didn't see it mentioned in the documentation, it's worth mentioning: By itself, Passwordstore will not encrypt file names or directory names (which by convention represent the names of the service/site you have an account with). That might not pose a problem if no one else has access to the machine that hosts your git repo, but if that's not the case (even if it's a private repo on whatever platform), you might want to use either Tomb or git-crypt-remote to have full end-to-end encryption. There are even some tools that glue tomb and pass together (https://github.com/roddhjav/pass-tomb https://github.com/roddhjav/pass-tomb for one), though I'm not sure what's the situation is like when it comes to mobile integration with tomb/git-crypt-remote.