Vulnerability Database · Go · Package report
github.com/libp2p/go-msgio: vulnerability history, versions and safety
github.com/libp2p/go-msgio is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/libp2p/go-msgio v0.3.0 i
Updated on 23 Oct 2026
Good news: v0.3.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.3.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 17 i
- OpenSSF scorecard 2/10 i
- Last release 45 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-msgio, 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.
- v0.3.1-0.20250821073204-68fcc077f405 21 Aug 2025
- v0.3.1-0.20250328130655-c3667926f2f8 28 Mar 2025
- v0.3.1-0.20250216200150-fe5f662546b3 16 Feb 2025
- v0.3.1-0.20240826102648-0967bbfcb386 26 Aug 2024
- v0.3.1-0.20240322071724-b71d621da592 22 Mar 2024
- v0.3.1-0.20240314112604-7b047a648b32 14 Mar 2024
- v0.3.1-0.20240131164855-0a9352ed8abc 31 Jan 2024
- v0.3.1-0.20230815100355-072cb0a80885 15 Aug 2023
- v0.3.1-0.20230814111334-216b33a8570f 14 Aug 2023
- v0.3.1-0.20230814084341-4df5189042a1 14 Aug 2023
- v0.3.1-0.20230813200017-45619a09ee1e 13 Aug 2023
- v0.3.1-0.20230628085251-8b3c812ee710 28 Jun 2023
- v0.3.1-0.20230614090553-0d95cf067120 14 Jun 2023
- v0.3.1-0.20230320093732-5c9463d6b985 20 Mar 2023
- v0.3.1-0.20230320093731-afb286e9023d 20 Mar 2023
- v0.3.1-0.20230320093716-2507a6be8316 20 Mar 2023
- v0.3.0 12 Jan 2023
- v0.2.1-0.20230108031931-b267c299b17c 08 Jan 2023
- v0.2.1-0.20230104010010-ff89d1813d27 04 Jan 2023
- v0.2.1-0.20220919134135-3215d35a6f36 19 Sep 2022
- v0.2.1-0.20220825125214-6c6045e2e01b 25 Aug 2022
- v0.2.0 19 Apr 2022
- v0.1.1-0.20220414122945-05788ec48f26 14 Apr 2022
- v0.1.1-0.20211210154832-55d52b474708 10 Dec 2021
- v0.0.7-0.20210817144525-3f720fda4b19 17 Aug 2021
- v0.1.0 17 Aug 2021
- v0.0.7-0.20210805065737-7c1a84b08e5d 05 Aug 2021
- v0.0.6 29 Jul 2020
- v0.0.5 29 Jul 2020
- v0.0.0-20190614160210-9142103f7d8d 14 Jun 2019
- v0.0.4 14 Jun 2019
- v0.0.3 06 Jun 2019
- v0.0.2 20 Apr 2019
- v0.0.0-20190227192206-2efd92d62d52 27 Feb 2019
- v0.0.1 27 Feb 2019
- v0.0.0-20190117001650-f8aaa1f70c8b 17 Jan 2019
- v0.0.0-20181010102932-031a413e6612 10 Oct 2018
- v0.0.0-20181005212410-a0cff72a54a0 05 Oct 2018
- v0.0.0-20181005205654-20c28f2765fd 05 Oct 2018
- v0.0.0-20180926174932-5b7d4ee2db24 26 Sep 2018
- v0.0.0-20180925225153-58542711d699 25 Sep 2018
- v0.0.0-20171219234116-3e3c5a71daa4 19 Dec 2017
- v0.0.0-20171211220509-d82125c9907e 11 Dec 2017
- v0.0.0-20171211203907-373c219f77da 11 Dec 2017
- v0.0.0-20171205003422-709299bfffa0 05 Dec 2017
- v0.0.0-20171125145254-063ce36bcec3 25 Nov 2017
- v0.0.0-20171119235546-fa984f54d57f 19 Nov 2017
- v0.0.0-20171117211358-44064e9f8c1b 17 Nov 2017
- v0.0.0-20171117211237-0ca011676ba3 17 Nov 2017
- v0.0.0-20171117204539-519416593883 17 Nov 2017
- v0.0.0-20171117193852-9c38e18f6652 17 Nov 2017
- v0.0.0-20160322123021-242a3f4ed2d0 22 Mar 2016
All 52 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-msgio
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
Questions
About github.com/libp2p/go-msgio
Is github.com/libp2p/go-msgio safe to use?
Vulert has no vulnerabilities on record for github.com/libp2p/go-msgio 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-msgio's Vulert package health score?
Vulert scores github.com/libp2p/go-msgio 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-msgio affected?
No. v0.3.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-msgio should I use?
v0.3.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-msgio have?
0 vulnerabilities are recorded for github.com/libp2p/go-msgio 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-msgio vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/libp2p/go-msgio 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-msgio 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-msgio for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/libp2p/go-msgio version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.