Vulnerability Database · Go · Package report
github.com/willf/bloom: vulnerability history, versions and safety
github.com/willf/bloom 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/willf/bloom v2.0.3+incompatible i
Updated on 23 Oct 2026
Good news: v2.0.3+incompatible, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Key ecosystem project
- Community Quiet
What to do: Stay on v2.0.3+incompatible or newer. This can change: a vulnerability disclosed tomorrow can affect v2.0.3+incompatible too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v2.0.3+incompatible — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 2,817 i
- OpenSSF scorecard 4/10 i
- Last release 113 months ago i
- Licence BSD-2-Clause 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/willf/bloom, 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.
- v2.0.4-0.20210429144143-153ac1cba827+incompatible 29 Apr 2021
- v2.0.4-0.20210429142745-08eca09dabca+incompatible 29 Apr 2021
- v2.0.4-0.20210425212426-bd521f1dba8b+incompatible 25 Apr 2021
- v2.0.4-0.20210423225224-18dd80c8cdf9+incompatible 23 Apr 2021
- v0.0.0-20190228212355-25ba46ef8744 28 Feb 2019
- v2.0.4-0.20190228212355-25ba46ef8744+incompatible 28 Feb 2019
- v0.0.0-20170505221640-54e3b963ee16 05 May 2017
- v1.0.1-0.20170505221640-54e3b963ee16 05 May 2017
- v2.0.3+incompatible 05 May 2017
- v2.0.2+incompatible 05 May 2017
- v2.0.1+incompatible 01 May 2017
- v2.0.1-0.20170415163450-bda5868a9abd+incompatible 15 Apr 2017
- v0.0.0-20170401144101-c94658585882 01 Apr 2017
- v2.0.1-0.20170401144101-c94658585882+incompatible 01 Apr 2017
- v2.0.1-0.20170301132200-77949819964e+incompatible 01 Mar 2017
- v2.0.1-0.20170228150336-18f5e3ec6361+incompatible 28 Feb 2017
- v0.0.0-20161203020925-278d7d8b1458 03 Dec 2016
- v2.0.1-0.20161203020925-278d7d8b1458+incompatible 03 Dec 2016
- v2.0.1-0.20160916152825-c358096ae522+incompatible 16 Sep 2016
- v2.0.1-0.20160908002526-3cd5893d62cd+incompatible 08 Sep 2016
- v0.0.0-20160824132524-a8bcd3701532 24 Aug 2016
- v2.0.1-0.20160824132524-a8bcd3701532+incompatible 24 Aug 2016
- v2.0.1-0.20160824104315-fd3e6ecce2dc+incompatible 24 Aug 2016
- v0.0.0-20160225145307-aa3071d92035 25 Feb 2016
- v2.0.1-0.20160225145307-aa3071d92035+incompatible 25 Feb 2016
- v2.0.1-0.20160225143649-054c31274a23+incompatible 25 Feb 2016
- v0.0.0-20151124223207-73320a6e73f3 24 Nov 2015
- v2.0.0+incompatible 24 Nov 2015
- v0.0.0-20150330202226-270f902f15ed 30 Mar 2015
- v1.0.1-0.20150330202226-270f902f15ed 30 Mar 2015
- v1.0.1-0.20141124222735-b27214d2ef0a 24 Nov 2014
- v1.0.1-0.20140806224125-52ddb0c223d7 06 Aug 2014
- v1.0.1-0.20140610141443-1f4496ad1f50 10 Jun 2014
- v1.0.1-0.20140610032240-0c69e0b5042f 10 Jun 2014
- v1.0.1-0.20140308233635-c4da872ca584 08 Mar 2014
- v1.0.1-0.20140308041813-c9d271c7c341 08 Mar 2014
- v1.0.0 15 Feb 2014
- v0.0.0-20131024183305-7f16f7da4291 24 Oct 2013
- v0.0.0-20130618045118-22ef191a0574 18 Jun 2013
- v0.0.0-20110523034808-150ec7e37c4e 23 May 2011
All 40 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/willf/bloom
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/willf/bloom
Is github.com/willf/bloom safe to use?
Vulert has no vulnerabilities on record for github.com/willf/bloom 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/willf/bloom's Vulert package health score?
Vulert scores github.com/willf/bloom 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/willf/bloom affected?
No. v2.0.3+incompatible, 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/willf/bloom should I use?
v2.0.3+incompatible 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/willf/bloom have?
0 vulnerabilities are recorded for github.com/willf/bloom 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/willf/bloom vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/willf/bloom 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/willf/bloom 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/willf/bloom for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/willf/bloom version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.