dotenv-expand
Expand environment variables using dotenv
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): tea.yaml is common in legitimate packages from the tea.xyz promotion era; dotenv-expand is a 30M+ downloads/week canonical package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature stable utility; infrequent publishes are normal. Same original author (motdotla) with strong track record. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 13.0.0 | 1 / 5 | |
| 12.0.3 | 1 / 5 | |
| 12.0.2 | 1 / 5 | |
| 12.0.1 | 1 / 5 | |
| 12.0.0 | 1 / 5 | |
| 11.0.7 | 1 / 5 | |
| 5.1.0 | 0 / 4 |
v13.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.2
2 findingsMatched 1 signal(s), weighted score 7: • [S_TEA_YAML] Package ships tea.yaml / tea.yml — marker used by tea.xyz token-farming packages.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.1
2 findingsMatched 1 signal(s), weighted score 7: • [S_TEA_YAML] Package ships tea.yaml / tea.yml — marker used by tea.xyz token-farming packages.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
2 findingsMatched 1 signal(s), weighted score 7: • [S_TEA_YAML] Package ships tea.yaml / tea.yml — marker used by tea.xyz token-farming packages.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.