VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/MicahParks/keyfunc: vulnerability history, versions and safety

github.com/MicahParks/keyfunc 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/MicahParks/keyfunc vulnerabilities

Vulert verdict on github.com/MicahParks/keyfunc v1.9.0 i

Updated on 23 Oct 2026

Good news: v1.9.0, the version you would install today, has no known vulnerabilities.

Package health score 55/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Inactive

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

  • Current release v1.9.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 416 i
  • OpenSSF scorecard 1/10 i
  • Last release 46 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/MicahParks/keyfunc, 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
v1.9.1-0.20230418024043-cd77b4a7eb6d 18 Apr 2023 none Apache-2.0 — Details →
v1.9.1-0.20230404121550-e2a23c9635a1 04 Apr 2023 none Apache-2.0 — Details →
v1.9.1-0.20230404120905-9a70007d2553 04 Apr 2023 none Apache-2.0 — Details →
v1.9.1-0.20230221135042-ee962a7cee1f 21 Feb 2023 none Apache-2.0 — Details →
v1.9.1-0.20230221103433-ed990edf4d3a 21 Feb 2023 none Apache-2.0 — Details →
v1.9.1-0.20221231150437-b797ba9139a2 31 Dec 2022 none Apache-2.0 — Details →
v1.9.1-0.20221231150420-e4457a063424 31 Dec 2022 none Apache-2.0 — Details →
v1.9.0 23 Dec 2022 none Apache-2.0 — Details →
v1.8.1-0.20221220133151-9ce014ef3987 20 Dec 2022 none Apache-2.0 — Details →
v1.8.0 20 Dec 2022 none Apache-2.0 — Details →
v1.7.0 30 Nov 2022 none Apache-2.0 — Details →
v1.6.0 26 Nov 2022 none Apache-2.0 — Details →
v1.5.3 03 Nov 2022 none Apache-2.0 — Details →
v1.5.2 01 Nov 2022 none Apache-2.0 — Details →
v1.5.1 15 Oct 2022 none Apache-2.0 — Details →
v1.5.0 15 Oct 2022 none Apache-2.0 — Details →
v1.4.1-0.20221014221409-40fb1f99bab0 14 Oct 2022 none Apache-2.0 — Details →
v1.4.0 27 Sep 2022 none Apache-2.0 — Details →
v1.3.0 26 Sep 2022 none Apache-2.0 — Details →
v1.2.3-0.20220812160732-7892f0927289 12 Aug 2022 none Apache-2.0 — Details →
v1.2.2 12 Aug 2022 none Apache-2.0 — Details →
v1.2.1 11 Aug 2022 none Apache-2.0 — Details →
v1.2.1-0.20220720145103-48a54b080001 20 Jul 2022 none Apache-2.0 — Details →
v1.2.0 20 Jul 2022 none Apache-2.0 — Details →
v1.1.0 14 Apr 2022 none Apache-2.0 — Details →
v1.0.3 06 Apr 2022 none Apache-2.0 — Details →
v1.0.2 06 Apr 2022 none Apache-2.0 — Details →
v1.0.1 06 Dec 2021 none Apache-2.0 — Details →
v1.0.0 06 Dec 2021 none Apache-2.0 — Details →
v0.10.1-0.20211203185044-1ed9d36ab59c 03 Dec 2021 none Apache-2.0 — Details →
v0.10.1-0.20211118132429-f3d199950457 18 Nov 2021 none Apache-2.0 — Details →
v0.10.1-0.20211118122810-798c40e0dd75 18 Nov 2021 none Apache-2.0 — Details →
v0.10.0 13 Nov 2021 none Apache-2.0 — Details →
v0.9.0 08 Oct 2021 none Apache-2.0 — Details →
v0.8.3 30 Sep 2021 none Apache-2.0 — Details →
v0.8.2 17 Sep 2021 none Apache-2.0 — Details →
v0.8.2-0.20210917145021-69b7a6c25e14 17 Sep 2021 none Apache-2.0 — Details →
v0.8.1 17 Sep 2021 none Apache-2.0 — Details →
v0.8.0 14 Sep 2021 none Apache-2.0 — Details →
v0.7.0 18 Aug 2021 none Apache-2.0 — Details →
v0.6.2-0.20210802170917-857c11792e94 02 Aug 2021 none Apache-2.0 — Details →
v0.6.1 02 Aug 2021 none Apache-2.0 — Details →
v0.6.0 30 Jun 2021 none Apache-2.0 — Details →
v0.5.0 27 Jun 2021 none Apache-2.0 — Details →
v0.4.2 03 Jun 2021 none Apache-2.0 — Details →
v0.4.1 27 May 2021 none Apache-2.0 — Details →
v0.4.0 21 Apr 2021 none Apache-2.0 — Details →
v0.3.3 30 Mar 2021 none Apache-2.0 — Details →
v0.3.2 28 Mar 2021 none Apache-2.0 — Details →
v0.3.1 22 Mar 2021 none Apache-2.0 — Details →
v0.3.0 18 Mar 2021 none Apache-2.0 — Details →
v0.2.1 11 Mar 2021 none Apache-2.0 — Details →
v0.2.0 10 Mar 2021 none Apache-2.0 — Details →
v0.1.2 10 Mar 2021 none Apache-2.0 — Details →
v0.1.1 10 Mar 2021 none Apache-2.0 — Details →
v0.1.0 10 Mar 2021 none Apache-2.0 — Details →

All 56 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/MicahParks/keyfunc

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/MicahParks/keyfunc

Is github.com/MicahParks/keyfunc safe to use?

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

Vulert scores github.com/MicahParks/keyfunc 55/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/MicahParks/keyfunc affected?

No. v1.9.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/MicahParks/keyfunc should I use?

v1.9.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/MicahParks/keyfunc have?

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

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

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