@rango-dev/provider-walletconnect-2
## Known issues
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Standard base64 decoding of cryptographic signature bytes in a Cosmos transaction signer — not obfuscation. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding of a transaction hash from Tendermint RPC response — normal blockchain SDK usage. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): Umee mainnet RPC URL in a mock/test fixture; legitimate blockchain endpoint, not C2. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.54.0 | 11 / 2 | |
| 0.53.1 | 16 / 2 | |
| 0.53.0 | 16 / 2 | |
| 0.52.0 | 16 / 2 | |
| 0.51.0 | 16 / 2 | |
| 0.50.0 | 16 / 2 | |
| 0.49.0 | 16 / 2 | |
| 0.48.1 | 16 / 2 | |
| 0.46.0 | 16 / 2 | |
| 0.45.0 | 16 / 2 | |
| 0.44.0 | 16 / 2 | |
| 0.43.0 | 16 / 2 | |
| 0.42.0 | 16 / 2 | |
| 0.41.0 | 16 / 2 | |
| 0.40.0 | 16 / 2 | |
| 0.39.0 | 16 / 2 | |
| 0.38.1 | 16 / 2 | |
| 0.38.0 | 16 / 2 |
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.