safe-publish-latest
Ensure that when you `npm publish`, the "latest" tag is only set for the truly latest version.
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 | no-provenance | AI (provenance): Package predates Sigstore provenance; ljharb is a well-known trusted publisher. Absence of provenance is expected for this package's age. | ai | |
| phantom-deps | phantom-dep:yargs | AI (phantom-deps): yargs is a declared runtime dependency used in the bin script; phantom classification is a false positive from indirect usage tracing. | ai | |
| phantom-deps | phantom-dep:in-publish | AI (phantom-deps): in-publish is a declared runtime dependency central to this package's purpose; phantom classification is a false positive. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 3 / 8 | |
| 1.1.5 | 3 / 7 | |
| 1.1.4 | 3 / 5 | |
| 1.1.3 | 4 / 5 | |
| 1.1.2 | 3 / 6 | |
| 1.1.1 | 3 / 5 | |
| 1.1.0 | 3 / 5 | |
| 1.0.1 | 3 / 5 | |
| 1.0.0 | 4 / 5 |
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.