npmpackage.info

Gathering detailed insights and metrics for @cprize/dotenv-expand

@cprize/dotenv-expand - 5.1.0 | npmpackage.info

@cprize/dotenv-expand

Variable expansion for dotenv. Expand variables already on your machine for use in your .env file.

5.1.0

1,012

BSD-2-Clause

JavaScript

4.86 kB

3.1

Installations

npm install @cprize/dotenv-expand

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Node Version

14.17.2

NPM Version

6.14.13 Pull Requests

Open

0

Total

79

Closed

29

Merged

50

Issues

Open

0

Total

56

Closed

56

Releases

Unable to fetch releases

Languages

JavaScript

TypeScript

JavaScript (99.5%)

TypeScript (0.5%)

Developer

motdotla

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

BSD-2-Clause License

1,012 Stars

267 Commits

98 Forks

5 Watchers

1 Branches

23 Contributors

Updated on Jul 13, 2025

Maintainers

View All 23 Contributors

Package Meta Information

Latest Version

5.1.0

Package Id

@cprize/dotenv-expand@5.1.0

Unpacked Size

4.86 kB

Size

2.37 kB

File Count

NPM Version

6.14.13

Node Version

14.17.2

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

dotenv lab should standard

dotenv-expand

Dotenv-expand adds variable expansion on top of dotenv. If you find yourself needing to expand environment variables already existing on your machine, then dotenv-expand is your tool.

Install

1npm install dotenv --save
2npm install dotenv-expand --save

Usage

As early as possible in your application, require dotenv and dotenv-expand, and wrap dotenv-expand around dotenv.

1var dotenv = require('dotenv')
2var dotenvExpand = require('dotenv-expand')
3
4var myEnv = dotenv.config()
5dotenvExpand(myEnv)

See test/.env for examples of variable expansion in your .env file.

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

3

Maintained

Determines if the project is "actively maintained".

3

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

3.1

/10

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