@fastify/view
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:vite | AI (typosquat): @fastify/view is a scoped Fastify template plugin with no relation to vite; Levenshtein proximity is coincidental and this is a stable false positive. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads compiled template files from a plugin-controlled directory; this is the expected pattern for doT template compilation in a template rendering plugin. | ai |
v12.0.0
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 (fdawgs) than the most recent previously approved version (matteo.collina) on 2026-06-09, but fdawgs 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.
v11.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.