stringify-package
stringifies npm-written json files
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Legitimate transfer from zkat to npm org team; isaacs and co-maintainers are the official npm team. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from zkat to isaacs reflects known npm org transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are all known npm org members. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): zkat left npm; removal is expected. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by npm org takeover is expected for this package. | ai |
v1.0.1
3 findingsAll previous maintainers (zkat) were replaced by new maintainers (adam_baldwin, ahmadnassri, annekimsey, billatnpm, claudiahdz, darcyclarke, isaacs, mikemimik, ruyadorno). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2019-09-30. 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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.