← Home

@walletconnect/core

npm Repository Homepage

Core for WalletConnect Protocol

100
Versions
SEE LICENSE IN LICENSE.md
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

cyberdrkreown-npm-org

Keywords

walletwalletconnect

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 100 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
2.13.3 17 / 2
2.13.2 17 / 2
2.13.1 17 / 2
2.13.0 17 / 2
2.12.2 17 / 2
2.12.1 17 / 2
2.12.0 17 / 2
2.11.3 17 / 2
2.11.2 17 / 2
2.11.1 17 / 2
2.11.0 17 / 2
2.10.6 16 / 2
2.10.5 16 / 2
2.10.4 16 / 2
2.10.3 16 / 2
2.10.2 16 / 2
2.10.1 16 / 2
2.10.0 16 / 2
2.9.2 16 / 2
2.9.1 16 / 2
2.9.0 16 / 2
2.8.6 16 / 2
2.8.5 16 / 2
2.8.4 16 / 2
2.8.3 16 / 2
2.8.2 16 / 2
2.8.1 16 / 2
2.8.0 16 / 2
2.7.8 16 / 2
2.7.7 16 / 2
2.7.6 16 / 2
2.7.5 15 / 2
2.7.4 15 / 2
2.7.3 15 / 2
2.7.2 15 / 2
2.7.1 15 / 2
2.7.0 15 / 2
2.6.2 16 / 1
2.6.1 16 / 1
2.6.0 16 / 1
2.5.2 16 / 1
2.5.1 16 / 1
2.5.0 16 / 1
2.4.10 16 / 1
2.4.9 16 / 1
2.4.8 16 / 1
2.4.7 16 / 1
2.4.6 16 / 1
2.4.5 16 / 1
Showing 100 of 118 Next page →

v2.19.4

2 findings
HIGH Publisher changed: gancho_walletconnect → reown-npm-org (on 2025-04-15) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.19.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.19.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.19.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.18.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.18.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.17.5

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.17.4

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.17.3

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.17.2

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.17.1

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.17.0

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.16.3

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.16.2

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.16.1

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.16.0

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.15.3

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.15.2

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.15.1

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.15.0

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.14.0

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.13.3

3 findings
HIGH Publisher changed: gancho_walletconnect → lukaisailovic (on 2024-06-14) provenance

This version was published by a different npm account than previous versions on 2024-06-14. This could indicate a legitimate maintainer transition or an account compromise.

HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.13.2

3 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: gancho_walletconnect → bkrem (on 2024-06-10, known maintainer) provenance

This version was published by a different npm account (bkrem) than the most recent previously approved version (gancho_walletconnect) on 2024-06-10, but bkrem is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.13.1

2 findings
HIGH Long encoded string in modified file: dist/index.umd.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.13.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.12.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.12.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.11.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.11.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.11.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.10.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.10.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.10.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.10.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.10.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.10.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.9.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.9.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.8.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.8.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.8.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.8.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.8.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.6.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.5.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.