VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@libp2p/pubsub: vulnerability history, versions and safety

@libp2p/pubsub 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 @libp2p/pubsub vulnerabilities

Vulert verdict on @libp2p/pubsub 10.1.18 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Moderate

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

  • Current release 10.1.18 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 198 packages i
  • Stars 2,584 i
  • OpenSSF scorecard 4/10 i
  • Last release 14 months ago i
  • Licence Apache-2.0 OR 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 @libp2p/pubsub, 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
10.1.18-87bc8d4fb 22 Sep 2025 none Apache-2.0 OR MIT — Details →
10.1.18-da78fa851 19 Sep 2025 none Apache-2.0 OR MIT — Details →
10.1.18-8484de8a2 08 Sep 2025 none Apache-2.0 OR MIT — Details →
10.1.18-0f07e3df5 05 Sep 2025 none Apache-2.0 OR MIT — Details →
10.1.18-a02cb0461 04 Sep 2025 none Apache-2.0 OR MIT — Details →
10.1.18-f5932c294 20 Aug 2025 none Apache-2.0 OR MIT — Details →
10.1.18 20 Aug 2025 none Apache-2.0 OR MIT — Details →
10.1.17-5ed83dd69 19 Aug 2025 none Apache-2.0 OR MIT — Details →
10.1.17-aa770ab81 17 Aug 2025 none Apache-2.0 OR MIT — Details →
10.1.17-7ce083dca 14 Aug 2025 none Apache-2.0 OR MIT — Details →
10.1.17-cf9aab5c8 30 Jul 2025 none Apache-2.0 OR MIT — Details →
10.1.17-cb1c14e62 24 Jul 2025 none Apache-2.0 OR MIT — Details →
10.1.17-4420fad68 13 Jul 2025 none Apache-2.0 OR MIT — Details →
10.1.17-79473c99a 10 Jul 2025 none Apache-2.0 OR MIT — Details →
10.1.17-ce6b542a8 09 Jul 2025 none Apache-2.0 OR MIT — Details →
10.1.17-58abe8702 09 Jul 2025 none Apache-2.0 OR MIT — Details →
10.1.17-87e5d5938 08 Jul 2025 none Apache-2.0 OR MIT — Details →
10.1.17-57e7fa441 07 Jul 2025 none Apache-2.0 OR MIT — Details →
10.1.17-cfe2be4c9 03 Jul 2025 none Apache-2.0 OR MIT — Details →
10.1.17 25 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.16-2d6079bc1 25 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.16-8ad44f759 25 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.16-d2dc12c7d 25 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.16-451e011d4 18 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.16-53001addf 18 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.16-439d2c9ce 17 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.16 17 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.15-7eed3b40d 17 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.15 16 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.14-6c42ea64a 16 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.14-ae595d8db 13 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.14 03 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.13-8e87be9e6 03 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.13-bb4ad31db 03 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.13-cc7b34c0f 03 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.13-b8600fce8 03 Jun 2025 none Apache-2.0 OR MIT — Details →
10.1.13-6a3ae02f5 30 May 2025 none Apache-2.0 OR MIT — Details →
10.1.13-307d0ba58 30 May 2025 none Apache-2.0 OR MIT — Details →
10.1.13-ec73d59a6 30 May 2025 none Apache-2.0 OR MIT — Details →
10.1.13-2a7425cdb 30 May 2025 none Apache-2.0 OR MIT — Details →
10.1.13-dbbc6ef1d 30 May 2025 none Apache-2.0 OR MIT — Details →
10.1.13-d91ae66c6 29 May 2025 none Apache-2.0 OR MIT — Details →
10.1.13-3528df829 29 May 2025 none Apache-2.0 OR MIT — Details →
10.1.13-b32bc8406 28 May 2025 none Apache-2.0 OR MIT — Details →
10.1.13-5b004c0c4 28 May 2025 none Apache-2.0 OR MIT — Details →
10.1.13-8efb065d2 28 May 2025 none Apache-2.0 OR MIT — Details →
10.1.13-14dbebea8 24 May 2025 none Apache-2.0 OR MIT — Details →
10.1.13-9f1be6742 24 May 2025 none Apache-2.0 OR MIT — Details →
10.1.13 23 May 2025 none Apache-2.0 OR MIT — Details →
10.1.12-ab014c0c0 22 May 2025 none Apache-2.0 OR MIT — Details →
10.1.12-7788b4025 22 May 2025 none Apache-2.0 OR MIT — Details →
10.1.12-776cb432d 21 May 2025 none Apache-2.0 OR MIT — Details →
10.1.12 20 May 2025 none Apache-2.0 OR MIT — Details →
10.1.11-aa25d38ab 20 May 2025 none Apache-2.0 OR MIT — Details →
10.1.11 19 May 2025 none Apache-2.0 OR MIT — Details →
10.1.10-3df5bf2da 19 May 2025 none Apache-2.0 OR MIT — Details →
10.1.10-3577af88a 19 May 2025 none Apache-2.0 OR MIT — Details →
10.1.10-32627c876 17 May 2025 none Apache-2.0 OR MIT — Details →
10.1.10-213a54a1e 16 May 2025 none Apache-2.0 OR MIT — Details →
10.1.10-185b23eac 14 May 2025 none Apache-2.0 OR MIT — Details →
10.1.10-4b8c0a6bd 14 May 2025 none Apache-2.0 OR MIT — Details →
10.1.10-a5a33afd9 12 May 2025 none Apache-2.0 OR MIT — Details →
10.1.10-9b33d202e 12 May 2025 none Apache-2.0 OR MIT — Details →
10.1.10-f1de46607 07 May 2025 none Apache-2.0 OR MIT — Details →
10.1.10-772b4011e 07 May 2025 none Apache-2.0 OR MIT — Details →
10.1.10-cdc63e6cc 06 May 2025 none Apache-2.0 OR MIT — Details →
10.1.10-6f96de86c 17 Apr 2025 none Apache-2.0 OR MIT — Details →
10.1.10-afa5c9f59 17 Apr 2025 none Apache-2.0 OR MIT — Details →
10.1.10 16 Apr 2025 none Apache-2.0 OR MIT — Details →
10.1.9-f09bef843 16 Apr 2025 none Apache-2.0 OR MIT — Details →
10.1.9-3833353bd 16 Apr 2025 none Apache-2.0 OR MIT — Details →
10.1.9-b9e32cc37 15 Apr 2025 none Apache-2.0 OR MIT — Details →
10.1.9 09 Apr 2025 none Apache-2.0 OR MIT — Details →
10.1.8-4f37aff53 09 Apr 2025 none Apache-2.0 OR MIT — Details →
10.1.8-53a9be54e 09 Apr 2025 none Apache-2.0 OR MIT — Details →
10.1.8-da7353a0b 09 Apr 2025 none Apache-2.0 OR MIT — Details →
10.1.8-4c64bd06d 09 Apr 2025 none Apache-2.0 OR MIT — Details →
10.1.8-da4e9da82 08 Apr 2025 none Apache-2.0 OR MIT — Details →
10.1.8-d53ef170c 25 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.8-0b9090aea 25 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.8-78cd7d53e 25 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.8-fc5122110 25 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.8-71267286 20 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.8-b2124c2db 20 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.8 18 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.7-2f2322a25 18 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.7-95909c3df 18 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.7-a71c7c32b 18 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.7-907518bad 14 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.7-a7ab9a41b 14 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.7-757577dd2 13 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.7 12 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.6-0699fb747 12 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.6-600d0a561 07 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.6-a6c9aee5a 06 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.6-88b5c29ed 06 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.6-5fe2a18fc 04 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.6 04 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.5-48cd9b652 03 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.5-2fbcdb687 03 Mar 2025 none Apache-2.0 OR MIT — Details →
10.1.5-2c8ecb455 03 Mar 2025 none — — Details →
10.1.5-3f127b610 03 Mar 2025 none — — Details →
10.1.5-dd71d8a86 03 Mar 2025 none — — Details →
10.1.5-80fe31aa1 03 Mar 2025 none — — Details →
10.1.5 03 Mar 2025 none — — Details →
10.1.4-52a46ecad 03 Mar 2025 none — — Details →
10.1.4-3d9b07c34 27 Feb 2025 none — — Details →
10.1.4-9acccaaed 27 Feb 2025 none — — Details →
10.1.4-0555339ba 26 Feb 2025 none — — Details →
10.1.4-22e62d00f 26 Feb 2025 none — — Details →
10.1.4-4939ef7ae 26 Feb 2025 none — — Details →
10.1.4-96f79bc11 26 Feb 2025 none — — Details →
10.1.4-e1f868f03 26 Feb 2025 none — — Details →
10.1.4-e2f49432b 26 Feb 2025 none — — Details →
10.1.4 25 Feb 2025 none — — Details →
10.1.3-90cca822b 25 Feb 2025 none — — Details →
10.1.3-6f8cfeafb 24 Feb 2025 none — — Details →
10.1.3-f465c5473 23 Feb 2025 none — — Details →
10.1.3-5b084e968 23 Feb 2025 none — — Details →
10.1.3-e7e01f58f 23 Feb 2025 none — — Details →

The newest 120 of 782 versions Vulert tracks. 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 @libp2p/pubsub

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 @libp2p/pubsub

Is @libp2p/pubsub safe to use?

Vulert has no vulnerabilities on record for @libp2p/pubsub 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 @libp2p/pubsub's Vulert package health score?

Vulert scores @libp2p/pubsub 76/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 @libp2p/pubsub affected?

No. 10.1.18, 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 @libp2p/pubsub should I use?

10.1.18 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 @libp2p/pubsub have?

0 vulnerabilities are recorded for @libp2p/pubsub 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 @libp2p/pubsub vulnerabilities disclosed?

0 vulnerabilities were recorded for @libp2p/pubsub 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 @libp2p/pubsub 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 @libp2p/pubsub for upcoming vulnerabilities?

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