@fastify/compress
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): matteo.collina is a core Fastify maintainer and listed contributor; publisher change is a legitimate transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jean-michelet is a known Fastify ecosystem contributor; addition is consistent with org maintenance. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer list cleanup in a well-established org package; no malicious indicators. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by a trusted core maintainer publishing with no code changes is low risk. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 8.3.1 | 8 / 9 | |
| 8.3.0 | 8 / 9 | |
| 8.2.0 | 8 / 9 | |
| 8.1.0 | 8 / 10 | |
| 8.0.3 | 8 / 10 | |
| 8.0.2 | 8 / 10 |
v8.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
2 findingsThis version was published by a different npm account than previous versions on 2025-07-01. 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.
v8.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.