Vulnerability Database · Go · Package report
github.com/libp2p/go-libp2p-record: vulnerability history, versions and safety
github.com/libp2p/go-libp2p-record 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-libp2p-record v0.3.1 i
Updated on 23 Oct 2026
Good news: v0.3.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.3.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.3.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.3.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 26 i
- OpenSSF scorecard 2/10 i
- Last release 20 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-record, 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.2-0.20250821073209-24a25767ab0b 21 Aug 2025
- v0.3.2-0.20250328130701-28b1a791a65d 28 Mar 2025
- v0.3.2-0.20250216200154-2e6e3abbd714 16 Feb 2025
- v0.3.1 23 Jan 2025
- v0.3.0 23 Jan 2025
- v0.2.1-0.20250117075325-f04da8350c6d 17 Jan 2025
- v0.2.1-0.20240826102653-d72bab7b487a 26 Aug 2024
- v0.2.1-0.20240807141552-26aae8fa220d 07 Aug 2024
- v0.2.1-0.20240322071731-f1194b0ee1b2 22 Mar 2024
- v0.2.1-0.20240314112612-ca6a89fe5de4 14 Mar 2024
- v0.2.1-0.20240131164934-37721c9b9f2e 31 Jan 2024
- v0.2.1-0.20230814133630-4bf4f1876a1c 14 Aug 2023
- v0.2.1-0.20230628085308-058bcc7930a1 28 Jun 2023
- v0.2.1-0.20230614090719-6c014b76c83f 14 Jun 2023
- v0.2.1-0.20230208142052-526edc753c1f 08 Feb 2023
- v0.2.1-0.20220919134220-f093f9649af5 19 Sep 2022
- v0.2.1-0.20220823153944-b891c49f36f8 23 Aug 2022
- v0.2.0 19 Aug 2022
- v0.1.4-0.20220819141409-298efb7ab092 19 Aug 2022
- v0.1.4-0.20220404165747-360bbf2eb2f6 04 Apr 2022
- v0.1.4-0.20211210111617-ea09627d61a5 10 Dec 2021
- v0.1.4-0.20210817144457-552f96a2a77a 17 Aug 2021
- v0.1.3 05 May 2020
- v0.1.3-0.20191206213318-3069e484de95 06 Dec 2019
- v0.0.0-20191202173212-8ccbca30634f 02 Dec 2019
- v0.1.2 02 Dec 2019
- v0.0.0-20190802164628-3f535b1abcdf 02 Aug 2019
- v0.1.1 02 Aug 2019
- v0.1.1-0.20190710190207-23af7804929a 10 Jul 2019
- v0.0.0-20190525124109-4837430afd8f 25 May 2019
- v0.1.0 25 May 2019
- v0.0.2-0.20190301164221-774b428e08c6 01 Mar 2019
- v0.0.0-20190301163856-4c2093f40950 01 Mar 2019
- v0.0.1 01 Mar 2019
- v0.0.0-20190226223446-0f29df9dd657 26 Feb 2019
- v0.0.0-20190226222643-0e81f4687089 26 Feb 2019
- v0.0.0-20190218150535-4e8ffc3e2485 18 Feb 2019
- v0.0.0-20181214050013-1deddc4dd2b6 14 Dec 2018
- v0.0.0-20181207225104-d04a504be025 07 Dec 2018
- v0.0.0-20181103041139-237ab9e10af1 03 Nov 2018
- v0.0.0-20181016110443-56beff422ba2 16 Oct 2018
- v0.0.0-20180924121127-7a182bb5ae66 24 Sep 2018
- v0.0.0-20180822000914-07353e628b47 22 Aug 2018
- v0.0.0-20180809015044-a08427cde51d 09 Aug 2018
- v0.0.0-20180808001029-a9be0a2769ae 08 Aug 2018
- v0.0.0-20180626002306-c29879dbb015 26 Jun 2018
- v0.0.0-20180609053111-e1ffee3ceea9 09 Jun 2018
- v0.0.0-20180609032542-11b89d3b90d6 09 Jun 2018
- v0.0.0-20180602072520-c4c6ef6a9327 02 Jun 2018
- v0.0.0-20180531190616-b3dd0d674568 31 May 2018
- v0.0.0-20180503212503-bd38da8f0610 03 May 2018
- v0.0.0-20180427224400-3b0f03e00194 27 Apr 2018
- v0.0.0-20180416045114-a8ce8561390c 16 Apr 2018
- v0.0.0-20180207224850-6774ecef51dd 07 Feb 2018
- v0.0.0-20180201025419-d7c1e5a6ef71 01 Feb 2018
- v0.0.0-20180120045240-91d50dbc4ba0 20 Jan 2018
- v0.0.0-20180120040322-2ca0fda0f58a 20 Jan 2018
- v0.0.0-20171205005414-9d563c74fbb1 05 Dec 2017
- v0.0.0-20171205005348-56ef08160cb6 05 Dec 2017
- v0.0.0-20170711231735-829c054bf734 11 Jul 2017
- v0.0.0-20170325015419-fe371136e75f 25 Mar 2017
- v0.0.0-20170306035214-5a091d904ab6 06 Mar 2017
- v0.0.0-20170203210741-063c957fa614 03 Feb 2017
- v0.0.0-20170203024204-8dba1fda7b75 03 Feb 2017
- v0.0.0-20161005190329-ffbd25bc6115 05 Oct 2016
- v0.0.0-20160930051510-f74cc11be3d3 30 Sep 2016
- v0.0.0-20160903185354-00e731fe982f 03 Sep 2016
- v0.0.0-20160831154311-17f0b3269b43 31 Aug 2016
All 68 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-record
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-libp2p-record
Is github.com/libp2p/go-libp2p-record safe to use?
Vulert has no vulnerabilities on record for github.com/libp2p/go-libp2p-record 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-record's Vulert package health score?
Vulert scores github.com/libp2p/go-libp2p-record 56/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-record affected?
No. v0.3.1, 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-record should I use?
v0.3.1 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-record have?
0 vulnerabilities are recorded for github.com/libp2p/go-libp2p-record 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-record vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/libp2p/go-libp2p-record 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-record 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-record 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-record version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.