Vulnerability Database · Go · Package report

github.com/jedib0t/go-pretty: vulnerability history, versions and safety

github.com/jedib0t/go-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/jedib0t/go-pretty v4.3.0+incompatible i

Updated on 23 Oct 2026

Good news: v4.3.0+incompatible, the version you would install today, has no known vulnerabilities.

Package health score 63/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release v4.3.0+incompatible — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 3,556 i
  • OpenSSF scorecard 4/10 i
  • Last release 86 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/jedib0t/go-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
v1.0.1-0.20200515174455-246ce90b3598 15 May 2020 none MIT — Details →
v0.0.0-20200513164024-8b58fbaf3b31 13 May 2020 none MIT — Details →
v1.0.1-0.20200513164024-8b58fbaf3b31 13 May 2020 none MIT — Details →
v1.0.1-0.20200513162803-d24d83bda5d4 13 May 2020 none MIT — Details →
v1.0.1-0.20200511041901-65260f6f71c3 11 May 2020 none MIT — Details →
v0.0.0-20200510190426-e6e6696030be 10 May 2020 none MIT — Details →
v0.0.0-20200508164659-fe76e12ce96b 08 May 2020 none MIT — Details →
v0.0.0-20200508155649-9e7d9eefdcc1 08 May 2020 none MIT — Details →
v0.0.0-20200508053615-c97d2bfdeefd 08 May 2020 none MIT — Details →
v0.0.0-20200507232608-42da823abb45 07 May 2020 none MIT — Details →
v1.0.1-0.20200301171410-ddd7635b5f87 01 Mar 2020 none MIT — Details →
v1.0.1-0.20191104025401-85fe5d6a7c4d 04 Nov 2019 none MIT — Details →
v4.3.1-0.20191104025401-85fe5d6a7c4d+incompatible 04 Nov 2019 none MIT — Details →
v0.0.0-20190726235044-1ec860a8cda3 26 Jul 2019 none MIT — Details →
v4.3.0+incompatible 26 Jul 2019 none MIT — Details →
v0.0.0-20190610054959-b5d36c1d5faf 10 Jun 2019 none MIT — Details →
v4.2.1+incompatible 10 Jun 2019 none MIT — Details →
v4.2.0+incompatible 30 May 2019 none MIT — Details →
v4.1.1-0.20190530061753-918cee69eecf+incompatible 30 May 2019 none MIT — Details →
v4.1.0+incompatible 08 May 2019 none MIT — Details →
v4.0.3+incompatible 28 Apr 2019 none MIT — Details →
v4.0.3-0.20190401163054-fba20de8a7d3+incompatible 01 Apr 2019 none MIT — Details →
v0.0.0-20181210165837-a37e1e030434 10 Dec 2018 none MIT — Details →
v4.0.2+incompatible 10 Dec 2018 none MIT — Details →
v4.0.1+incompatible 04 Dec 2018 none MIT — Details →
v4.0.0+incompatible 23 Oct 2018 none MIT — Details →
v3.3.2+incompatible 13 Sep 2018 none MIT — Details →
v3.3.1+incompatible 03 Sep 2018 none MIT — Details →
v3.3.0+incompatible 23 Aug 2018 none MIT — Details →
v3.2.0+incompatible 19 Aug 2018 none MIT — Details →
v3.1.1+incompatible 16 Aug 2018 none MIT — Details →
v3.1.0+incompatible 14 Aug 2018 none MIT — Details →
v3.0.1+incompatible 10 Aug 2018 none MIT — Details →
v3.0.0+incompatible 30 May 2018 none MIT — Details →
v2.5.0+incompatible 23 May 2018 none MIT — Details →
v2.4.0+incompatible 22 May 2018 none MIT — Details →
v2.3.0+incompatible 20 May 2018 none MIT — Details →
v2.2.0+incompatible 15 May 2018 none MIT — Details →
v2.1.0+incompatible 15 May 2018 none MIT — Details →
v2.0.0+incompatible 14 May 2018 none MIT — Details →
v1.0.0 08 May 2018 none MIT — Details →
v0.1.0 05 May 2018 none MIT — Details →

All 42 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/jedib0t/go-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/jedib0t/go-pretty

Is github.com/jedib0t/go-pretty safe to use?

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

Vulert scores github.com/jedib0t/go-pretty 63/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/jedib0t/go-pretty affected?

No. v4.3.0+incompatible, 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/jedib0t/go-pretty should I use?

v4.3.0+incompatible 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/jedib0t/go-pretty have?

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

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

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/jedib0t/go-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.