libnpmpublish
Programmatic API for the bits behind npm publish and unpublish
4
Versions
ISC
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
saquibkhannpm-cli-opsreggiowlstronaut
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in provenance.js is standard DSSE envelope parsing for Sigstore provenance verification — not obfuscation. Stable false positive for this package. | ai | |
| dependencies | unvetted-dep:sigstore | AI (dependencies): sigstore is a legitimate npm/GitHub-maintained package required for provenance signing in npm publish workflows. | ai | |
| dependencies | unvetted-dep:npm-package-arg | AI (dependencies): npm-package-arg is a core npm CLI utility package maintained by GitHub/npm org; expected dependency for libnpmpublish. | ai | |
| dependencies | unvetted-dep:npm-registry-fetch | AI (dependencies): npm-registry-fetch is a core npm CLI utility package maintained by GitHub/npm org; expected dependency for libnpmpublish. | ai | |
| dependencies | unvetted-dep:@npmcli/package-json | AI (dependencies): @npmcli/package-json is a core npm CLI utility package maintained by GitHub/npm org; expected dependency for libnpmpublish. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 11.2.0 | 8 / 5 | |
| 11.1.3 | 8 / 5 | |
| 11.1.2 | 8 / 5 | |
| 11.0.1 | 8 / 5 |
v11.2.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.2
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.
v11.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.