secure-json-parse
JSON parse with prototype poisoning protection
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 | publisher-changed | AI (provenance): Legitimate maintainer transition within the fastify team; fdawgs is a listed contributor and known fastify core member. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): All added maintainers are recognized fastify core team members; reflects org-level maintainer list update. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 0 / 8 | |
| 4.0.0 | 0 / 9 | |
| 3.0.2 | 0 / 9 | |
| 3.0.1 | 0 / 8 | |
| 3.0.0 | 0 / 8 | |
| 2.7.0 | 0 / 7 | |
| 2.6.0 | 0 / 7 | |
| 2.5.0 | 0 / 7 | |
| 2.4.0 | 0 / 7 | |
| 2.3.2 | 0 / 6 | |
| 2.3.1 | 0 / 6 | |
| 2.3.0 | 0 / 2 | |
| 2.2.0 | 0 / 2 | |
| 2.1.0 | 0 / 2 | |
| 2.0.0 | 0 / 2 | |
| 1.0.0 | 0 / 2 | |
| 0.1.0 | 0 / 0 |
v3.0.2
2 findingsThis version was published by a different npm account than previous versions on 2025-01-03. 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.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.