VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/libp2p/go-libp2p-gostream: vulnerability history, versions and safety

github.com/libp2p/go-libp2p-gostream is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go 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 github.com/libp2p/go-libp2p-gostream vulnerabilities

Vulert verdict on github.com/libp2p/go-libp2p-gostream v0.6.0 i

Updated on 23 Oct 2026

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

Package health score 50/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.6.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 25 i
  • OpenSSF scorecard 2/10 i
  • Last release 43 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, 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 github.com/libp2p/go-libp2p-gostream, 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
v0.6.1-0.20250821073415-9d18149e14c5 21 Aug 2025 none MIT — Details →
v0.6.1-0.20250328130842-b3550cfe9929 28 Mar 2025 none MIT — Details →
v0.6.1-0.20250216200232-5bb85dbb8c5d 16 Feb 2025 none MIT — Details →
v0.6.1-0.20240826104634-6468a40ee0cc 26 Aug 2024 none MIT — Details →
v0.6.1-0.20240321170322-421d3db9614c 21 Mar 2024 none MIT — Details →
v0.6.1-0.20240314113111-10c5500e2883 14 Mar 2024 none MIT — Details →
v0.6.1-0.20240131165157-498fdfa55085 31 Jan 2024 none MIT — Details →
v0.0.0-20230821135107-741e647e6bef 21 Aug 2023 none MIT — Details →
v0.6.1-0.20230821135107-741e647e6bef 21 Aug 2023 none MIT — Details →
v0.6.1-0.20230814075203-9e42aaff6498 14 Aug 2023 none MIT — Details →
v0.6.1-0.20230628085411-45d4a2195abe 28 Jun 2023 none MIT — Details →
v0.6.1-0.20230614090638-961355b74189 14 Jun 2023 none MIT — Details →
v0.6.0 26 Feb 2023 none MIT — Details →
v0.5.1-0.20220922152527-01890e03d7d7 22 Sep 2022 none MIT — Details →
v0.5.0 02 Sep 2022 none MIT — Details →
v0.4.1-0.20220720161416-e1952aede109 20 Jul 2022 none MIT — Details →
v0.4.0 20 Jun 2022 none MIT — Details →
v0.3.2-0.20220309102559-3d4abe2a19ac 09 Mar 2022 none MIT — Details →
v0.3.2-0.20220309101727-f619079d868d 09 Mar 2022 none MIT — Details →
v0.3.2-0.20211210151859-16a4ebf2f4e3 10 Dec 2021 none MIT — Details →
v0.3.2-0.20211029090910-262050e5a9e9 29 Oct 2021 none MIT — Details →
v0.3.2-0.20211022202008-a2cf14e0601d 22 Oct 2021 none MIT — Details →
v0.3.2-0.20210817150354-191ec5d0bcfa 17 Aug 2021 none MIT — Details →
v0.3.2-0.20210519184429-ea39a6955c53 19 May 2021 none MIT — Details →
v0.3.1 13 Jan 2021 none MIT — Details →
v0.2.3-0.20201112052009-9c9ec16cbb44 12 Nov 2020 none MIT — Details →
v0.3.0 12 Nov 2020 none MIT — Details →
v0.2.2-0.20201102200208-3d76385dcb57 02 Nov 2020 none MIT — Details →
v0.2.2 20 Oct 2020 none MIT — Details →
v0.2.1 13 Mar 2020 none MIT — Details →
v0.2.0 27 Sep 2019 none MIT — Details →
v0.1.2 04 Jul 2019 none MIT — Details →
v0.1.1 06 Jun 2019 none MIT — Details →
v0.0.0-20190227195646-68f5153d3e40 27 Feb 2019 none MIT — Details →
v0.0.0-20181025100514-1993926542aa 25 Oct 2018 none MIT — Details →
v0.0.0-20180628091130-9f078322a4bf 28 Jun 2018 none MIT — Details →
v0.0.0-20171023112515-c75991eb05a4 23 Oct 2017 none MIT — Details →

All 37 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 github.com/libp2p/go-libp2p-gostream

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 github.com/libp2p/go-libp2p-gostream

Is github.com/libp2p/go-libp2p-gostream safe to use?

Vulert has no vulnerabilities on record for github.com/libp2p/go-libp2p-gostream in Go 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 github.com/libp2p/go-libp2p-gostream's Vulert package health score?

Vulert scores github.com/libp2p/go-libp2p-gostream 50/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 github.com/libp2p/go-libp2p-gostream affected?

No. v0.6.0, 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 github.com/libp2p/go-libp2p-gostream should I use?

v0.6.0 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 github.com/libp2p/go-libp2p-gostream have?

0 vulnerabilities are recorded for github.com/libp2p/go-libp2p-gostream in the Go 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 github.com/libp2p/go-libp2p-gostream vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/libp2p/go-libp2p-gostream 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 github.com/libp2p/go-libp2p-gostream 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 github.com/libp2p/go-libp2p-gostream for upcoming vulnerabilities?

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