
Research
/Security News
Intercom’s npm Package Compromised in Ongoing Mini Shai-Hulud Worm Attack
Compromised intercom-client@7.0.4 npm package is tied to the ongoing Mini Shai-Hulud worm attack targeting developer and CI/CD secrets.
@dotenv/cli
Advanced tools
Warning ⚠️
This CLI is deprecated. Please use the new and improved dotenv-vault cli.
Dotenv cli is a command line tool that syncs your .env files across machines and between your team members. It's like 1Password, but for developers. Designed by the same people that brought you dotenv, it's a recommended plugin for dotenv.
# install globally (recommended)
npm install @dotenv/cli -g # optionally run with sudo npm install @dotenv/cli -g
or
# install locally
npm install @dotenv/cli --save-dev
Usage is easy! Run the command:
dotenv-cli new
Follow those instructions and then run:
dotenv-cli push
And if you need to pull changes that another teammate made, run:
dotenv-cli pull
That's it!
dotenv-cli help [COMMAND]display help for dotenv-cli
USAGE
$ dotenv-cli help [COMMAND]
ARGUMENTS
COMMAND command to show help for
OPTIONS
--all see all commands in CLI
dotenv-cli newCreate your .env.project file.
Example:
$ dotenv-cli new
dotenv-cli push [FILENAME]Push your .env file to development environment.
Example:
$ dotenv-cli push
# pushes local .env to remote development
Set input filename. Defaults to .env.
Example:
$ dotenv-cli push .env.development
# pushes .env.development to remote development environment
Directly pass your DOTENV_ME value to the command line, instead of reading from a .env.me file.
Examples:
$ dotenv-cli push .env.development --dotenv_me=me_1234
# pushes local .env.development to remote development
dotenv-cli pull [ENVIRONMENT] [FILENAME]Pulls your development|staging|ci|production environment(s) to your machine.
Example:
$ dotenv-cli pull
# pulls remote development envs to .env
For more information run..
$ dotenv-cli help pull
Pull .env.ci, .env.staging, and .env.production
Example:
$ dotenv-cli pull staging
# pulls remote staging envs to .env.staging
Set output filename. Defaults to .env for development and .env.{environment} for other environments
Example:
$ dotenv-cli pull production .env
# pulls remote production envs to .env
Directly pass your DOTENV_ME value to the command line, instead of reading from a .env.me file.
Examples:
$ dotenv-cli pull staging --dotenv_me=me_1234
# pulls remote staging envs to .env.staging
$ dotenv-cli pull production .env --dotenv_me=me_1234
# pulls remote production envs to .env
NODE_TLS_REJECT_UNAUTHORIZED=0 DOTENV_API_URL=https://cli.dotenv.development ./bin/run
yarn test
Only for those with permission.
npm publish
See CONTRIBUTING.md
See CHANGELOG.md
FAQs
CLI to interact with dotenv
The npm package @dotenv/cli receives a total of 639 weekly downloads. As such, @dotenv/cli popularity was classified as not popular.
We found that @dotenv/cli demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
/Security News
Compromised intercom-client@7.0.4 npm package is tied to the ongoing Mini Shai-Hulud worm attack targeting developer and CI/CD secrets.

Research
Socket detected a malicious supply chain attack on PyPI package lightning versions 2.6.2 and 2.6.3, which execute credential-stealing malware on import.

Research
A brand-squatted TanStack npm package used postinstall scripts to steal .env files and exfiltrate developer secrets to an attacker-controlled endpoint.