Vulnerability Database · Go · Package report
github.com/niemeyer/pretty: vulnerability history, versions and safety
github.com/niemeyer/pretty 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/niemeyer/pretty v0.0.0-20200227124842-a10e7caefd8e i
Updated on 23 Oct 2026
Good news: v0.0.0-20200227124842-a10e7caefd8e, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.0-20200227124842-a10e7caefd8e or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20200227124842-a10e7caefd8e too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20200227124842-a10e7caefd8e — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 9 i
- OpenSSF scorecard 2/10 i
- Last release 79 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/niemeyer/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.
- v0.0.0-20200227124842-a10e7caefd8e 27 Feb 2020
- v0.0.0-20160823170715-cfb55aafdaf3 23 Aug 2016
- v0.0.0-20160708215748-737b74a46c4b 08 Jul 2016
- v0.0.0-20160707214721-7497514e3754 07 Jul 2016
- v0.0.0-20160707214038-fcfa3241d869 07 Jul 2016
- v0.0.0-20160707213922-5da52abd6af8 07 Jul 2016
- v0.0.0-20160707212242-8fb778d21b15 07 Jul 2016
- v0.0.0-20160707211711-c49dea8a01a4 07 Jul 2016
- v0.0.0-20160325215624-add1dbc86daf 25 Mar 2016
- v0.0.0-20160325183721-b19c9bac1a28 25 Mar 2016
- v0.0.0-20150520163514-e6ac2fc51e89 20 May 2015
- v0.0.0-20150119221228-cb0850c1681c 19 Jan 2015
- v0.0.0-20150119101127-e5594928ca7b 19 Jan 2015
- v0.0.0-20140930012423-e03c43e1f929 30 Sep 2014
- v0.0.0-20140812000539-f31442d60e51 12 Aug 2014
- v0.0.0-20140807174246-4d1dc9b4e969 07 Aug 2014
- v0.0.0-20140807173932-01bc0efed7b7 07 Aug 2014
- v0.0.0-20140804231824-5feda8d40680 04 Aug 2014
- v0.0.0-20140723054909-088c856450c0 23 Jul 2014
- v0.0.0-20140722061047-18947b1381c4 22 Jul 2014
- v0.0.0-20130510082846-bc9499caa0f4 10 May 2013
- v0.0.0-20130508051439-3e586b5b617b 08 May 2013
- v0.0.0-20130508021354-c2c013616406 08 May 2013
- v0.0.0-20130507041328-70b415e34a55 07 May 2013
- v0.0.0-20130507041305-6dec4dadca1e 07 May 2013
- v0.0.0-20130507033607-6f6db302adeb 07 May 2013
- v0.0.0-20130507033344-08e859034c9c 07 May 2013
- v0.0.0-20130503055225-2c2f68c2ef98 03 May 2013
- v0.0.0-20130503051328-61ba5e4926f6 03 May 2013
- v0.0.0-20130119010507-195524255c32 19 Jan 2013
- v0.0.0-20121222053239-46b3e070c3d7 22 Dec 2012
- v0.0.0-20121222031110-5ce225cb8211 22 Dec 2012
- v0.0.0-20121222031024-c6123a7570c9 22 Dec 2012
- v0.0.0-20120225203542-4c5f1d70177a 25 Feb 2012
- v0.0.0-20110608085334-ac395b7fd275 08 Jun 2011
- v0.0.0-20110504215442-2795cc3249e4 04 May 2011
- v0.0.0-20110419012625-d599dd2ad1fc 19 Apr 2011
- v0.0.0-20110419012415-dfe8fc0bebd2 19 Apr 2011
- v0.0.0-20110118020410-45b22bc2b61d 18 Jan 2011
- v0.0.0-20110114033108-d1a3b0e8f743 14 Jan 2011
- v0.0.0-20110114032736-b5f2db3a8000 14 Jan 2011
- v0.0.0-20110114024311-bc50154b02bf 14 Jan 2011
- v0.0.0-20110114023929-41fe116fa345 14 Jan 2011
- v0.0.0-20110114022519-131db13b2ac8 14 Jan 2011
- v0.0.0-20110114015839-32dd01cff21f 14 Jan 2011
All 45 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/niemeyer/pretty
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/niemeyer/pretty
Is github.com/niemeyer/pretty safe to use?
Vulert has no vulnerabilities on record for github.com/niemeyer/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/niemeyer/pretty's Vulert package health score?
Vulert scores github.com/niemeyer/pretty 44/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/niemeyer/pretty affected?
No. v0.0.0-20200227124842-a10e7caefd8e, 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/niemeyer/pretty should I use?
v0.0.0-20200227124842-a10e7caefd8e 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/niemeyer/pretty have?
0 vulnerabilities are recorded for github.com/niemeyer/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/niemeyer/pretty vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/niemeyer/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/niemeyer/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/niemeyer/pretty for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/niemeyer/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.