@walletconnect/sign-client
Sign Client 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@walletconnect/jsonrpc-provider | AI (phantom-deps): Same-org dep, likely used via bundled build output. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): Used as pino transport at runtime, not statically imported. | ai | |
| provenance | publisher-changed | AI (provenance): Known WalletConnect→Reown org transition; publisher has strong approved track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old WalletConnect maintainer dropped as part of Reown rebrand. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same documented org transition to reown-npm-org. | ai | |
| source-diff | encoded-string-file:dist/index.umd.js | AI (source-diff): Rollup UMD build output; long strings are bundled minified code, not obfuscated payload. | ai | |
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Rollup-bundled ESM output; standard minification for this package. | ai | |
| source-diff | obfuscated-file:dist/index.cjs | AI (source-diff): Rollup-bundled CJS output; standard minification for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver and short README are expected for a monorepo sub-package migrating to a new npm org scope; version tracks monorepo release cadence. Not indicative of spam or malicious intent. | ai | |
| phantom-deps | phantom-dep:@walletconnect/heartbeat | AI (phantom-deps): Same-org dependency declared for transitive use via @walletconnect/core; not a phantom dep concern for this package. | ai | |
| phantom-deps | phantom-dep:@walletconnect/events | AI (phantom-deps): Same-org dependency declared for transitive use via @walletconnect/core; not a phantom dep concern for this package. | ai |
Versions (showing 51 of 120)
| Version | Deps | Published |
|---|---|---|
| 2.23.10 | 7 / 2 | |
| 2.23.9 | 9 / 2 | |
| 2.23.8 | 9 / 2 | |
| 2.23.7 | 9 / 2 | |
| 2.23.6 | 9 / 2 | |
| 2.23.5 | 9 / 2 | |
| 2.23.4 | 9 / 2 | |
| 2.23.3 | 9 / 2 | |
| 2.23.2 | 9 / 2 | |
| 2.23.1 | 9 / 2 | |
| 2.23.0 | 9 / 2 | |
| 2.22.4 | 9 / 2 | |
| 2.22.3 | 9 / 2 | |
| 2.22.2 | 9 / 2 | |
| 2.22.1 | 9 / 2 | |
| 2.22.0 | 9 / 2 | |
| 2.21.10 | 9 / 1 | |
| 2.21.9 | 9 / 1 | |
| 2.21.8 | 9 / 1 | |
| 2.21.7 | 9 / 1 | |
| 2.21.6 | 9 / 1 | |
| 2.21.5 | 9 / 1 | |
| 2.21.4 | 9 / 1 | |
| 2.21.3 | 9 / 1 | |
| 2.21.2 | 9 / 1 | |
| 2.21.1 | 9 / 1 | |
| 2.21.0 | 9 / 1 | |
| 2.20.3 | 9 / 1 | |
| 2.20.2 | 9 / 1 | |
| 2.20.1 | 9 / 1 | |
| 2.20.0 | 9 / 1 | |
| 2.19.4 | 9 / 1 | |
| 2.19.3 | 9 / 1 | |
| 2.19.2 | 9 / 1 | |
| 2.19.1 | 9 / 1 | |
| 2.19.0 | 9 / 1 | |
| 2.18.1 | 9 / 1 | |
| 2.18.0 | 9 / 1 | |
| 2.17.5 | 9 / 4 | |
| 2.17.4 | 9 / 4 | |
| 2.17.3 | 9 / 4 | |
| 2.17.2 | 9 / 4 | |
| 2.17.1 | 9 / 4 | |
| 2.17.0 | 9 / 4 | |
| 2.16.3 | 9 / 4 | |
| 2.16.2 | 9 / 4 | |
| 2.16.1 | 9 / 4 | |
| 2.16.0 | 9 / 4 | |
| 2.15.3 | 9 / 4 | |
| 2.15.2 | 9 / 4 | |
| 2.15.1 | 9 / 4 |
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
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.4
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.3
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.2
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.3
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.2
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.3
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.2
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.