← Home

pkgmgr

npm Repository Homepage
3
Versions
—
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

kentcdodds

Keywords

npmpnpmyarnbunpackage-managercli

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Fires in test helper that snapshots process.env for restoration; not production code and not a security risk. ai

Versions (showing 3 of 3)

Version Deps Published
1.1.1 0 / 0
1.1.0 0 / 0
1.0.0 0 / 0

v1.1.1

2 findings
HIGH env-spread: bin/lib.test.js:6 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/kentcdodds/pkgmgr/blob/ed2be283ceecb6fd5254eca09d1ed091d7d323bc/bin/lib.test.js#L6 4 | 5 | function setupEnv(overrides = {}) { > 6 | const original = { ...process.env } 7 | 8 | delete process.env.PKGMGR

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.

v1.1.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.

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.