VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@libp2p/keychain: vulnerability history, versions and safety

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

Vulert verdict on @libp2p/keychain 6.1.10 i

Updated on 23 Oct 2026

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

Package health score 85/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 6.1.10 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 343 packages i
  • Stars 2,584 i
  • OpenSSF scorecard 4/10 i
  • Last release this month 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/keychain, 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
6.1.10-7fa88999d 19 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.10-c57bf6228 19 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.10-3da8bab7c 19 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.10-b927d5921 18 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.10-aa5ba42d0 18 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.10 18 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.9-2d4c93ed6 17 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.9-d1ce8bdbe 17 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.9-95392efdf 17 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.9-f0e64b9b8 17 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.9-57c4b4456 17 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.9-6d888970e 17 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.9 17 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.8-be63a4416 16 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.8-e48eabf67 16 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.8-e073d373d 15 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.8-4a416447c 12 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.8-974e63f20 11 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.8-5c4cdb2d6 10 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.8 10 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.7-e724dd173 10 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.7-9441e049a 10 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.7-fc90066f8 08 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.7-40480a034 05 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.7-235711723 05 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.7-16fba5630 03 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.7-183116ba0 03 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.7-a9bae64cb 03 Oct 2026 none Apache-2.0 OR MIT — Details →
6.1.7-776cdedf6 27 Sep 2026 none Apache-2.0 OR MIT — Details →
6.1.7-e7359e5f6 27 Sep 2026 none Apache-2.0 OR MIT — Details →
6.1.7-2f63792c7 27 Sep 2026 none Apache-2.0 OR MIT — Details →
6.1.7-fb139d1c8 23 Sep 2026 none Apache-2.0 OR MIT — Details →
6.1.7-d91797b55 16 Sep 2026 none Apache-2.0 OR MIT — Details →
6.1.7-5cb617ae2 02 Sep 2026 none Apache-2.0 OR MIT — Details →
6.1.7-185d901cd 02 Sep 2026 none Apache-2.0 OR MIT — Details →
6.1.7-cef4d32cf 31 Aug 2026 none Apache-2.0 OR MIT — Details →
6.1.7-ac7305ccf 31 Aug 2026 none Apache-2.0 OR MIT — Details →
6.1.7-87dca02b0 27 Aug 2026 none Apache-2.0 OR MIT — Details →
6.1.7-4a6c5d11a 27 Aug 2026 none Apache-2.0 OR MIT — Details →
6.1.7 23 Aug 2026 none Apache-2.0 OR MIT — Details →
6.1.6-947d304ed 22 Aug 2026 none Apache-2.0 OR MIT — Details →
6.1.6-0967e75f5 22 Aug 2026 none Apache-2.0 OR MIT — Details →
6.1.6-4dae661b4 22 Aug 2026 none Apache-2.0 OR MIT — Details →
6.1.6-8786aa8d0 20 Aug 2026 none Apache-2.0 OR MIT — Details →
6.1.6-55d7a539a 20 Aug 2026 none Apache-2.0 OR MIT — Details →
6.1.6-d5534174d 13 Aug 2026 none Apache-2.0 OR MIT — Details →
6.1.6-47cf9cdc1 10 Aug 2026 none Apache-2.0 OR MIT — Details →
6.1.6 30 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.5-ef6e1851c 30 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.5-423335b45 30 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.5 26 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-5927b62d6 26 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-68794c8e2 26 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-b500071e4 26 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-d9292b690 24 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-7f5500989 24 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-868b33379 20 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-e86b39e5d 20 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-05b15b2b1 19 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-02fcf704d 19 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-382fbb4ca 19 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-dee9df67f 19 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-d96b30ebd 19 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-99b23b2a0 19 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-ff9e5fc7c 19 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-523b52bd6 19 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-5459e136d 18 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-bd7f0cda6 17 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-3bf5d395c 17 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-89335e39f 17 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-ba1551199 17 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-cec2b1f34 17 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-084ad7890 17 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-fb9e8a76e 16 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-a04f5e0bf 15 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4-4bb8fbe8d 08 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.4 07 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.3-dd084c0b2 07 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.3-08898d7df 07 Jul 2026 none Apache-2.0 OR MIT — Details →
6.1.3-f144def15 22 Jun 2026 none Apache-2.0 OR MIT — Details →
6.1.3-47a51e3d1 20 Jun 2026 none Apache-2.0 OR MIT — Details →
6.1.3-d4dad9bf5 20 Jun 2026 none Apache-2.0 OR MIT — Details →
6.1.3-bfb7ceb0f 20 Jun 2026 none Apache-2.0 OR MIT — Details →
6.1.3 13 Jun 2026 none Apache-2.0 OR MIT — Details →
6.1.2-5e07d5963 13 Jun 2026 none Apache-2.0 OR MIT — Details →
6.1.2-404c7824a 12 Jun 2026 none Apache-2.0 OR MIT — Details →
6.1.2-7ae12f9b0 06 Jun 2026 none Apache-2.0 OR MIT — Details →
6.1.2-a34745c01 05 Jun 2026 none Apache-2.0 OR MIT — Details →
6.1.2 31 May 2026 none Apache-2.0 OR MIT — Details →
6.1.1-160a24585 30 May 2026 none Apache-2.0 OR MIT — Details →
6.1.1-5b8813abc 30 May 2026 none Apache-2.0 OR MIT — Details →
6.1.1-b7c6dc0f2 29 May 2026 none Apache-2.0 OR MIT — Details →
6.1.1-29797a5bb 29 May 2026 none Apache-2.0 OR MIT — Details →
6.1.1-d888f182f 27 May 2026 none Apache-2.0 OR MIT — Details →
6.1.1-ed1ad1f26 25 May 2026 none Apache-2.0 OR MIT — Details →
6.1.1-3574648c3 25 May 2026 none Apache-2.0 OR MIT — Details →
6.1.1-d59c165ac 18 May 2026 none Apache-2.0 OR MIT — Details →
6.1.1-b9ebef660 17 May 2026 none Apache-2.0 OR MIT — Details →
6.1.1-cc151e147 16 May 2026 none Apache-2.0 OR MIT — Details →
6.1.1-9eb27be79 15 May 2026 none Apache-2.0 OR MIT — Details →
6.1.1-5692f3f16 13 May 2026 none — — Details →
6.1.1-9c3c0b22a 12 May 2026 none — — Details →
6.1.1 11 May 2026 none — — Details →
6.1.0-15eeedba1 09 May 2026 none — — Details →
6.1.0-bd9e02dad 09 May 2026 none — — Details →
6.1.0-d1ab98294 04 May 2026 none — — Details →
6.1.0-3a5e46eaa 29 Apr 2026 none — — Details →
6.1.0-10b2bdf50 26 Apr 2026 none — — Details →
6.1.0 25 Apr 2026 none — — Details →
6.0.14-baf3ddb03 25 Apr 2026 none — — Details →
6.0.14-61d594a6c 25 Apr 2026 none — — Details →
6.0.14-d57fe74c0 24 Apr 2026 none — — Details →
6.0.14-5466a8def 24 Apr 2026 none — — Details →
6.0.14-cbfda2cdc 23 Apr 2026 none — — Details →
6.0.14-69a44651f 22 Apr 2026 none — — Details →
6.0.14-fd68eecf7 20 Apr 2026 none — — Details →
6.0.14-20bfcb3f9 20 Apr 2026 none — — Details →
6.0.14-7cea7b9a5 20 Apr 2026 none — — Details →
6.0.14-8ddbb9e81 19 Apr 2026 none — — Details →
6.0.14-48f66c41e 18 Apr 2026 none — — Details →

The newest 120 of 918 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/keychain

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/keychain

Is @libp2p/keychain safe to use?

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

Vulert scores @libp2p/keychain 85/100, which reads as healthy. 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/keychain affected?

No. 6.1.10, 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.

How many vulnerabilities does @libp2p/keychain have?

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

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

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