@fastify/multipart
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/error | AI (dependencies): @fastify/error is a core Fastify ecosystem package maintained by the same org; stable dependency for any @fastify/* plugin. | ai | |
| dependencies | unvetted-dep:fastify-plugin | AI (dependencies): fastify-plugin is the standard plugin wrapper for Fastify; a canonical dependency for all Fastify plugins. | ai | |
| provenance | no-provenance | AI (provenance): Established Fastify org package published by known maintainer matteo.collina; lack of Sigstore provenance is not a concern here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 10.1.0 | 5 / 16 | |
| 10.0.0 | 5 / 16 | |
| 9.4.0 | 5 / 16 | |
| 9.3.0 | 5 / 16 | |
| 9.2.1 | 5 / 17 |
v10.1.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 (matteo.collina) 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.