@walletconnect/signer-connection SEE LICENSE IN LICENSE.md 51 versions

@walletconnect/signer-connection

npm Repository Homepage

Signer Connection for WalletConnect Protocol

51

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.

Source	Rule	Reason	Accepted by	When
source-diff	encoded-string-file:dist/index.umd.js	AI (source-diff): Bundled UMD build output, not true obfuscation; no malicious behavior found.	ai	2026/07/19
maintainer-change	maintainer-added	AI (maintainer-change): Stale publisher change, long-standing, part of official WalletConnect org.	ai	2026/07/19
source-diff	obfuscated-file:dist/index.cjs	AI (source-diff): Standard rollup minified bundle for WalletConnect SDK; content is readable WalletConnect logic, not obfuscated malware.	ai	2026/05/26
source-diff	obfuscated-file:dist/index.js	AI (source-diff): Standard rollup ESM bundle; same pattern as dist/index.cjs, no malicious content.	ai	2026/05/26
phantom-deps	phantom-dep:uint8arrays	AI (phantom-deps): uint8arrays is a declared dependency used transitively; phantom-dep heuristic false positive for this package.	ai	2026/05/26

Versions (showing 51 of 56)

View all versions

Version	Deps	Published
2.23.10	7 / 0	2026-06-24
2.23.9	7 / 0	2026-03-27
2.23.8	7 / 0	2026-03-10
2.23.7	7 / 0	2026-02-27
2.23.6	7 / 0	2026-02-18
2.23.5	7 / 0	2026-02-11
2.23.4	7 / 0	2026-01-21
2.23.3	7 / 0	2026-01-14
2.23.2	7 / 0	2026-01-13
2.23.1	7 / 0	2025-12-11
2.23.0	7 / 0	2025-10-30
2.22.4	7 / 0	2025-10-14
2.22.3	7 / 0	2025-10-11
2.22.2	7 / 0	2025-10-08
2.22.1	7 / 0	2025-10-08
2.22.0	7 / 0	2025-10-08
2.21.10	7 / 0	2025-09-30
2.21.9	7 / 0	2025-09-18
2.21.8	7 / 0	2025-08-11
2.21.7	7 / 0	2025-08-07
2.21.6	7 / 0	2025-07-31
2.21.5	7 / 0	2025-07-17
2.21.4	7 / 0	2025-06-25
2.21.3	7 / 0	2025-06-16
2.21.2	7 / 0	2025-06-09
2.21.1	7 / 0	2025-06-03
2.21.0	7 / 0	2025-05-29
2.20.3	7 / 0	2025-05-20
2.20.2	7 / 0	2025-05-01
2.20.1	7 / 0	2025-05-01
2.20.0	7 / 0	2025-04-15
2.19.4	7 / 0	2025-04-15
2.19.3	7 / 0	2025-04-15
2.19.2	7 / 0	2025-03-26
2.19.1	7 / 0	2025-03-12
2.19.0	7 / 0	2025-02-26
2.18.1	7 / 0	2025-02-18
2.18.0	7 / 0	2025-01-29
2.17.5	7 / 0	2025-01-21
2.17.4	7 / 0	2025-01-16
2.17.3	7 / 0	2024-12-16
2.17.2	7 / 0	2024-11-05
2.17.1	7 / 0	2024-10-09
2.17.0	7 / 0	2024-10-01
2.16.3	7 / 0	2024-09-30
2.16.2	7 / 0	2024-09-18
2.16.1	7 / 0	2024-09-09
2.16.0	7 / 0	2024-09-06
2.15.3	7 / 0	2024-09-05
2.15.2	7 / 0	2024-08-30
2.15.1	7 / 0	2024-08-20

v2.20.3

2 findings

MEDIUM Publisher changed: gancho_walletconnect → reown-npm-org (on 2025-05-20, unremoved on npm for 424d) provenance

This version was published by a different npm account (reown-npm-org) than the most recent previously approved version (gancho_walletconnect) on 2025-05-20. It has since remained available on npm for 424 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.20.2

2 findings

MEDIUM Publisher changed: gancho_walletconnect → reown-npm-org (on 2025-05-01, unremoved on npm for 443d) provenance

This version was published by a different npm account (reown-npm-org) than the most recent previously approved version (gancho_walletconnect) on 2025-05-01. It has since remained available on npm for 443 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.20.1

2 findings

MEDIUM Publisher changed: gancho_walletconnect → reown-npm-org (on 2025-05-01, unremoved on npm for 443d) provenance

This version was published by a different npm account (reown-npm-org) than the most recent previously approved version (gancho_walletconnect) on 2025-05-01. It has since remained available on npm for 443 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.20.0

2 findings

MEDIUM Publisher changed: gancho_walletconnect → reown-npm-org (on 2025-04-15, unremoved on npm for 459d) provenance

This version was published by a different npm account (reown-npm-org) than the most recent previously approved version (gancho_walletconnect) on 2025-04-15. It has since remained available on npm for 459 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

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

MEDIUM Publisher changed: gancho_walletconnect → reown-npm-org (on 2025-04-15, unremoved on npm for 459d) provenance

This version was published by a different npm account (reown-npm-org) than the most recent previously approved version (gancho_walletconnect) on 2025-04-15. It has since remained available on npm for 459 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

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

MEDIUM Publisher changed: gancho_walletconnect → reown-npm-org (on 2025-04-15, unremoved on npm for 459d) provenance

This version was published by a different npm account (reown-npm-org) than the most recent previously approved version (gancho_walletconnect) on 2025-04-15. It has since remained available on npm for 459 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

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.