the per-phrase PIN lock in 3.0 is the right scope for the problem. most snippet managers make you choose between one vault-wide password that gets annoying to unlock constantly, or leaving everything in the clear. locking just the bank details and leaving everyday replies and SQL snippets frictionless is a much better tradeoff. source-available is also a smart call for something that's going to sit close to sensitive text.
Hi and thank you for your review.
So if I get your improvement request correct, you'd like to see some kind of filter, in order to filter for protected items. Correct?
In that case I'll have good news: The feature "filtering" will come very soon with version 3.1. Originally intended for cleanup tasks (deleting unused and old items). But of course it's easy to filter for protected items also.
While I'm at it I just like to make a new small clarification: the PIN/password is for the whole database. So you basically have one pin or password. But you can decide which phrases to protect as an individual decision. This keeps PhraseVault still easy and simple. Most people probably won't touch this feature. But if you require more protection it is just like you are used to: unlock and elevate your Windows PC, Mac OS, and Linux sudo with one password/PIN.
Hope this helps and clarifies. Thank you again for your review.