@nestjs/platform-fastify
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Official NestJS package; README link density reflects legitimate ecosystem documentation, not spam/phishing. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 11.1.20 | 10 / 0 | |
| 11.1.19 | 10 / 0 | |
| 11.1.18 | 10 / 0 | |
| 11.1.17 | 10 / 0 | |
| 11.1.16 | 10 / 0 |
v11.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.