@walletconnect/sign-client 2.21.9

Sign Client for WalletConnect Protocol

@walletconnect/sign-client@2.21.9 was published on 2025-09-18. Its manifest declares 9 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @walletconnect/sign-client versions · Permanent reference to 2.21.9 · Latest release

Package specifications

Version2.21.9
License declarationSEE LICENSE IN LICENSE.md
Published2025-09-18T13:32:03.686Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count9
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size3139.10 KiB
Published file count50
Package typeNot declared
ES module entrydist/index.es.js
Default entrydist/index.cjs.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies95
Repository stars1688
Repository forks818

Install @walletconnect/sign-client 2.21.9

npm install @walletconnect/sign-client@2.21.9
pnpm add @walletconnect/sign-client@2.21.9
yarn add @walletconnect/sign-client@2.21.9

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained10/10 — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Code-Review4/10 — Found 4/10 approved changesets -- score normalized to 4
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts9/10 — binaries present in source code
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
License9/10 — license file detected
Security-Policy0/10 — security policy file not detected
Branch-Protection5/10 — branch protection is not maximal on development and all release branches
Fuzzing0/10 — project is not fuzzed
Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4
Packaging10/10 — packaging workflow detected
SAST8/10 — SAST tool is not run on all commits -- score normalized to 8

Evidence and freshness