@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, so a manually published version cannot be tied back to a reviewed commit.
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 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 0.55.0 | 11 / 2 | |
| 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 | |
| 0.30.0 | 16 / 2 | |
| 0.29.0 | 17 / 1 | |
| 0.28.1 | 17 / 1 | |
| 0.28.0 | 17 / 1 | |
| 0.27.0 | 17 / 1 | |
| 0.26.2 | 17 / 1 | |
| 0.26.1 | 17 / 1 | |
| 0.26.0 | 17 / 1 | |
| 0.25.0 | 17 / 1 | |
| 0.24.0 | 17 / 1 | |
| 0.23.0 | 17 / 1 | |
| 0.22.0 | 17 / 1 | |
| 0.21.0 | 16 / 1 | |
| 0.20.0 | 16 / 1 | |
| 0.19.0 | 16 / 1 | |
| 0.18.0 | 16 / 1 | |
| 0.17.0 | 16 / 1 | |
| 0.16.0 | 16 / 1 | |
| 0.15.0 | 16 / 1 | |
| 0.14.0 | 16 / 1 | |
| 0.13.0 | 16 / 1 | |
| 0.12.0 | 16 / 1 | |
| 0.11.0 | 16 / 1 | |
| 0.10.0 | 16 / 1 | |
| 0.9.0 | 16 / 1 | |
| 0.8.0 | 16 / 1 | |
| 0.7.0 | 16 / 1 | |
| 0.6.0 | 16 / 1 | |
| 0.5.0 | 16 / 1 | |
| 0.4.0 | 16 / 1 | |
| 0.3.0 | 16 / 1 | |
| 0.2.0 | 16 / 1 |
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.