VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@walletconnect/logger: vulnerability history, versions and safety

@walletconnect/logger is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @walletconnect/logger vulnerabilities

Vulert verdict on @walletconnect/logger 3.0.2 i

Updated on 23 Oct 2026

Good news: 3.0.2, the version you would install today, has no known vulnerabilities.

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

What to do: Stay on 3.0.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.0.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.0.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 17,012 packages i
  • Stars 133 i
  • OpenSSF scorecard 4/10 i
  • Last release 9 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @walletconnect/logger, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.0.2 09 Jan 2026 none MIT — Details →
3.0.2-canary-0 09 Jan 2026 none MIT — Details →
3.0.1 11 Dec 2025 none MIT — Details →
3.0.0-canary-1 10 Dec 2025 none MIT — Details →
3.0.0 09 Oct 2025 none MIT — Details →
2.1.3-canary-p-2 09 Oct 2025 none MIT — Details →
2.1.3-canary-p-1 09 Oct 2025 none MIT — Details →
2.1.2-canary-p-2 08 Oct 2025 none MIT — Details →
2.1.3 08 Oct 2025 none MIT — Details →
2.1.2-canary-p-1 08 Oct 2025 none MIT — Details →
2.1.2 08 Apr 2024 none MIT — Details →
2.1.2-98c4166 08 Apr 2024 none MIT — Details →
2.1.1 08 Apr 2024 none MIT — Details →
2.1.0 26 Mar 2024 none MIT — Details →
2.1.0-1385741 22 Mar 2024 none MIT — Details →
2.1.0-27c6d93 22 Mar 2024 none MIT — Details →
2.1.0-e8db983 21 Mar 2024 none MIT — Details →
2.1.0-cab1ccc 21 Mar 2024 none MIT — Details →
2.1.0-5a8e178 21 Mar 2024 none MIT — Details →
2.1.0-b750420 18 Mar 2024 none MIT — Details →
2.0.1 25 Nov 2022 none MIT — Details →
2.0.0-rc-aa30f361 22 Nov 2022 none MIT — Details →
2.0.0-rc-be5347f3 18 Nov 2022 none MIT — Details →
2.0.0-rc-caab26e7 18 Nov 2022 none MIT — Details →
2.0.0-rc-57af4ea9 15 Nov 2022 none MIT — Details →
2.0.0 10 Nov 2022 none MIT — Details →
1.0.1-rc-ba731f71 10 Nov 2022 none MIT — Details →
1.0.1 14 Jun 2022 none MIT — Details →
1.0.0 28 Jul 2021 none MIT — Details →
1.0.0-beta.1 26 Jul 2021 none MIT — Details →

All 30 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for @walletconnect/logger

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @walletconnect/logger

Is @walletconnect/logger safe to use?

Vulert has no vulnerabilities on record for @walletconnect/logger in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is @walletconnect/logger's Vulert package health score?

Vulert scores @walletconnect/logger 77/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @walletconnect/logger affected?

No. 3.0.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of @walletconnect/logger should I use?

3.0.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @walletconnect/logger have?

0 vulnerabilities are recorded for @walletconnect/logger in the npm ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @walletconnect/logger vulnerabilities disclosed?

0 vulnerabilities were recorded for @walletconnect/logger in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @walletconnect/logger are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @walletconnect/logger for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @walletconnect/logger version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.