Vulnerability Database · Go · Package report

github.com/kr/pretty: vulnerability history, versions and safety

github.com/kr/pretty 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/kr/pretty v0.3.1 i

Updated on 23 Oct 2026

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

Package health score 57/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Widely used
  • Community Quiet

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

  • Current release v0.3.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,409 i
  • OpenSSF scorecard 2/10 i
  • Last release 49 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/kr/pretty, 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.3.2-0.20230403065708-c84e586bbff0 03 Apr 2023 none MIT — Details →
v0.3.2-0.20230320065729-04e237e0b545 20 Mar 2023 none MIT — Details →
v0.0.0-20220829230305-3cd153a126da 29 Aug 2022 none MIT — Details →
v0.3.1 29 Aug 2022 none MIT — Details →
v0.3.1-0.20220829230305-3cd153a126da 29 Aug 2022 none MIT — Details →
v0.3.1-0.20220825051634-d8c7eb13a5c4 25 Aug 2022 none MIT — Details →
v0.0.0-20220308010035-d928460c8d68 08 Mar 2022 none MIT — Details →
v0.3.1-0.20220308010035-d928460c8d68 08 Mar 2022 none MIT — Details →
v0.0.0-20210805001301-0c671bcf5d4d 05 Aug 2021 none MIT — Details →
v0.3.1-0.20210805001301-0c671bcf5d4d 05 Aug 2021 none MIT — Details →
v0.0.0-20201124222238-a883a8422cd2 24 Nov 2020 none MIT — Details →
v0.2.2-0.20201124222238-a883a8422cd2 24 Nov 2020 none MIT — Details →
v0.3.0 24 Nov 2020 none MIT — Details →
v0.2.2-0.20200831113834-59b4212b823b 31 Aug 2020 none MIT — Details →
v0.2.2-0.20200821033810-3630c7d4e5f8 21 Aug 2020 none MIT — Details →
v0.0.0-20200810074440-814ac30b4b18 10 Aug 2020 none MIT — Details →
v0.2.1-0.20200810074440-814ac30b4b18 10 Aug 2020 none MIT — Details →
v0.2.2-0.20200810074440-814ac30b4b18 10 Aug 2020 none MIT — Details →
v0.2.2-0.20200810074338-44035784bff0 10 Aug 2020 none MIT — Details →
v0.0.0-20200729040243-ead452280cd0 29 Jul 2020 none MIT — Details →
v0.2.1 29 Jul 2020 none MIT — Details →
v0.0.0-20191231234008-4e0886370c3a 31 Dec 2019 none MIT — Details →
v0.2.0 31 Dec 2019 none MIT — Details →
v0.0.0-20190720101428-71e7e4993750 20 Jul 2019 none MIT — Details →
v0.1.1-0.20190720101428-71e7e4993750 20 Jul 2019 none MIT — Details →
v0.0.0-20190507004717-a0c635c0aede 07 May 2019 none MIT — Details →
v0.1.1-0.20190507004717-a0c635c0aede 07 May 2019 none MIT — Details →
v0.0.0-20180506083345-73f6ac0b30a9 06 May 2018 none MIT — Details →
v0.1.0 06 May 2018 none MIT — Details →
v0.0.0-20160823170715-cfb55aafdaf3 23 Aug 2016 none MIT — Details →
v0.0.0-20160708215748-737b74a46c4b 08 Jul 2016 none MIT — Details →
v0.0.0-20160707214721-7497514e3754 07 Jul 2016 none MIT — Details →
v0.0.0-20160707213922-5da52abd6af8 07 Jul 2016 none MIT — Details →
v0.0.0-20160325215624-add1dbc86daf 25 Mar 2016 none MIT — Details →
v0.0.0-20150520163514-e6ac2fc51e89 20 May 2015 none MIT — Details →
v0.0.0-20150119221228-cb0850c1681c 19 Jan 2015 none MIT — Details →
v0.0.0-20140812000539-f31442d60e51 12 Aug 2014 none MIT — Details →
v0.0.0-20140807174246-4d1dc9b4e969 07 Aug 2014 none MIT — Details →
v0.0.0-20140807173932-01bc0efed7b7 07 Aug 2014 none MIT — Details →
v0.0.0-20140804231824-5feda8d40680 04 Aug 2014 none MIT — Details →
v0.0.0-20140723054909-088c856450c0 23 Jul 2014 none MIT — Details →
v0.0.0-20140722061047-18947b1381c4 22 Jul 2014 none MIT — Details →
v0.0.0-20130510082846-bc9499caa0f4 10 May 2013 none MIT — Details →
v0.0.0-20130508051439-3e586b5b617b 08 May 2013 none MIT — Details →
v0.0.0-20130507033344-08e859034c9c 07 May 2013 none MIT — Details →
v0.0.0-20130503055225-2c2f68c2ef98 03 May 2013 none MIT — Details →
v0.0.0-20130119010507-195524255c32 19 Jan 2013 none MIT — Details →
v0.0.0-20121222053239-46b3e070c3d7 22 Dec 2012 none — — Details →
v0.0.0-20120306234858-821b30f52f1a 06 Mar 2012 none — — Details →
v0.0.0-20120225203542-4c5f1d70177a 25 Feb 2012 none — — Details →
v0.0.0-20120225113928-d7035ee8f79a 25 Feb 2012 none — — Details →
v0.0.0-20111227191817-e201f8673108 27 Dec 2011 none — — Details →
v0.0.0-20111118002049-9c87471b7848 18 Nov 2011 none — — Details →
v0.0.0-20110611233740-a6f3cf47d962 11 Jun 2011 none — — Details →
v0.0.0-20110504215442-2795cc3249e4 04 May 2011 none — — Details →
v0.0.0-20110419012625-d599dd2ad1fc 19 Apr 2011 none — — Details →
v0.0.0-20110415113513-e86b82e37c57 15 Apr 2011 none — — Details →
v0.0.0-20110114022519-131db13b2ac8 14 Jan 2011 none — — Details →

All 58 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/kr/pretty

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/kr/pretty

Is github.com/kr/pretty safe to use?

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

Vulert scores github.com/kr/pretty 57/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/kr/pretty affected?

No. v0.3.1, 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/kr/pretty should I use?

v0.3.1 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/kr/pretty have?

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

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

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