@walletconnect/types 2.6.2-rc-verify

Typings for WalletConnect Protocol

@walletconnect/types@2.6.2-rc-verify was published on 2023-04-06. Its manifest declares 6 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/types versions · Permanent reference to 2.6.2-rc-verify · Latest release

Package specifications

Version2.6.2-rc-verify
License declarationApache-2.0
Published2023-04-06T12:59:37.933Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count6
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size228.33 KiB
Published file count51
Package typeNot declared
ES module entrydist/index.es.js
Default entrydist/index.cjs.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies143
Repository stars1688
Repository forks818

Install @walletconnect/types 2.6.2-rc-verify

npm install @walletconnect/types@2.6.2-rc-verify
pnpm add @walletconnect/types@2.6.2-rc-verify
yarn add @walletconnect/types@2.6.2-rc-verify

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