Vulnerability Database · Go · Package report
github.com/mgutz/ansi: vulnerability history, versions and safety
github.com/mgutz/ansi is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/mgutz/ansi v0.0.0-20200706080929-d51e80ef957d i
Updated on 23 Oct 2026
Good news: v0.0.0-20200706080929-d51e80ef957d, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Inactive
What to do: Stay on v0.0.0-20200706080929-d51e80ef957d or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20200706080929-d51e80ef957d too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20200706080929-d51e80ef957d — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 426 i
- OpenSSF scorecard 1/10 i
- Last release 75 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/mgutz/ansi, 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.
- v0.0.0-20200706080929-d51e80ef957d 06 Jul 2020
- v0.0.0-20170322154318-187ed69e51a0 22 Mar 2017
- v0.0.0-20170322153854-ecebe6838662 22 Mar 2017
- v0.0.0-20170322153832-8bef9dabaa01 22 Mar 2017
- v0.0.0-20170206155736-9520e82c474b 06 Feb 2017
- v0.0.0-20170206155725-f4c46233f25a 06 Feb 2017
- v0.0.0-20170206155652-1d038424997b 06 Feb 2017
- v0.0.0-20151215201258-999d1bc55bf8 15 Dec 2015
- v0.0.0-20150914162238-c286dcecd19f 14 Sep 2015
- v0.0.0-20150709152456-452f5f539654 09 Jul 2015
- v0.0.0-20150709133643-5247d049a3df 09 Jul 2015
- v0.0.0-20150306154017-22ddafb24adc 06 Mar 2015
- v0.0.0-20150304162511-cc83c1ed67dc 04 Mar 2015
- v0.0.0-20150303233312-3f1dfc38493f 03 Mar 2015
- v0.0.0-20150303232256-1b8ff8760b8a 03 Mar 2015
- v0.0.0-20150303230905-bae6eb06f429 03 Mar 2015
- v0.0.0-20150227033142-58d20d34316b 27 Feb 2015
- v0.0.0-20141228113034-8e063c63ec3c 28 Dec 2014
- v0.0.0-20141227210202-fd952be66fb7 27 Dec 2014
- v0.0.0-20130515065447-376eb392d7d7 15 May 2013
- v0.0.0-20130515034927-05f7456d45df 15 May 2013
- v0.0.0-20130512180504-6c74472efebb 12 May 2013
All 22 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/mgutz/ansi
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
Questions
About github.com/mgutz/ansi
Is github.com/mgutz/ansi safe to use?
Vulert has no vulnerabilities on record for github.com/mgutz/ansi 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/mgutz/ansi's Vulert package health score?
Vulert scores github.com/mgutz/ansi 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/mgutz/ansi affected?
No. v0.0.0-20200706080929-d51e80ef957d, 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/mgutz/ansi should I use?
v0.0.0-20200706080929-d51e80ef957d 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/mgutz/ansi have?
0 vulnerabilities are recorded for github.com/mgutz/ansi 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/mgutz/ansi vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/mgutz/ansi 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/mgutz/ansi 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/mgutz/ansi for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/mgutz/ansi version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.