Vulnerability Database · Go · Package report

github.com/kylelemons/godebug: vulnerability history, versions and safety

github.com/kylelemons/godebug 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.

Vulert verdict on github.com/kylelemons/godebug v1.1.0 i

Updated on 23 Oct 2026

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

Package health score 49/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Inactive

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

  • Current release v1.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 356 i
  • OpenSSF scorecard 1/10 i
  • Last release 89 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/kylelemons/godebug, 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.0.0-20201107061927-e693023230a4 07 Nov 2020 none Apache-2.0 — Details →
v1.1.1-0.20201107061927-e693023230a4 07 Nov 2020 none Apache-2.0 — Details →
v1.1.1-0.20201107061214-7a0035301fcf 07 Nov 2020 none Apache-2.0 — Details →
v1.1.1-0.20201107055611-64c05a116967 07 Nov 2020 none Apache-2.0 — Details →
v0.0.0-20190824192725-fa7b53cdfc91 24 Aug 2019 none Apache-2.0 — Details →
v1.1.1-0.20190824192725-fa7b53cdfc91 24 Aug 2019 none Apache-2.0 — Details →
v1.1.1-0.20190824185015-bde9f3c96d7a 24 Aug 2019 none Apache-2.0 — Details →
v1.1.1-0.20190824184510-fbf057ca71bb 24 Aug 2019 none Apache-2.0 — Details →
v1.1.1-0.20190824184423-b2dd1a805a6c 24 Aug 2019 none Apache-2.0 — Details →
v0.0.0-20190629025922-a435ca668a92 29 Jun 2019 none Apache-2.0 — Details →
v1.1.1-0.20190629025922-a435ca668a92 29 Jun 2019 none Apache-2.0 — Details →
v1.0.1-0.20190505012655-e866184aa0f9 05 May 2019 none Apache-2.0 — Details →
v0.0.0-20190505011637-9ff306d4fbea 05 May 2019 none Apache-2.0 — Details →
v1.1.0 05 May 2019 none Apache-2.0 — Details →
v1.0.1-0.20190505011400-7c2843eff2f0 05 May 2019 none Apache-2.0 — Details →
v0.0.0-20190430015139-ce74423a4a27 30 Apr 2019 none Apache-2.0 — Details →
v1.0.0 30 Apr 2019 none Apache-2.0 — Details →
v0.0.0-20171118190045-7a67e28dea99 18 Nov 2017 none Apache-2.0 — Details →
v0.0.0-20170822035801-2c79fab568fc 22 Aug 2017 none Apache-2.0 — Details →
v0.0.0-20170822033709-ecf6d57b7139 22 Aug 2017 none Apache-2.0 — Details →
v0.0.0-20170820005314-ba6def33137f 20 Aug 2017 none Apache-2.0 — Details →
v0.0.0-20170820004410-5301bd2ee6e8 20 Aug 2017 none Apache-2.0 — Details →
v0.0.0-20170820004349-d65d576e9348 20 Aug 2017 none Apache-2.0 — Details →
v0.0.0-20170224010052-a616ab194758 24 Feb 2017 none Apache-2.0 — Details →
v0.0.0-20170223165533-4106ce705375 23 Feb 2017 none Apache-2.0 — Details →
v0.0.0-20170222213550-95b382491af5 22 Feb 2017 none Apache-2.0 — Details →
v0.0.0-20161109210102-d99083b96f42 09 Nov 2016 none Apache-2.0 — Details →
v0.0.0-20161109185432-d31080de9365 09 Nov 2016 none Apache-2.0 — Details →
v0.0.0-20161108211809-397d9a06b644 08 Nov 2016 none Apache-2.0 — Details →
v0.0.0-20160406211939-eadb3ce320cb 06 Apr 2016 none Apache-2.0 — Details →
v0.0.0-20160406211919-68d2bbec656a 06 Apr 2016 none Apache-2.0 — Details →
v0.0.0-20160405003045-fffda665884a 05 Apr 2016 none Apache-2.0 — Details →
v0.0.0-20160402192154-328c2a297d0d 02 Apr 2016 none Apache-2.0 — Details →
v0.0.0-20160330070904-135288e33abe 30 Mar 2016 none Apache-2.0 — Details →
v0.0.0-20160322231641-165b433c1d1c 22 Mar 2016 none Apache-2.0 — Details →
v0.0.0-20150519154555-21cb3784d9bd 19 May 2015 none Apache-2.0 — Details →
v0.0.0-20150517183047-6f3948b42335 17 May 2015 none Apache-2.0 — Details →
v0.0.0-20150515194752-c13a706a38b2 15 May 2015 none Apache-2.0 — Details →
v0.0.0-20150416052901-509abe0bbf74 16 Apr 2015 none Apache-2.0 — Details →
v0.0.0-20131002215753-808ac284003c 02 Oct 2013 none Apache-2.0 — Details →
v0.0.0-20130406053043-0f00afa0734e 06 Apr 2013 none Apache-2.0 — Details →
v0.0.0-20130111024722-21e37b6e1065 11 Jan 2013 none Apache-2.0 — Details →
v0.0.0-20130106105120-0ce6b6c8dcf2 06 Jan 2013 none — — Details →

All 43 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/kylelemons/godebug

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/kylelemons/godebug

Is github.com/kylelemons/godebug safe to use?

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

Vulert scores github.com/kylelemons/godebug 49/100, which reads as risky. 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/kylelemons/godebug affected?

No. v1.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/kylelemons/godebug should I use?

v1.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/kylelemons/godebug have?

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

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

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