@web3-storage/upload-client
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package; no provenance is consistent across all versions of this package. | ai | |
| dependencies | unvetted-dep:@ucanto/core | AI (dependencies): First-party sibling dep from storacha/w3up ecosystem; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@ucanto/client | AI (dependencies): First-party sibling dep from storacha/w3up ecosystem; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@ucanto/transport | AI (dependencies): First-party sibling dep from storacha/w3up ecosystem; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@web3-storage/blob-index | AI (dependencies): First-party sibling dep from storacha/w3up ecosystem; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@web3-storage/capabilities | AI (dependencies): First-party sibling dep from storacha/w3up ecosystem; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@web3-storage/data-segment | AI (dependencies): First-party sibling dep from storacha/w3up ecosystem; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@web3-storage/filecoin-client | AI (dependencies): First-party sibling dep from storacha/w3up ecosystem; stable pattern across versions. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 17.1.4 | 16 / 16 | |
| 17.1.3 | 16 / 16 | |
| 17.1.2 | 16 / 16 | |
| 17.1.1 | 16 / 16 | |
| 17.1.0 | 16 / 16 | |
| 17.0.1 | 16 / 16 | |
| 17.0.0 | 16 / 16 |
v17.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.