Vulnerability Database · Go · Package report
github.com/sahilm/fuzzy: vulnerability history, versions and safety
github.com/sahilm/fuzzy 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/sahilm/fuzzy v0.1.3 i
Updated on 23 Oct 2026
Good news: v0.1.3, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Widely used
- Community Quiet
What to do: Stay on v0.1.3 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.1.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.1.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 1,450 i
- OpenSSF scorecard 3/10 i
- Last release 4 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/sahilm/fuzzy, 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.4-0.20260624085617-89d593d2aa05 24 Jun 2026
- v0.1.3 11 Jun 2026
- v0.1.2 07 May 2026
- v0.0.0-20250802025426-5ed613fa112b 02 Aug 2025
- v0.1.2-0.20250802025426-5ed613fa112b 02 Aug 2025
- v0.0.0-20230530133925-c48e322e2a8f 30 May 2023
- v0.1.1 30 May 2023
- v0.1.1-0.20230530133925-c48e322e2a8f 30 May 2023
- v0.1.1-0.20201026230834-c72cd382d3e5 26 Oct 2020
- v0.0.0-20191030223719-d88f8cb825dd 30 Oct 2019
- v0.1.1-0.20191030223719-d88f8cb825dd 30 Oct 2019
- v0.0.0-20181210094637-eaa29a3062e4 10 Dec 2018
- v0.1.1-0.20181210094637-eaa29a3062e4 10 Dec 2018
- v0.1.1-0.20181014085254-485b11793d7e 14 Oct 2018
- v0.1.0 01 Sep 2018
- v0.0.5 09 May 2018
- v0.0.4 30 Apr 2018
- v0.0.3 25 Oct 2017
- v0.0.2 23 Oct 2017
- v0.0.1 22 Oct 2017
All 20 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/sahilm/fuzzy
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/sahilm/fuzzy
Is github.com/sahilm/fuzzy safe to use?
Vulert has no vulnerabilities on record for github.com/sahilm/fuzzy 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/sahilm/fuzzy's Vulert package health score?
Vulert scores github.com/sahilm/fuzzy 75/100, which reads as in good shape. 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/sahilm/fuzzy affected?
No. v0.1.3, 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/sahilm/fuzzy should I use?
v0.1.3 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/sahilm/fuzzy have?
0 vulnerabilities are recorded for github.com/sahilm/fuzzy 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/sahilm/fuzzy vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/sahilm/fuzzy 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/sahilm/fuzzy 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/sahilm/fuzzy for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/sahilm/fuzzy version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.