npm-cache-filename
Given a cache folder and url, return the appropriate cache folder.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): isaacs → zkat is a well-documented npm team transition; both are core npm maintainers. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): zkat/kat (Kat Marchán) was a core npm CLI team member; legitimate maintainer addition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Tiny stable utility under npm org; infrequent publishes are expected, not suspicious. | ai | |
| bogus-package | bogus-package | AI (bogus-package): isaacs is npm's creator, not spam. Tiny payload and no keywords are normal for a focused utility. | ai |
v1.0.2
2 findingsThis version was published by a different npm account than previous versions on 2015-06-29. 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.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.