← Home

@walletconnect/sign-client

npm Repository Homepage

Sign Client 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/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 100 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
2.15.0 9 / 4
2.14.0 9 / 4
2.13.3 9 / 4
2.13.2 9 / 4
2.13.1 9 / 4
2.13.0 9 / 4
2.12.2 9 / 4
2.12.1 9 / 4
2.12.0 9 / 4
2.11.3 9 / 5
2.11.2 9 / 5
2.11.1 9 / 5
2.11.0 9 / 5
2.10.6 9 / 5
2.10.5 9 / 5
2.10.4 9 / 5
2.10.3 9 / 5
2.10.2 9 / 5
2.10.1 9 / 5
2.10.0 9 / 5
2.9.2 9 / 5
2.9.1 9 / 5
2.9.0 9 / 5
2.8.6 9 / 5
2.8.5 9 / 5
2.8.4 9 / 5
2.8.3 9 / 5
2.8.2 9 / 5
2.8.1 9 / 5
2.8.0 9 / 5
2.7.8 9 / 5
2.7.7 9 / 5
2.7.6 9 / 5
2.7.5 9 / 5
2.7.4 9 / 5
2.7.3 9 / 5
2.7.2 9 / 5
2.7.1 9 / 5
2.7.0 9 / 5
2.6.2 10 / 5
2.6.1 10 / 5
2.6.0 10 / 5
2.5.2 10 / 5
2.5.1 10 / 5
2.5.0 10 / 5
2.4.10 10 / 5
2.4.9 11 / 4
2.4.8 11 / 4
2.4.7 11 / 4
Showing 100 of 120 Next page →

v2.20.0

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

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.