@walletconnect/core
Core 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/relay-api | AI (phantom-deps): Same-org dep, expected type-only or transitive usage. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): Logger formatting dep, plausibly used conditionally; benign for this package. | ai | |
| phantom-deps | phantom-dep:uint8arrays | AI (phantom-deps): Common byte-array util, likely used in bundled/minified code. | ai | |
| phantom-deps | phantom-dep:@walletconnect/jsonrpc-types | AI (phantom-deps): Same-org type dep, transitively used; stable FP. | ai | |
| source-diff | encoded-string-file:dist/index.umd.js | AI (source-diff): Rollup UMD bundle output; long strings are normal minified dist. | ai | |
| source-diff | obfuscated-file:dist/index.cjs | AI (source-diff): Rollup-bundled CJS output; standard minification for this package. | ai | |
| phantom-deps | phantom-dep:es-toolkit | AI (phantom-deps): Declared dep consumed inside the bundle; not a direct import but used at runtime. | ai | |
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Rollup-bundled ESM output; standard minification for this package. | ai | |
| dependencies | unvetted-dep:@walletconnect/jsonrpc-utils | AI (dependencies): Part of the WalletConnect monorepo ecosystem; expected sub-package dependency. | ai | |
| dependencies | unvetted-dep:@walletconnect/window-getters | AI (dependencies): Part of the WalletConnect monorepo ecosystem; expected sub-package dependency. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @walletconnect/core is the legitimate WalletConnect core package in a scoped namespace; Levenshtein comparison to 'cors' is a false positive with no impersonation intent. | ai | |
| dependencies | unvetted-dep:@walletconnect/jsonrpc-ws-connection | AI (dependencies): Part of the WalletConnect monorepo ecosystem; expected sub-package dependency. | ai | |
| dependencies | unvetted-dep:@walletconnect/jsonrpc-provider | AI (dependencies): Part of the WalletConnect monorepo ecosystem; expected sub-package dependency. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver is expected for a monorepo package versioned in lockstep; short README is typical for ecosystem sub-packages. Not indicative of spam or malice. | ai | |
| dependencies | unvetted-dep:es-toolkit | AI (dependencies): es-toolkit is a well-known utility library; its use here is legitimate. | ai | |
| dependencies | unvetted-dep:uint8arrays | AI (dependencies): uint8arrays is a standard utility for binary data in the JS/IPFS ecosystem; legitimate dependency. | ai | |
| dependencies | unvetted-dep:@walletconnect/time | AI (dependencies): Part of the WalletConnect monorepo ecosystem; expected sub-package dependency. | ai | |
| dependencies | unvetted-dep:@walletconnect/relay-api | AI (dependencies): Part of the WalletConnect monorepo ecosystem; expected sub-package dependency. | ai | |
| dependencies | unvetted-dep:@walletconnect/safe-json | AI (dependencies): Part of the WalletConnect monorepo ecosystem; expected sub-package dependency. | ai | |
| dependencies | unvetted-dep:@walletconnect/relay-auth | AI (dependencies): Part of the WalletConnect monorepo ecosystem; expected sub-package dependency. | ai |
Versions (showing 51 of 118)
| Version | Deps | Published |
|---|---|---|
| 2.23.10 | 17 / 0 | |
| 2.23.9 | 17 / 0 | |
| 2.23.8 | 17 / 0 | |
| 2.23.7 | 17 / 0 | |
| 2.23.6 | 17 / 0 | |
| 2.23.5 | 17 / 0 | |
| 2.23.4 | 17 / 0 | |
| 2.23.3 | 17 / 0 | |
| 2.23.2 | 17 / 0 | |
| 2.23.1 | 17 / 0 | |
| 2.23.0 | 17 / 0 | |
| 2.22.4 | 17 / 0 | |
| 2.22.3 | 17 / 0 | |
| 2.22.2 | 17 / 0 | |
| 2.22.1 | 17 / 0 | |
| 2.22.0 | 17 / 0 | |
| 2.21.10 | 17 / 0 | |
| 2.21.9 | 17 / 0 | |
| 2.21.8 | 17 / 0 | |
| 2.21.7 | 17 / 0 | |
| 2.21.6 | 17 / 0 | |
| 2.21.5 | 17 / 0 | |
| 2.21.4 | 17 / 0 | |
| 2.21.3 | 17 / 0 | |
| 2.21.2 | 17 / 0 | |
| 2.21.1 | 17 / 0 | |
| 2.21.0 | 17 / 0 | |
| 2.20.3 | 17 / 0 | |
| 2.20.2 | 17 / 0 | |
| 2.20.1 | 17 / 0 | |
| 2.19.4 | 17 / 0 | |
| 2.19.2 | 17 / 0 | |
| 2.19.1 | 17 / 0 | |
| 2.19.0 | 17 / 1 | |
| 2.18.1 | 17 / 1 | |
| 2.18.0 | 17 / 1 | |
| 2.17.5 | 17 / 1 | |
| 2.17.4 | 17 / 1 | |
| 2.17.3 | 17 / 1 | |
| 2.17.2 | 17 / 1 | |
| 2.17.1 | 17 / 1 | |
| 2.17.0 | 16 / 1 | |
| 2.16.3 | 16 / 1 | |
| 2.16.2 | 16 / 1 | |
| 2.16.1 | 16 / 1 | |
| 2.16.0 | 16 / 1 | |
| 2.15.3 | 16 / 1 | |
| 2.15.2 | 16 / 1 | |
| 2.15.1 | 16 / 1 | |
| 2.15.0 | 16 / 1 | |
| 2.14.0 | 17 / 2 |
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.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.
v2.15.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.14.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.