@walletconnect/types
Typings for WalletConnect Protocol
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate WalletConnect maintainer handoff; publisher has clean track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same handoff; stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver reflects monorepo versioning convention; sparse README is typical for a types-only package in a large monorepo. Not indicative of spam or malicious intent. | ai |
Versions (showing 51 of 120)
| Version | Deps | Published |
|---|---|---|
| 2.23.10 | 6 / 0 | |
| 2.23.9 | 6 / 0 | |
| 2.23.8 | 6 / 0 | |
| 2.23.7 | 6 / 0 | |
| 2.23.6 | 6 / 0 | |
| 2.23.5 | 6 / 0 | |
| 2.23.4 | 6 / 0 | |
| 2.23.3 | 6 / 0 | |
| 2.23.2 | 6 / 0 | |
| 2.23.1 | 6 / 0 | |
| 2.23.0 | 6 / 0 | |
| 2.22.4 | 6 / 0 | |
| 2.22.3 | 6 / 0 | |
| 2.22.2 | 6 / 0 | |
| 2.22.1 | 6 / 0 | |
| 2.22.0 | 6 / 0 | |
| 2.21.10 | 6 / 0 | |
| 2.21.9 | 6 / 0 | |
| 2.21.8 | 6 / 0 | |
| 2.21.7 | 6 / 0 | |
| 2.21.6 | 6 / 0 | |
| 2.21.5 | 6 / 0 | |
| 2.21.4 | 6 / 0 | |
| 2.21.3 | 6 / 0 | |
| 2.21.2 | 6 / 0 | |
| 2.21.1 | 6 / 0 | |
| 2.21.0 | 6 / 0 | |
| 2.20.3 | 6 / 0 | |
| 2.20.2 | 6 / 0 | |
| 2.20.1 | 6 / 0 | |
| 2.20.0 | 6 / 0 | |
| 2.19.4 | 6 / 0 | |
| 2.19.3 | 6 / 0 | |
| 2.19.2 | 6 / 0 | |
| 2.19.1 | 6 / 0 | |
| 2.19.0 | 6 / 0 | |
| 2.18.1 | 6 / 0 | |
| 2.18.0 | 6 / 0 | |
| 2.17.5 | 6 / 0 | |
| 2.17.4 | 6 / 0 | |
| 2.17.3 | 6 / 0 | |
| 2.17.2 | 6 / 0 | |
| 2.17.1 | 6 / 0 | |
| 2.17.0 | 6 / 0 | |
| 2.16.3 | 6 / 0 | |
| 2.16.2 | 6 / 0 | |
| 2.16.1 | 6 / 0 | |
| 2.16.0 | 6 / 0 | |
| 2.15.3 | 6 / 0 | |
| 2.15.2 | 6 / 0 | |
| 2.15.1 | 6 / 0 |
v2.20.0
2 findingsThis version was published by a different npm account than previous versions on 2025-04-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.4
2 findingsThis version was published by a different npm account than previous versions on 2025-04-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.3
2 findingsThis version was published by a different npm account than previous versions on 2025-04-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.