@walletconnect/jsonrpc-ws-connection
WS Connection 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): WalletConnect org team rotation; publisher is a known maintainer with 94 approved packages. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org team rotation, not a hostile takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects org maintenance cadence; no malicious signals in the diff. | ai |
v1.0.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (bkrem) on 2024-11-26, but gancho_walletconnect is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.