Vulnerability Database · Go · Package report
github.com/ipfs/bbloom: vulnerability history, versions and safety
github.com/ipfs/bbloom 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/ipfs/bbloom 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 Sustainable
- Popularity Little adoption
- 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 14 i
- OpenSSF scorecard 3/10 i
- Last release 6 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/ipfs/bbloom, 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.0 08 Apr 2026
- v0.0.5-0.20260313134946-e882fc33651e 13 Mar 2026
- v0.0.5-0.20250821073316-fb354d51442d 21 Aug 2025
- v0.0.5-0.20250328130909-322e5e98be26 28 Mar 2025
- v0.0.5-0.20250216200312-8432bde8ef90 16 Feb 2025
- v0.0.5-0.20240826102745-57a3ee5a72f7 26 Aug 2024
- v0.0.5-0.20240322071854-73e3f896a4f8 22 Mar 2024
- v0.0.5-0.20240314112727-5a28180bef7f 14 Mar 2024
- v0.0.5-0.20240131173549-6d96f4ccc950 31 Jan 2024
- v0.0.5-0.20230815121029-2f1c4398b8db 15 Aug 2023
- v0.0.5-0.20230814084742-1c3f3a3605fb 14 Aug 2023
- v0.0.5-0.20230628085010-fbfe8e0d5807 28 Jun 2023
- v0.0.5-0.20230614111252-6aeee3bea46f 14 Jun 2023
- v0.0.5-0.20221216083106-ecf4b65cf4b9 16 Dec 2022
- v0.0.5-0.20220823155851-350c512bc50d 23 Aug 2022
- v0.0.5-0.20220404114216-d1effa2fdd1d 04 Apr 2022
- v0.0.5-0.20211210152206-858ed330e8cc 10 Dec 2021
- v0.0.5-0.20210817134734-2e7198fb2a9e 17 Aug 2021
- v0.0.5-0.20210802160323-9387056aab7a 02 Aug 2021
- v0.0.5-0.20210802155916-7151476119e3 02 Aug 2021
- v0.0.5-0.20200504101439-7ca16de14615 04 May 2020
- v0.0.5-0.20200407123011-93e865ee8e61 07 Apr 2020
- v0.0.4 23 Aug 2019
- v0.0.4-0.20190823182117-84e8303a9bfb 23 Aug 2019
- v0.0.4-0.20190823172629-221c7e02565a 23 Aug 2019
- v0.0.2 23 Aug 2019
- v0.0.3 23 Aug 2019
- v0.0.1 01 Mar 2019
- v0.0.0-20180721065414-f6503c07a6c2 21 Jul 2018
- v0.0.0-20170711135841-6c7292d0e005 11 Jul 2017
- v0.0.0-20170710125407-0bd8cd2981c0 10 Jul 2017
- v0.0.0-20170709212855-7dffc1f87069 09 Jul 2017
- v0.0.0-20170709212458-4595e998bccb 09 Jul 2017
- v0.0.0-20160906071415-0f5286d21db6 06 Sep 2016
- v0.0.0-20160906070959-f1f60dc31539 06 Sep 2016
- v0.0.0-20160622192047-b8906599d4b9 22 Jun 2016
- v0.0.0-20160622191841-6ce406bc108e 22 Jun 2016
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/ipfs/bbloom
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/ipfs/bbloom
Is github.com/ipfs/bbloom safe to use?
Vulert has no vulnerabilities on record for github.com/ipfs/bbloom 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/ipfs/bbloom's Vulert package health score?
Vulert scores github.com/ipfs/bbloom 63/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/ipfs/bbloom 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/ipfs/bbloom 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/ipfs/bbloom have?
0 vulnerabilities are recorded for github.com/ipfs/bbloom 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/ipfs/bbloom vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/ipfs/bbloom 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/ipfs/bbloom 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/ipfs/bbloom for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/ipfs/bbloom version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.