@web3-storage/w3up-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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@web3-storage/blob-index | AI (phantom-deps): Same-org package; declared as dep and used transitively in this monorepo package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 17.3.0 | 12 / 20 | |
| 17.2.0 | 12 / 20 | |
| 17.1.2 | 12 / 20 | |
| 17.1.1 | 12 / 20 | |
| 17.1.0 | 12 / 20 | |
| 17.0.0 | 12 / 20 |
v17.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.