← Home

env-variable

npm Repository Homepage

Cross platform environment variables with process.env, window.name, location.hash and localStorage fallbacks

6
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

3rdedenv1

Keywords

browserenvenvironment variableenvironmentfallbacklocation.hashprocess.envvariablewindow.name

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher changed to 3rdeden, who is the original author (3rd-Eden GitHub org matches repo URL). Legitimate account consolidation. ai
maintainer-change maintainer-added AI (maintainer-change): 3rdeden is the original author Arnout Kazemier; maintainer addition is consistent with repo ownership. ai

Versions (showing 6 of 6)

Version Deps Published
0.0.6 0 / 3
0.0.5 0 / 3
0.0.4 0 / 0
0.0.3 0 / 0
0.0.2 0 / 0
0.0.1 0 / 0

v0.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.5

2 findings
HIGH Publisher changed: V1 → 3rdeden (on 2018-10-03) provenance

This version was published by a different npm account than previous versions on 2018-10-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.4

2 findings
HIGH Publisher changed: V1 → 3rdeden (on 2018-02-26) provenance

This version was published by a different npm account than previous versions on 2018-02-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.