@parqlet/storage-s3
S3 ClientStorage adapter. Wraps an injected @aws-sdk/client-s3 instance.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@parqlet/protocol | AI (phantom-deps): Same-org monorepo workspace dep; not directly imported but legitimately declared as a dependency. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.1.13 | 1 / 4 | |
| 0.1.12 | 1 / 4 | |
| 0.1.11 | 1 / 4 | |
| 0.1.10 | 1 / 4 | |
| 0.1.9 | 1 / 4 | |
| 0.1.8 | 1 / 4 | |
| 0.1.4 | 1 / 4 | |
| 0.1.3 | 2 / 2 | |
| 0.1.2 | 2 / 2 | |
| 0.1.1 | 2 / 2 |
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.