@opengis/fastify-file
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@grpc/proto-loader | AI (phantom-deps): gRPC proto-loader loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:image-size | AI (phantom-deps): Utility dep referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@grpc/grpc-js | AI (phantom-deps): gRPC dep loaded by convention per config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-s3 | AI (phantom-deps): AWS SDK loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:formidable | AI (phantom-deps): Framework-scoped optional dependency loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:fastify | AI (phantom-deps): fastify is a peer dependency in a fastify plugin; not directly imported but used via plugin registration. | ai | |
| phantom-deps | phantom-dep:undici | AI (phantom-deps): undici is a known implicit runtime dependency of fastify; stable false positive for fastify plugins. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used to write uploaded file content to disk — standard file upload handling, not obfuscation. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.86 | 9 / 2 | |
| 1.0.85 | 9 / 2 | |
| 1.0.84 | 9 / 10 | |
| 1.0.83 | 9 / 10 | |
| 1.0.82 | 9 / 10 | |
| 1.0.81 | 9 / 10 | |
| 1.0.80 | 9 / 10 | |
| 1.0.76 | 9 / 10 |
v1.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.