envify
Selectively replace Node-style environment variables with plain strings.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:esprima-fb | AI (dependencies): esprima-fb is Facebook's well-known esprima fork; its unusual version string is a documented quirk of FB's versioning, not a malicious indicator. Appropriate dependency for a source-transform tool. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance on npm by many years; absence is expected and not a risk signal for this established package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from hughsk to yoshuawuyts is a documented legitimate handoff; yoshuawuyts has an excellent track record (1386 approved, 0 rejected). Stable for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is consistent with a maintainer transition period. No code changes were introduced; risk is low for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 2 / 2 | |
| 4.0.0 | 2 / 2 | |
| 3.4.1 | 2 / 2 | |
| 3.4.0 | 2 / 2 | |
| 3.3.1 | 2 / 2 | |
| 3.3.0 | 2 / 2 | |
| 3.2.0 | 2 / 2 | |
| 3.1.0 | 2 / 2 | |
| 3.0.0 | 4 / 1 | |
| 2.0.1 | 4 / 1 | |
| 2.0.0 | 4 / 1 | |
| 1.2.1 | 4 / 1 | |
| 1.2.0 | 4 / 1 | |
| 1.1.0 | 3 / 1 | |
| 1.0.1 | 2 / 1 | |
| 1.0.0 | 2 / 1 | |
| 0.2.0 | 2 / 1 | |
| 0.1.0 | 2 / 1 | |
| 0.0.1 | 2 / 1 |
v4.1.0
2 findingsThis version was published by a different npm account than previous versions on 2017-07-07. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-11-27. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-03-16. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.