@fastify/send
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
starptechsimonebcoopflowdelvedormatteo.collinaallevojsumnerszekthrafaelgsseommfox1tairhornskibertoadclimba03003galvezsimenbgurgundaymetcoder95ivan-tymoshenkofdawgs
Keywords
staticfileserver
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@lukeed/ms | AI (dependencies): @lukeed/ms is a legitimate, widely-used utility by Luke Edwards; its use in a static file server for time-string parsing is expected and benign across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Fastify org package; lack of provenance is common and not a risk signal for this well-known package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 5 / 9 |
v4.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.