@fastify/cors
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:fastify-plugin | AI (dependencies): fastify-plugin is a core Fastify ecosystem utility; its use in @fastify/cors is expected and stable across all versions. | ai | |
| dependencies | unvetted-dep:toad-cache | AI (dependencies): toad-cache is a standard LRU/TTL cache used throughout the Fastify plugin ecosystem; its use here is expected and legitimate. | ai | |
| provenance | no-provenance | AI (provenance): Lack of Sigstore provenance is common (~88% of npm packages); not a meaningful risk signal for this well-established Fastify org package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 11.3.0 | 2 / 8 | |
| 11.2.0 | 2 / 8 | |
| 11.1.0 | 2 / 9 | |
| 11.0.1 | 2 / 9 | |
| 11.0.0 | 2 / 9 |
v11.3.0
2 findings[Accepted risk] Package 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 (gurgunday) on 2026-07-08, 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.
v11.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.