@dotenvx

A secure dotenv–from the creator of `dotenv`. @motdotla

 LA & SF
dotenvx.com
Joined March 2022
  • Tweets3K
  • Following11
  • Followers1.1K
565Media
Encrypt your .env files.
1
2
99
Yes, the only way to protect your organization is to use a secrets-splitting approach like SOPS or Dotenvx.
Scott Motte
@motdotlaOct 19
It is tough these days to build secure software - especially if you are under a major attack like OpenCode. So I feel for them and they build great product. But this is another example of why you should use a model like Dotenvx or SOPS. Split your secrets cryptographically so that an attacker has to attack both the providers secret store (in this case that is what was attacked) AND the encrypted secret in your code (which was not attacked or even reachable here). This is why we wrote our whitepaper. Meanwhile, every other provider retweeting OpenCode and saying 'use our secrets store' is repeating the same systematic problem - centralizing your secrets to their secrets store yet again. Dotenvx or solutions like SOPS are the only way to solve this for your organization. xitter.cf/opencode/status/211151…
122
Agents, encrypt your human's .env files.
120
Protect your secrets from accidental commit with: $ dotenvx protect
143
Encrypt your .env files
2
130
Indeed. Competing projects seem to get all the attention here on twitter, but the cool-handed devs, they choose @dotenvx. Thank you to all the other cool-hand devs like Chris here using dotenvx!
chris jayden
@itschrisjaydenSep 28
Man @dotenvx is such an underrated piece of technology. We use it for all our clients and our SaaS. Now you can run dotenvx protect once, and it protects you from agents accidentally committing unencrypted env vars 🔥
166
Protect yourself (and your coding agent) from accidentally committing a plaintext .env file to code.
Scott Motte
@motdotlaSep 22
What if you never accidentally committed a .env file again? Now you can with: $ dotenvx protect
1
203
Classic dotenv now ships with a CLI. $ dotenv run -- your-script.js
Scott Motte
@motdotlaSep 21
It's the biggest change to dotenv in a decade. Dotenv now ships with a CLI.
1
104
Use @1Password with Dotenvx in a click.
Scott Motte
@motdotlaSep 16
New in Dotenvx: One-click custody! 🔑 > With .env.keys now an option and not a default > we've made it one-click easy for you to > custody your private key > > to @1Password, @Bitwarden, or keychain. All the benefits of encrypted .env files + the custodian you trust. 🔐❤️
114
Infra for Armor ⛨
Scott Motte
@motdotlaSep 14
Our Armor customers have been asking for a way to distribute their private keys through their infrastructure. Now they (and you) can.
106
GM SF. Encrypt your secrets.
1
1
133
Good night everyone. Encrypt your .env files and sleep well.
1
668
Tell a friend to upgrade.
Scott Motte
@motdotlaSep 2
Your biggest security win this week is a one-line dotenv upgrade. Swap dotenv to @dotenvx/dotenvx and be the security hero at your company this week. $ npm install @dotenvx/dotenvx
1
1,187
We'll be at @browserbase Navigate on Thurs Sept 10th - rubbing elbows with the best. Shoot us a DM to talk secrets and agents while there!
1
1
818
Armor up devs.
Scott Motte
@motdotlaSep 1
You're encrypting your .env files - keeping them safe from agents. But are you armoring your private key? $ dotenvx armor up
322
$ dx run -f .env.local,.env That's cleaner.
Scott Motte
@motdotlaAug 31
It's been annoying repeating -f when loading multiple .env files. You no longer have to! Just pass `-f .env.local,.env` as a comma separated string of filenames. I don't know why I didn't add this a long time ago!
222
You want the agent to understand your secrets but not read them. Encrypt them in a .env file and keep the private decryption key away from your agent. Now it can.
1
180
11 Million Weekly. Thank you everyone for the continued support.
121
The SOC 2 process for Armor continues.
Scott Motte
@motdotlaAug 26
We are nearing the end of our observation period and then will have our SOC 2 Type 2 audit. It's been a great experience with @oneleet's help. Most importantly, our customers are even safer.
153
Encrypt your .env files and commit them to code. This is safer in the event your coding agent accidentally wipes or modifies your .env file. You'll see the change attempt.
2
181
Load more