@fastify/busboy
A streaming parser for HTML form data for node.js
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): Both kibertoad and eomm are trusted Fastify ecosystem maintainers with long track records; this transition reflects normal org-level maintainer rotation, not a compromise. | ai | |
| provenance | no-provenance | AI (provenance): Established Fastify ecosystem package; lack of Sigstore provenance is a process gap, not a security risk for this well-known package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 0 / 10 | |
| 3.1.1 | 0 / 9 | |
| 3.1.0 | 0 / 9 | |
| 3.0.0 | 0 / 9 | |
| 2.1.1 | 0 / 9 | |
| 2.1.0 | 0 / 9 | |
| 2.0.0 | 0 / 13 | |
| 1.2.1 | 1 / 13 | |
| 1.2.0 | 1 / 13 | |
| 1.1.0 | 1 / 13 | |
| 1.0.0 | 1 / 13 |
v2.1.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-02-28. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.0
2 findingsThis version was published by a different npm account than previous versions on 2023-11-12. 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.
v2.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-09-28. This could indicate a legitimate maintainer transition or an account compromise.