Gathering detailed insights and metrics for @dotenv/cli
Gathering detailed insights and metrics for @dotenv/cli
Gathering detailed insights and metrics for @dotenv/cli
Gathering detailed insights and metrics for @dotenv/cli
dotenv-cli
A global executable to run applications with the ENV variables loaded by dotenv
@dotenv-run/core
core library to load environment variables with monorepo support
@dotenv-run/webpack
Run your scripts with dotenv variables
@karmaniverous/get-dotenv
Process dotenv files in an arbitrary location & optionally populate environment variables.
npm install @dotenv/cli
Typescript
Module System
Min. Node Version
Node Version
NPM Version
TypeScript (99.41%)
JavaScript (0.48%)
Batchfile (0.11%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
46 Stars
129 Commits
4 Forks
1 Watchers
1 Branches
2 Contributors
Updated on Dec 07, 2024
Latest Version
2.2.2
Package Id
@dotenv/cli@2.2.2
Unpacked Size
46.17 kB
Size
9.02 kB
File Count
45
NPM Version
7.18.1
Node Version
17.8.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
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.
1# install globally (recommended) 2npm install @dotenv/cli -g # optionally run with sudo npm install @dotenv/cli -g
or
1# install locally 2npm install @dotenv/cli --save-dev
Usage is easy! Run the command:
1dotenv-cli new
Follow those instructions and then run:
1dotenv-cli push
And if you need to pull changes that another teammate made, run:
1dotenv-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 new
Create your .env.project
file.
Example:
1$ dotenv-cli new
dotenv-cli push [FILENAME]
Push your .env
file to development environment.
Example:
1$ dotenv-cli push 2# pushes local .env to remote development
Set input filename. Defaults to .env.
Example:
1$ dotenv-cli push .env.development 2# 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:
1$ dotenv-cli push .env.development --dotenv_me=me_1234 2# pushes local .env.development to remote development
dotenv-cli pull [ENVIRONMENT] [FILENAME]
Pulls your development|staging|ci|production environment(s) to your machine.
Example:
1$ dotenv-cli pull 2# pulls remote development envs to .env
For more information run..
1$ dotenv-cli help pull
Pull .env.ci, .env.staging, and .env.production
Example:
1$ dotenv-cli pull staging 2# pulls remote staging envs to .env.staging
Set output filename. Defaults to .env for development and .env.{environment} for other environments
Example:
1$ dotenv-cli pull production .env 2# 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:
1$ dotenv-cli pull staging --dotenv_me=me_1234 2# pulls remote staging envs to .env.staging 3 4$ dotenv-cli pull production .env --dotenv_me=me_1234 5# 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
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
Found 0/12 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
license file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
security policy file not detected
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
24 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More