np
A better `npm publish`
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:pkg-dir | AI (phantom-deps): pkg-dir is declared and used in config; phantom-dep is a false positive for this package's legitimate use case. | ai | |
| dependencies | unvetted-dep:onetime | AI (dependencies): onetime is a sindresorhus utility package; same trusted publisher as np itself. No security concern. | ai | |
| phantom-deps | phantom-dep:package-directory | AI (phantom-deps): package-directory is a declared dependency used in config/indirect context; not a security risk for this package. | ai | |
| phantom-deps | phantom-dep:symbol-observable | AI (phantom-deps): symbol-observable is a declared dependency used transitively by rxjs/listr; not a security risk for this package. | ai | |
| provenance | no-provenance | AI (provenance): sindresorhus is a highly trusted publisher with a long track record; absence of Sigstore provenance is a hygiene note, not a risk signal for this package. | ai |
Versions (showing 51 of 108)
| Version | Deps | Published |
|---|---|---|
| 11.2.2 | 36 / 12 | |
| 11.2.1 | 36 / 12 | |
| 11.2.0 | 36 / 12 | |
| 11.1.0 | 36 / 12 | |
| 11.0.3 | 36 / 12 | |
| 11.0.2 | 36 / 12 | |
| 11.0.1 | 36 / 12 | |
| 11.0.0 | 36 / 12 | |
| 10.3.0 | 36 / 12 | |
| 10.2.0 | 36 / 12 | |
| 10.1.0 | 36 / 12 | |
| 10.0.7 | 36 / 12 | |
| 10.0.6 | 36 / 12 | |
| 10.0.5 | 36 / 12 | |
| 10.0.4 | 36 / 12 | |
| 10.0.3 | 36 / 12 | |
| 10.0.2 | 36 / 12 | |
| 10.0.1 | 36 / 12 | |
| 10.0.0 | 37 / 12 | |
| 9.2.0 | 38 / 12 | |
| 9.1.0 | 38 / 12 | |
| 9.0.0 | 38 / 12 | |
| 8.0.4 | 36 / 9 | |
| 8.0.3 | 36 / 9 | |
| 8.0.2 | 36 / 9 | |
| 8.0.1 | 36 / 9 | |
| 8.0.0 | 36 / 9 | |
| 7.7.0 | 39 / 6 | |
| 7.6.4 | 39 / 6 | |
| 7.6.3 | 39 / 6 | |
| 7.6.2 | 39 / 6 | |
| 7.6.1 | 39 / 6 | |
| 7.6.0 | 39 / 6 | |
| 7.5.0 | 39 / 6 | |
| 7.4.0 | 39 / 6 | |
| 7.3.0 | 39 / 6 | |
| 7.2.0 | 39 / 6 | |
| 7.1.0 | 39 / 6 | |
| 7.0.0 | 38 / 6 | |
| 6.5.0 | 35 / 6 | |
| 6.4.0 | 35 / 6 | |
| 6.3.2 | 35 / 6 | |
| 6.3.1 | 35 / 6 | |
| 6.3.0 | 35 / 4 | |
| 6.2.5 | 35 / 4 | |
| 6.2.4 | 35 / 4 | |
| 6.2.3 | 35 / 4 | |
| 6.2.2 | 35 / 4 | |
| 6.2.1 | 35 / 4 | |
| 6.2.0 | 35 / 4 | |
| 6.1.0 | 35 / 4 |
v11.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.