← Home

@walletconnect/utils

npm Repository Homepage

Utilities 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:query-string AI (phantom-deps): Config-file reference, common false positive for this package. ai
dependencies unvetted-dep:elliptic AI (dependencies): Established crypto lib used for legit ECDSA in this package. ai
source-diff encoded-string-file:dist/index.umd.js AI (source-diff): Rollup UMD bundle output, not obfuscation. ai
source-diff encoded-string-file:dist/index.es.js AI (source-diff): Rollup bundle output, not obfuscation. ai
source-diff encoded-string-file:dist/index.cjs.js AI (source-diff): Rollup bundle output, not obfuscation; stable for this build pipeline. ai
maintainer-change maintainer-added AI (maintainer-change): Same handoff; stable across versions. ai
provenance publisher-changed AI (provenance): Legitimate maintainer transition on established WalletConnect org package; publisher has clean track record. ai
source-diff obfuscated-file:dist/index.js AI (source-diff): Standard Rollup bundle output; not obfuscated. Stable for this package. ai
source-diff obfuscated-file:dist/index.cjs AI (source-diff): Standard Rollup bundle output; not obfuscated. Stable for this package. ai
publish-pattern new-deps-added AI (publish-pattern): ox is a vetted Ethereum primitives lib replacing viem; not a suspicious addition for this package. ai
phantom-deps phantom-dep:@walletconnect/safe-json AI (phantom-deps): Same-org WalletConnect package; phantom finding reflects monorepo bundler config usage, not a real risk. ai
phantom-deps phantom-dep:@noble/ciphers AI (phantom-deps): @noble/ciphers is a reputable cryptography library; phantom finding reflects monorepo bundler config usage, not a real risk for this package. ai
phantom-deps phantom-dep:@noble/hashes AI (phantom-deps): @noble/hashes is a reputable cryptography library; phantom finding reflects monorepo bundler config usage, not a real risk for this package. ai
phantom-deps phantom-dep:@noble/curves AI (phantom-deps): @noble/curves is a reputable cryptography library; phantom finding reflects monorepo bundler config usage, not a real risk for this package. ai
bogus-package bogus-package AI (bogus-package): WalletConnect rebranded to Reown; new publisher account but same canonical monorepo with SLSA provenance. Inflated semver is continuation of existing version line. ai

Versions (showing 100 of 106)

