dotenv
Loads environment variables from .env file
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:.tap/report/lcov-report/prettify.js | AI (source-diff): Google prettify.js shipped as part of tap test runner's lcov HTML coverage report output; not a runtime file. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Standard crypto key parsing in dotenv's decrypt() for encrypted .env vault files. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard ciphertext decoding in dotenv's decrypt() for encrypted .env vault files. | ai |
Versions (showing 100 of 100)
| Version | Deps | Published |
|---|---|---|
| 17.4.2 | 0 / 7 | |
| 17.4.1 | 0 / 7 | |
| 17.4.0 | 0 / 7 | |
| 17.3.1 | 0 / 7 | |
| 17.3.0 | 0 / 7 | |
| 17.2.4 | 0 / 7 | |
| 17.2.3 | 0 / 7 | |
| 17.2.2 | 0 / 7 | |
| 17.2.1 | 0 / 7 | |
| 17.2.0 | 0 / 7 | |
| 17.1.0 | 0 / 7 | |
| 17.0.1 | 0 / 7 | |
| 17.0.0 | 0 / 7 | |
| 16.6.1 | 0 / 7 | |
| 16.6.0 | 0 / 7 | |
| 16.5.0 | 0 / 7 | |
| 16.4.7 | 0 / 7 | |
| 16.4.6 | 0 / 7 | |
| 16.4.5 | 0 / 10 | |
| 16.4.4 | 0 / 10 | |
| 16.4.3 | 0 / 10 | |
| 16.4.2 | 0 / 10 | |
| 16.4.1 | 0 / 10 | |
| 16.4.0 | 0 / 10 | |
| 16.3.2 | 0 / 10 | |
| 16.3.1 | 0 / 10 | |
| 16.3.0 | 0 / 10 | |
| 16.2.0 | 0 / 10 | |
| 16.1.4 | 0 / 10 | |
| 16.1.3 | 0 / 10 | |
| 16.1.2 | 0 / 10 | |
| 16.1.1 | 0 / 10 | |
| 16.1.0 | 0 / 10 | |
| 16.0.3 | 0 / 10 | |
| 16.0.2 | 0 / 10 | |
| 16.0.1 | 0 / 10 | |
| 16.0.0 | 0 / 9 | |
| 15.0.1 | 0 / 9 | |
| 15.0.0 | 0 / 9 | |
| 14.3.2 | 0 / 9 | |
| 14.3.1 | 0 / 9 | |
| 14.3.0 | 0 / 9 | |
| 14.2.0 | 0 / 9 | |
| 14.1.1 | 0 / 9 | |
| 14.1.0 | 0 / 9 | |
| 14.0.1 | 0 / 9 | |
| 14.0.0 | 0 / 9 | |
| 13.0.1 | 0 / 9 | |
| 13.0.0 | 0 / 9 | |
| 12.0.4 | 0 / 9 | |
| 12.0.3 | 0 / 9 | |
| 12.0.2 | 0 / 9 | |
| 12.0.1 | 0 / 9 | |
| 12.0.0 | 0 / 9 | |
| 11.0.0 | 0 / 8 | |
| 10.0.0 | 0 / 8 | |
| 9.0.2 | 0 / 8 | |
| 9.0.1 | 0 / 8 | |
| 9.0.0 | 0 / 8 | |
| 8.6.0 | 0 / 8 | |
| 8.5.1 | 0 / 8 | |
| 8.5.0 | 0 / 8 | |
| 8.4.0 | 0 / 8 | |
| 8.3.0 | 0 / 8 | |
| 8.2.0 | 0 / 8 | |
| 8.1.0 | 0 / 7 | |
| 8.0.0 | 0 / 7 | |
| 7.0.0 | 0 / 6 | |
| 6.2.0 | 0 / 6 | |
| 6.1.0 | 0 / 5 | |
| 6.0.0 | 0 / 4 | |
| 5.0.1 | 0 / 7 | |
| 5.0.0 | 0 / 7 | |
| 4.0.0 | 0 / 8 | |
| 3.0.0 | 0 / 8 | |
| 2.0.0 | 0 / 6 | |
| 1.2.0 | 0 / 5 | |
| 1.1.0 | 0 / 4 | |
| 1.0.0 | 0 / 4 | |
| 0.5.1 | 0 / 2 | |
| 0.5.0 | 0 / 2 | |
| 0.4.0 | 0 / 2 | |
| 0.3.0 | 0 / 2 | |
| 0.2.8 | 0 / 2 | |
| 0.2.7 | 0 / 2 | |
| 0.2.6 | 0 / 2 | |
| 0.2.5 | 0 / 2 | |
| 0.2.4 | 0 / 2 | |
| 0.2.3 | 0 / 2 | |
| 0.2.2 | 0 / 2 | |
| 0.2.1 | 0 / 2 | |
| 0.2.0 | 0 / 2 | |
| 0.1.2 | 0 / 2 | |
| 0.1.1 | 0 / 2 | |
| 0.1.0 | 0 / 2 | |
| 0.0.5 | 0 / 2 | |
| 0.0.4 | 0 / 2 | |
| 0.0.3 | 0 / 2 | |
| 0.0.2 | 0 / 2 | |
| 0.0.1 | 0 / 2 |
v17.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.6
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.