@fastify/fast-json-stringify-compiler
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Fastify org regularly rotates maintainers; tony133 and jean-michelet are known Fastify contributors. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal Fastify org maintainer rotation; no evidence of hostile takeover. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is intentional in this JSON serialization compiler — it compiles schema-derived serializer functions at runtime, which is the documented purpose of fast-json-stringify's standalone mode. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.1.0 | 1 / 6 | |
| 5.0.3 | 1 / 7 | |
| 5.0.2 | 1 / 7 | |
| 5.0.1 | 1 / 6 | |
| 5.0.0 | 1 / 6 |
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
2 findingsThis version was published by a different npm account than previous versions on 2025-01-04. 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.
v5.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (eomm) than the most recent previously approved version (matteo.collina) on 2024-09-21, but eomm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.