path-name
Cross-platform PATH env name
1
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
zkochan
Keywords
envenvironpath
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-bulk-read | AI (semgrep): Object.keys(process.env) is used solely to find the correct casing of the PATH variable on Windows — the package's entire documented purpose. No exfiltration or misuse of env data. | ai | |
| provenance | no-provenance | AI (provenance): Package is 9+ years old with a single version from a trusted publisher; lack of Sigstore provenance is expected for packages predating that ecosystem feature. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 0 / 3 |
v1.0.0
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.