@walletconnect/jsonrpc-types
Typings for JSON-RPC
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:keyvaluestorage-interface | AI (phantom-deps): This is a typings package; keyvaluestorage-interface is legitimately declared as a dependency for type references without necessarily being directly imported in source files. | ai | |
| provenance | no-provenance | AI (provenance): WalletConnect packages in this ecosystem do not use Sigstore provenance attestation; this is consistent across their published packages and not a security concern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.4 | 2 / 17 | |
| 1.0.3 | 2 / 30 | |
| 1.0.2 | 2 / 30 | |
| 1.0.1 | 1 / 30 | |
| 1.0.0 | 1 / 30 |
v1.0.2
2 findingsThis version was published by a different npm account (bkrem) than the most recent previously approved version (pedrouid) on 2022-11-25. It has since remained available on npm for 1332 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.