VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/blevesearch/geo: vulnerability history, versions and safety

github.com/blevesearch/geo is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/blevesearch/geo vulnerabilities

Vulert verdict on github.com/blevesearch/geo v0.2.6 i

Updated on 23 Oct 2026

Good news: v0.2.6, the version you would install today, has no known vulnerabilities.

Package health score 67/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

What to do: Stay on v0.2.6 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.2.6 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v0.2.6 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2 i
  • OpenSSF scorecard 3/10 i
  • Last release 2 months ago i
  • Licence Apache-2.0 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/blevesearch/geo, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.2.7-0.20260831141219-9c3e3a4d84bc 31 Aug 2026 none Apache-2.0 — Details →
v0.0.0-20260805065110-a696685e93c5 05 Aug 2026 none Apache-2.0 — Details →
v0.2.6 05 Aug 2026 none Apache-2.0 — Details →
v0.2.6-0.20260805065110-a696685e93c5 05 Aug 2026 none Apache-2.0 — Details →
v0.2.5 20 Feb 2026 none Apache-2.0 — Details →
v0.2.4 07 Aug 2025 none Apache-2.0 — Details →
v0.2.3 15 May 2025 none Apache-2.0 — Details →
v0.2.2 12 May 2025 none Apache-2.0 — Details →
v0.2.1 08 May 2025 none Apache-2.0 — Details →
v0.2.1-0.20250507051613-96ba0b9516a2 07 May 2025 none Apache-2.0 — Details →
v0.2.1-0.20250506080145-49aee829e3be 06 May 2025 none Apache-2.0 — Details →
v0.2.0 17 Apr 2025 none Apache-2.0 — Details →
v0.1.20 02 Feb 2024 none Apache-2.0 — Details →
v0.1.19 16 Jan 2024 none Apache-2.0 — Details →
v0.1.18 30 Aug 2023 none Apache-2.0 — Details →
v0.1.17 19 Dec 2022 none Apache-2.0 — Details →
v0.1.16 18 Nov 2022 none Apache-2.0 — Details →
v0.1.15 28 Sep 2022 none Apache-2.0 — Details →
v0.1.15-0.20220928045608-a8f45565d798 28 Sep 2022 none Apache-2.0 — Details →
v0.1.14 06 Aug 2022 none Apache-2.0 — Details →
v0.1.14-0.20220806033936-256c7049d467 06 Aug 2022 none Apache-2.0 — Details →
v0.1.14-0.20220805085234-1bc1d50c7220 05 Aug 2022 none Apache-2.0 — Details →
v0.1.13 22 Jul 2022 none Apache-2.0 — Details →
v0.1.12 06 Jun 2022 none Apache-2.0 — Details →
v0.1.12-0.20220606102651-aab42add3121 06 Jun 2022 none Apache-2.0 — Details →
v0.1.12-0.20220531073316-e435177b73a3 31 May 2022 none Apache-2.0 — Details →
v0.1.12-0.20220530122157-1e74e8de7c9d 30 May 2022 none Apache-2.0 — Details →
v0.1.12-0.20220525024427-4ff549e2782c 25 May 2022 none Apache-2.0 — Details →
v0.1.11 23 May 2022 none Apache-2.0 — Details →
v0.1.10 20 Apr 2022 none Apache-2.0 — Details →
v0.1.9 22 Mar 2022 none Apache-2.0 — Details →

All 31 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/blevesearch/geo

No vulnerability write-ups match this view

Search all 0 in the database →

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/blevesearch/geo

Is github.com/blevesearch/geo safe to use?

Vulert has no vulnerabilities on record for github.com/blevesearch/geo 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/blevesearch/geo's Vulert package health score?

Vulert scores github.com/blevesearch/geo 67/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/blevesearch/geo affected?

No. v0.2.6, 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/blevesearch/geo should I use?

v0.2.6 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/blevesearch/geo have?

0 vulnerabilities are recorded for github.com/blevesearch/geo 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/blevesearch/geo vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/blevesearch/geo 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/blevesearch/geo 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/blevesearch/geo for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/blevesearch/geo version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.