env-dot-prop
Get, set, or delete nested properties of process.env using a dot path
8
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
simonepri
Keywords
env-dot-propdot-propenv-configenv-configsenv-configrenv-configurationenv-configuratorconfigconfigsconfigrconfigurationconfiguratorenvenvironment
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): env-dot-prop's core purpose is reading/writing process.env via dot paths; enumerating process.env keys is expected and intentional, not malicious. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 1 / 3 | |
| 2.0.1 | 1 / 5 | |
| 2.0.0 | 1 / 5 | |
| 1.1.2 | 2 / 5 | |
| 1.1.0 | 2 / 5 | |
| 1.0.2 | 2 / 4 | |
| 1.0.1 | 2 / 4 | |
| 1.0.0 | 2 / 4 |
v3.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.