Version Deps Published
2.23.10 19 / 2
2.23.9 19 / 2
2.23.8 19 / 2
2.23.7 19 / 2
2.23.6 19 / 2
2.23.5 19 / 2
2.23.4 20 / 2
2.23.3 20 / 2
2.23.2 20 / 2
2.23.1 20 / 2
2.23.0 20 / 2
2.22.4 20 / 2
2.22.3 20 / 2
2.22.2 20 / 2
2.22.1 19 / 2
2.22.0 19 / 2
2.21.10 19 / 2
2.21.9 19 / 2
2.21.8 20 / 2
2.21.7 20 / 2
2.21.6 20 / 2
2.21.5 20 / 2
2.21.4 20 / 2
2.21.3 20 / 2
2.21.2 20 / 2
2.21.1 17 / 2
2.21.0 17 / 2
2.20.3 17 / 2
2.20.2 17 / 2
2.20.1 17 / 2
2.20.0 17 / 2
2.19.4 17 / 2
2.19.3 17 / 2
2.19.2 17 / 2
2.18.0 17 / 4
2.16.3 16 / 2
2.16.2 16 / 2
2.15.1 14 / 1
2.14.0 14 / 1
2.13.3 14 / 1
2.13.2 14 / 1
2.13.1 14 / 1
2.13.0 14 / 1
2.12.2 14 / 1
2.12.1 14 / 1
2.12.0 14 / 1
2.11.3 14 / 1
2.11.2 14 / 1
2.11.1 14 / 1
2.11.0 14 / 1
2.10.6 14 / 1
2.10.5 14 / 1
2.10.4 14 / 1
2.10.3 14 / 1
2.10.2 14 / 1
2.10.1 14 / 1
2.10.0 14 / 1
2.9.2 14 / 1
2.9.1 14 / 1
2.9.0 14 / 1
2.8.6 14 / 1
2.8.5 14 / 1
2.8.4 14 / 1
2.8.3 14 / 1
2.8.2 14 / 1
2.8.1 14 / 1
2.8.0 14 / 1
2.7.8 14 / 1
2.7.7 14 / 1
2.7.6 14 / 1
2.7.5 15 / 1
2.7.4 15 / 1
2.7.3 15 / 1
2.7.2 15 / 1
2.7.1 15 / 1
2.7.0 15 / 1
2.6.2 15 / 1
2.6.1 15 / 1
2.6.0 15 / 1
2.5.2 15 / 1
2.5.1 15 / 1
2.5.0 15 / 1
2.4.10 15 / 1
2.4.9 15 / 1
2.4.8 15 / 1
2.4.7 15 / 1
2.4.6 15 / 1
2.4.5 15 / 1
2.4.4 15 / 1
2.4.3 15 / 1
2.4.2 15 / 1
2.4.1 15 / 1
2.4.0 15 / 1
2.3.3 15 / 1
2.3.2 15 / 1
2.3.1 15 / 1
2.3.0 15 / 1
2.2.1 15 / 1
2.2.0 15 / 1
2.1.5 15 / 1
Showing 100 of 106 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

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: bkrem → gancho_walletconnect (on 2025-03-26, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (bkrem) on 2025-03-26, but gancho_walletconnect 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.18.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: bkrem → gancho_walletconnect (on 2025-01-29, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (bkrem) on 2025-01-29, but gancho_walletconnect 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.16.3

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

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

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

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

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: bkrem → gancho_walletconnect (on 2024-09-30, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (bkrem) on 2024-09-30, but gancho_walletconnect 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.16.2

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

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

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

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

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: bkrem → gancho_walletconnect (on 2024-09-18, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (bkrem) on 2024-09-18, but gancho_walletconnect 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.15.1

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

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

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

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

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: bkrem → gancho_walletconnect (on 2024-08-20, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (bkrem) on 2024-08-20, but gancho_walletconnect 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.14.0

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

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

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

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

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: bkrem → gancho_walletconnect (on 2024-07-18, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (bkrem) on 2024-07-18, but gancho_walletconnect 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.3

2 findings
HIGH Publisher changed: bkrem → 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.

LOW No provenance attestation provenance

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

v2.13.2

2 findings
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

1 finding
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. Consider requesting the maintainer enable provenance via CI/CD.

v2.12.1

1 finding
LOW No provenance attestation provenance

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

v2.12.0

1 finding
LOW No provenance attestation provenance

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

v2.11.3

1 finding
LOW No provenance attestation provenance

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

v2.11.2

1 finding
LOW No provenance attestation provenance

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

v2.11.1

1 finding
LOW No provenance attestation provenance

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

v2.11.0

1 finding
LOW No provenance attestation provenance

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

v2.10.6

1 finding
LOW No provenance attestation provenance

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

v2.10.5

1 finding
LOW No provenance attestation provenance

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

v2.10.4

1 finding
LOW No provenance attestation provenance

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

v2.10.3

1 finding
LOW No provenance attestation provenance

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

v2.10.2

1 finding
LOW No provenance attestation provenance

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

v2.10.1

1 finding
LOW No provenance attestation provenance

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

v2.10.0

1 finding
LOW No provenance attestation provenance

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

v2.9.2

1 finding
LOW No provenance attestation provenance

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

v2.9.1

1 finding
LOW No provenance attestation provenance

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

v2.9.0

1 finding
LOW No provenance attestation provenance

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

v2.8.6

2 findings
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 → iljadoesdev (on 2023-06-29, known maintainer) provenance

This version was published by a different npm account (iljadoesdev) than the most recent previously approved version (gancho_walletconnect) on 2023-06-29, but iljadoesdev 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.8.5

1 finding
LOW No provenance attestation provenance

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

v2.8.4

1 finding
LOW No provenance attestation provenance

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

v2.8.3

2 findings
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 → iljadoesdev (on 2023-06-26, known maintainer) provenance

This version was published by a different npm account (iljadoesdev) than the most recent previously approved version (gancho_walletconnect) on 2023-06-26, but iljadoesdev 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.8.2

1 finding
LOW No provenance attestation provenance

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

v2.8.1

2 findings
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 2023-06-15, known maintainer) provenance

This version was published by a different npm account (bkrem) than the most recent previously approved version (gancho_walletconnect) on 2023-06-15, 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.8.0

1 finding
LOW No provenance attestation provenance

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

v2.7.8

1 finding
LOW No provenance attestation provenance

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

v2.7.7

1 finding
LOW No provenance attestation provenance

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

v2.7.6

1 finding
LOW No provenance attestation provenance

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

v2.7.5

1 finding
LOW No provenance attestation provenance

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

v2.7.4

1 finding
LOW No provenance attestation provenance

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

v2.7.3

1 finding
LOW No provenance attestation provenance

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

v2.7.2

1 finding
LOW No provenance attestation provenance

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

v2.7.1

1 finding
LOW No provenance attestation provenance

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

v2.7.0

1 finding
LOW No provenance attestation provenance

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

v2.6.2

2 findings
LOW No provenance attestation provenance

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

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

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (bkrem) on 2023-04-06, but gancho_walletconnect 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.6.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: bkrem → gancho_walletconnect (on 2023-04-05, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (bkrem) on 2023-04-05, but gancho_walletconnect 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.6.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: iljadoesdev → bkrem (on 2023-04-03, known maintainer) provenance

This version was published by a different npm account (bkrem) than the most recent previously approved version (iljadoesdev) on 2023-04-03, 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.5.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: iljadoesdev → gancho_walletconnect (on 2023-03-23, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (iljadoesdev) on 2023-03-23, but gancho_walletconnect 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.5.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: bkrem → iljadoesdev (on 2023-03-16, known maintainer) provenance

This version was published by a different npm account (iljadoesdev) than the most recent previously approved version (bkrem) on 2023-03-16, but iljadoesdev 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.5.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: bkrem → iljadoesdev (on 2023-03-15, known maintainer) provenance

This version was published by a different npm account (iljadoesdev) than the most recent previously approved version (bkrem) on 2023-03-15, but iljadoesdev 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.4.10

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: iljadoesdev → bkrem (on 2023-03-13, known maintainer) provenance

This version was published by a different npm account (bkrem) than the most recent previously approved version (iljadoesdev) on 2023-03-13, 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.4.9

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: iljadoesdev → gancho_walletconnect (on 2023-03-10, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (iljadoesdev) on 2023-03-10, but gancho_walletconnect 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.4.8

1 finding
LOW No provenance attestation provenance

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

v2.4.7

2 findings
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 → iljadoesdev (on 2023-03-03, known maintainer) provenance

This version was published by a different npm account (iljadoesdev) than the most recent previously approved version (gancho_walletconnect) on 2023-03-03, but iljadoesdev 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.4.6

1 finding
LOW No provenance attestation provenance

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

v2.4.5

1 finding
LOW No provenance attestation provenance

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

v2.4.4

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: iljadoesdev → gancho_walletconnect (on 2023-02-16, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (iljadoesdev) on 2023-02-16, but gancho_walletconnect 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.4.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: iljadoesdev → gancho_walletconnect (on 2023-02-14, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (iljadoesdev) on 2023-02-14, but gancho_walletconnect 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.4.2

2 findings
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 → iljadoesdev (on 2023-02-13, known maintainer) provenance

This version was published by a different npm account (iljadoesdev) than the most recent previously approved version (gancho_walletconnect) on 2023-02-13, but iljadoesdev 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.4.1

1 finding
LOW No provenance attestation provenance

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

v2.4.0

1 finding
LOW No provenance attestation provenance

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

v2.3.3

2 findings
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 → iljadoesdev (on 2023-02-01, known maintainer) provenance

This version was published by a different npm account (iljadoesdev) than the most recent previously approved version (gancho_walletconnect) on 2023-02-01, but iljadoesdev 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.3.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: devceline → gancho_walletconnect (on 2023-01-26, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (devceline) on 2023-01-26, but gancho_walletconnect 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.3.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: devceline → gancho_walletconnect (on 2023-01-25, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (devceline) on 2023-01-25, but gancho_walletconnect 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.3.0

2 findings
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 → devceline (on 2023-01-23, known maintainer) provenance

This version was published by a different npm account (devceline) than the most recent previously approved version (gancho_walletconnect) on 2023-01-23, but devceline 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.2.1

2 findings
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 → iljadoesdev (on 2023-01-10, known maintainer) provenance

This version was published by a different npm account (iljadoesdev) than the most recent previously approved version (gancho_walletconnect) on 2023-01-10, but iljadoesdev 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.2.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: bkrem → gancho_walletconnect (on 2023-01-05, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (bkrem) on 2023-01-05, but gancho_walletconnect 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.1.5

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: bkrem → gancho_walletconnect (on 2022-12-22, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (bkrem) on 2022-12-22, but gancho_walletconnect 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.