VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

libp2p-crypto: vulnerability history, versions and safety

libp2p-crypto 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-crypto vulnerabilities

Vulert verdict on libp2p-crypto 0.21.2 i

Updated on 23 Oct 2026

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

Package health score 53/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Quiet

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

  • Current release 0.21.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 577 packages i
  • Stars 79 i
  • OpenSSF scorecard 2/10 i
  • Last release 57 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 libp2p-crypto, 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
0.21.2 20 Jan 2022 none MIT — Details →
0.21.1 18 Jan 2022 none MIT — Details →
0.21.0 01 Dec 2021 none MIT — Details →
0.20.0 21 Oct 2021 none MIT — Details →
0.19.7 18 Aug 2021 none MIT — Details →
0.16.4 30 Jul 2021 none MIT — Details →
0.19.6 15 Jul 2021 none MIT — Details →
0.19.5 07 Jul 2021 none MIT — Details →
0.19.4 20 Apr 2021 none MIT — Details →
0.19.3 11 Apr 2021 none MIT — Details →
0.19.2 17 Mar 2021 none MIT — Details →
0.19.1 15 Mar 2021 none MIT — Details →
0.19.0 15 Jan 2021 none MIT — Details →
0.18.0 07 Aug 2020 none MIT — Details →
0.17.9 05 Aug 2020 none MIT — Details →
0.17.8 20 Jul 2020 none MIT — Details →
0.17.7 09 Jun 2020 none MIT — Details →
0.17.6 07 Apr 2020 none MIT — Details →
0.17.5 24 Mar 2020 none MIT — Details →
0.17.4 23 Mar 2020 none MIT — Details →
0.17.3 26 Feb 2020 none MIT — Details →
0.17.2 17 Jan 2020 none MIT — Details →
0.16.3 25 Oct 2019 none MIT — Details →
0.17.1 25 Oct 2019 none MIT — Details →
0.16.2 25 Sep 2019 none MIT — Details →
0.17.0 11 Jul 2019 none MIT — Details →
0.16.1 26 Feb 2019 none MIT — Details →
0.16.0 08 Jan 2019 none MIT — Details →
0.15.0 03 Jan 2019 none MIT — Details →
0.14.1 05 Nov 2018 none MIT — Details →
0.14.0 17 Sep 2018 none MIT — Details →
0.13.0 05 Apr 2018 none MIT — Details →
0.12.1 12 Feb 2018 none MIT — Details →
0.12.0 27 Jan 2018 none MIT — Details →
0.11.0 20 Dec 2017 none MIT — Details →
0.10.4 01 Dec 2017 none MIT — Details →
0.10.3 07 Sep 2017 none MIT — Details →
0.10.2 06 Sep 2017 none MIT — Details →
0.10.0 03 Sep 2017 none MIT — Details →
0.9.4 22 Jul 2017 none MIT — Details →
0.9.3 22 Jul 2017 none MIT — Details →
0.9.2 22 Jul 2017 none MIT — Details →
0.9.1 22 Jul 2017 none MIT — Details →
0.9.0 22 Jul 2017 none MIT — Details →
0.8.8 11 Apr 2017 none MIT — Details →
0.8.7 21 Mar 2017 none MIT — Details →
0.8.6 03 Mar 2017 none MIT — Details →
0.8.5 11 Feb 2017 none MIT — Details →
0.8.4 11 Feb 2017 none MIT — Details →
0.8.3 11 Feb 2017 none MIT — Details →
0.8.2 10 Feb 2017 none MIT — Details →
0.8.1 09 Feb 2017 none MIT — Details →
0.8.0 07 Feb 2017 none MIT — Details →
0.7.7 27 Jan 2017 none MIT — Details →
0.7.6 16 Jan 2017 none MIT — Details →
0.7.5 13 Dec 2016 none MIT — Details →
0.7.4 06 Dec 2016 none MIT — Details →
0.7.3 01 Dec 2016 none MIT — Details →
0.7.2 30 Nov 2016 none MIT — Details →
0.7.1 11 Nov 2016 none MIT — Details →
0.7.0 03 Nov 2016 none MIT — Details →
0.6.1 11 Sep 2016 none MIT — Details →
0.6.0 11 Sep 2016 none MIT — Details →
0.5.0 24 May 2016 none MIT — Details →
0.4.0 23 May 2016 none MIT — Details →
0.3.1 20 May 2016 none MIT — Details →
0.3.0 20 May 2016 none MIT — Details →

All 67 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 libp2p-crypto

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-crypto

Is libp2p-crypto safe to use?

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

Vulert scores libp2p-crypto 53/100, which reads as usable, but worth attention. 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-crypto affected?

No. 0.21.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 libp2p-crypto should I use?

0.21.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 libp2p-crypto have?

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

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

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