Vulnerability Database · Go · Package report
github.com/libp2p/go-buffer-pool: vulnerability history, versions and safety
github.com/libp2p/go-buffer-pool 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-buffer-pool v0.1.0 i
Updated on 23 Oct 2026
Good news: v0.1.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Inactive
What to do: Stay on v0.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.1.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 80 i
- OpenSSF scorecard 2/10 i
- Last release 51 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-buffer-pool, 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.1.1-0.20250821073224-86b7b85b26ae 21 Aug 2025
- v0.1.1-0.20250328130723-b4f394b7039a 28 Mar 2025
- v0.1.1-0.20250216213811-f7426fa63a5e 16 Feb 2025
- v0.1.1-0.20240826151227-4ac51de78564 26 Aug 2024
- v0.1.1-0.20240322071746-07853ef05011 22 Mar 2024
- v0.1.1-0.20240314112627-aa68a9eafe75 14 Mar 2024
- v0.1.1-0.20240131164921-65aa7b7b3301 31 Jan 2024
- v0.1.1-0.20230814133639-caa172843715 14 Aug 2023
- v0.1.1-0.20230814062056-4b382536ca6c 14 Aug 2023
- v0.1.1-0.20230628085448-716b603bbb87 28 Jun 2023
- v0.1.1-0.20230614090445-53d25458c32a 14 Jun 2023
- v0.1.1-0.20230208141636-1e60629cd3e5 08 Feb 2023
- v0.1.1-0.20220919134021-a29bd39bcbb7 19 Sep 2022
- v0.1.1-0.20220827015844-53937159e25b 27 Aug 2022
- v0.0.3-0.20220827015734-d8146c5adfbc 27 Aug 2022
- v0.0.3-0.20220827014906-df02d42781bb 27 Aug 2022
- v0.0.3-0.20220827014828-a908a6734c53 27 Aug 2022
- v0.1.1-0.20220823153723-dbd49f9b4041 23 Aug 2022
- v0.1.0 01 Jul 2022
- v0.0.3-0.20220701184454-38c507e76a53 01 Jul 2022
- v0.0.3-0.20220404115217-e4cd76f95b12 04 Apr 2022
- v0.0.3-0.20220131174246-bfc3315227fa 31 Jan 2022
- v0.0.3-0.20211210150033-f4ac4e4ddc09 10 Dec 2021
- v0.0.3-0.20211017161110-1ac03b603aeb 17 Oct 2021
- v0.0.3-0.20211015115748-ed6a0d2e9bab 15 Oct 2021
- v0.0.3-0.20210601180309-755c6ef29382 01 Jun 2021
- v0.0.3-0.20210510193620-2efc7b61c66d 10 May 2021
- v0.0.3-0.20210510193257-ccf95b0f639f 10 May 2021
- v0.0.3-0.20210510193204-aec628916218 10 May 2021
- v0.0.3-0.20210505124939-1a02bce07f90 05 May 2021
- v0.0.3-0.20210505124653-83441051824d 05 May 2021
- v0.0.0-20191206215133-4016316b51a2 06 Dec 2019
- v0.0.3-0.20191206215133-4016316b51a2 06 Dec 2019
- v0.0.3-0.20191206212854-6744b503d894 06 Dec 2019
- v0.0.0-20190619091711-d94255cb3dfc 19 Jun 2019
- v0.0.3-0.20190619091711-d94255cb3dfc 19 Jun 2019
- v0.0.3-0.20190619091032-fc648bc873eb 19 Jun 2019
- v0.0.0-20190521202419-c4a5988a1e47 21 May 2019
- v0.0.2 21 May 2019
- v0.0.2-0.20190521194931-7b5d8db5ff98 21 May 2019
- v0.0.2-0.20190521194242-0081fc69204b 21 May 2019
- v0.0.2-0.20190411201115-8af23348b9e4 11 Apr 2019
- v0.0.2-0.20190409145810-0418b3494b3d 09 Apr 2019
- v0.0.0-20190227191726-eecb57f6a721 27 Feb 2019
- v0.0.1 27 Feb 2019
- v0.0.0-20190227191355-2610f630f76b 27 Feb 2019
- v0.0.0-20190123225638-a8d831235797 23 Jan 2019
- v0.0.0-20190123210530-d0927c2e6a51 23 Jan 2019
- v0.0.0-20190123210050-74525f76a0fc 23 Jan 2019
- v0.0.0-20181009094743-058210c5a0d0 09 Oct 2018
- v0.0.0-20181006021951-e0f6ad1ea2b7 06 Oct 2018
- v0.0.0-20181006020026-c136f72a011f 06 Oct 2018
- v0.0.0-20181004200957-8adc4b47f0af 04 Oct 2018
- v0.0.0-20181004200821-e8a991d68b4c 04 Oct 2018
- v0.0.0-20181004063537-2ad47e566cea 04 Oct 2018
- v0.0.0-20180121223658-1d28ab5fdb42 21 Jan 2018
- v0.0.0-20180121223646-944ed06fd52c 21 Jan 2018
- v0.0.0-20180121223357-eb6b2a447a7e 21 Jan 2018
- v0.0.0-20180121223343-ac6cb82b065d 21 Jan 2018
- v0.0.0-20180121223330-3759af98c3b3 21 Jan 2018
- v0.0.0-20180121213945-932f0384af57 21 Jan 2018
- v0.0.0-20180121213837-1d08797b6dc2 21 Jan 2018
- v0.0.0-20180121185730-deedd3bb82c7 21 Jan 2018
- v0.0.0-20171220213511-cb18b7949d8e 20 Dec 2017
- v0.0.0-20171220211907-a156257eecd0 20 Dec 2017
- v0.0.0-20171220211550-8967793ec56e 20 Dec 2017
- v0.0.0-20171220211110-3d6ef091b7a0 20 Dec 2017
- v0.0.0-20171220211047-2792e41d553a 20 Dec 2017
- v0.0.0-20141206161609-20e5705ada51 06 Dec 2014
All 69 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-buffer-pool
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-buffer-pool
Is github.com/libp2p/go-buffer-pool safe to use?
Vulert has no vulnerabilities on record for github.com/libp2p/go-buffer-pool 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-buffer-pool's Vulert package health score?
Vulert scores github.com/libp2p/go-buffer-pool 49/100, which reads as risky. 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-buffer-pool affected?
No. v0.1.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-buffer-pool should I use?
v0.1.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-buffer-pool have?
0 vulnerabilities are recorded for github.com/libp2p/go-buffer-pool 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-buffer-pool vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/libp2p/go-buffer-pool 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-buffer-pool 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-buffer-pool for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/libp2p/go-buffer-pool version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.