@fastify/merge-json-schemas
Builds a logical conjunction (AND) of multiple JSON schemas
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): fdawgs (Frazer Smith) was already a listed contributor in package.json before becoming publisher; transition within the Fastify org is legitimate. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): fdawgs is a pre-existing contributor with 289 approved packages and 0 rejected; addition is a legitimate org maintainer transition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signal triggered by simenb in historical maintainer list; current publisher fdawgs has a clean track record and this is a legitimate Fastify org package. | ai |
v0.2.1
2 findingsThis version was published by a different npm account than previous versions on 2025-01-06. 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.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.