Why not have one less square mile of attack surface by not having secrets in a .env file in the first place?
What are people doing that requires something like this?
What are people doing that requires something like this?
The idea seems nice with a simple yet effective implementation. While I think I currently have a shell script syntax highlight plugin reading env files, it's definitely overkill. Now if only this could protect from random npm packages reading your env files...