@remix-run/file-storage-s3
S3 backend for remix/file-storage
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Explicitly a CI/OIDC placeholder at 0.0.0 from the official remix-run org; not a malicious throwaway. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Intentional namespace reservation placeholder; sparse metadata is expected for this package type. | ai | |
| dependencies | unvetted-dep:@remix-run/file-storage | AI (dependencies): Sibling package in the same remix-run org; expected dependency for this S3 backend. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.3 | 2 / 4 | |
| 0.1.2 | 2 / 4 | |
| 0.1.1 | 2 / 4 | |
| 0.1.0 | 2 / 2 | |
| 0.0.0 | 0 / 0 |
v0.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.