@meshsdk/web3-sdk
⚠️ DEPRECATED - Use @utxos/sdk instead. UTXOS SDK - Web3 infrastructure platform for UTXO blockchains
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@meshsdk/wallet | AI (dependencies): First-party @meshsdk sibling package; stable across versions. | ai | |
| dependencies | unvetted-dep:@meshsdk/bitcoin | AI (dependencies): First-party @meshsdk sibling package; stable across versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @meshsdk/bitcoin is a first-party sibling dep pinned to the same beta version as all other @meshsdk packages — consistent monorepo release pattern. | ai | |
| phantom-deps | phantom-dep:base32-encoding | AI (phantom-deps): base32-encoding is a declared runtime dep; phantom-dep fires because it's referenced via types (@types/base32-encoding) in devDeps rather than direct import. | ai | |
| provenance | no-provenance | AI (provenance): Established MeshSDK package; no provenance is consistent across all 68 versions and is not a risk indicator here. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.0.62 | 9 / 8 | |
| 0.0.39 | 8 / 8 | |
| 0.0.31 | 8 / 8 | |
| 0.0.30 | 8 / 8 | |
| 0.0.29 | 7 / 7 | |
| 0.0.28 | 7 / 7 | |
| 0.0.27 | 7 / 7 | |
| 0.0.26 | 7 / 7 | |
| 0.0.25 | 7 / 4 | |
| 0.0.24 | 7 / 4 | |
| 0.0.23 | 7 / 4 | |
| 0.0.22 | 7 / 4 | |
| 0.0.20 | 7 / 4 | |
| 0.0.19 | 7 / 4 | |
| 0.0.17 | 7 / 4 | |
| 0.0.16 | 7 / 4 | |
| 0.0.15 | 7 / 4 | |
| 0.0.14 | 7 / 4 | |
| 0.0.13 | 6 / 4 | |
| 0.0.12 | 6 / 4 | |
| 0.0.10 | 6 / 4 | |
| 0.0.7 | 5 / 4 | |
| 0.0.6 | 5 / 4 | |
| 0.0.5 | 4 / 4 | |
| 0.0.3 | 4 / 4 |
v0.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.