lazy-universal-dotenv
Robust Environment Configuration for Universal Applications.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from pksunkara to ndelangen reflects legitimate Storybook team maintainer transition; both are known team members. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (hypnosphi, igor-dv, ndelangen) are known Storybook team members; legitimate org transfer. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Standard Babel-compiled package pattern; @babel/runtime is injected by babel plugin at build time. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 3 / 3 | |
| 3.0.1 | 5 / 7 | |
| 3.0.0 | 5 / 7 | |
| 2.0.0 | 5 / 7 | |
| 1.9.1 | 5 / 13 |
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2019-06-19. 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.