Vulnerability Database · Go · Package report

github.com/cpuguy83/go-md2man: vulnerability history, versions and safety

github.com/cpuguy83/go-md2man 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/cpuguy83/go-md2man v1.0.10 i

Updated on 23 Oct 2026

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

Package health score 52/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Quiet

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

  • Current release v1.0.10 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 271 i
  • OpenSSF scorecard 3/10 i
  • Last release 91 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/cpuguy83/go-md2man, 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-20190314224556-7762f7e404f8 14 Mar 2019 none MIT — Details →
v1.0.10 14 Mar 2019 none MIT — Details →
v1.0.9 14 Mar 2019 none MIT — Details →
v1.0.9-0.20190314182720-7c3bbf680b77 14 Mar 2019 none MIT — Details →
v0.0.0-20180619205630-691ee98543af 19 Jun 2018 none MIT — Details →
v1.0.9-0.20180619205630-691ee98543af 19 Jun 2018 none MIT — Details →
v1.0.9-0.20180618162052-d138fd8aeb08 18 Jun 2018 none MIT — Details →
v0.0.0-20180215021727-48d8747a2ca1 15 Feb 2018 none MIT — Details →
v1.0.9-0.20180215021727-48d8747a2ca1 15 Feb 2018 none MIT — Details →
v1.0.9-0.20180214190710-8fe40b5a6ad9 14 Feb 2018 none MIT — Details →
v1.0.9-0.20180209162919-391147570fb4 09 Feb 2018 none MIT — Details →
v1.0.9-0.20180208215341-1cd83043fda3 08 Feb 2018 none MIT — Details →
v1.0.9-0.20180205143020-dc9f53734905 05 Feb 2018 none MIT — Details →
v1.0.9-0.20180203201709-124c15a91abb 03 Feb 2018 none MIT — Details →
v1.0.9-0.20180129160249-c6b32e290712 29 Jan 2018 none MIT — Details →
v0.0.0-20180119155312-20f5889cbdc3 19 Jan 2018 none MIT — Details →
v1.0.8 19 Jan 2018 none MIT — Details →
v1.0.8-0.20180119015251-60a40f99d4db 19 Jan 2018 none MIT — Details →
v0.0.0-20171223160537-8d868be6e9bf 23 Dec 2017 none MIT — Details →
v1.0.8-0.20171223160537-8d868be6e9bf 23 Dec 2017 none MIT — Details →
v1.0.8-0.20171109184735-dba60c42a4d4 09 Nov 2017 none MIT — Details →
v0.0.0-20170827120120-1d903dcb7499 27 Aug 2017 none MIT — Details →
v1.0.7 27 Aug 2017 none MIT — Details →
v1.0.7-0.20170827120120-1d903dcb7499 27 Aug 2017 none MIT — Details →
v1.0.7-0.20170826211706-ddf7deab5a6d 26 Aug 2017 none MIT — Details →
v1.0.7-0.20170824211020-43b0d151ead7 24 Aug 2017 none MIT — Details →
v0.0.0-20170603125239-23709d084719 03 Jun 2017 none MIT — Details →
v1.0.7-0.20170603125239-23709d084719 03 Jun 2017 none MIT — Details →
v2.0.0-20170603125239-23709d084719+incompatible 03 Jun 2017 none MIT — Details →
v1.0.7-0.20170602164905-419afbdd20ab 02 Jun 2017 none MIT — Details →
v0.0.0-20170509204418-bcc0a711c5e6 09 May 2017 none MIT — Details →
v1.0.7-0.20170509204418-bcc0a711c5e6 09 May 2017 none MIT — Details →
v1.0.7-0.20170509204119-469757f07182 09 May 2017 none MIT — Details →
v1.0.7-0.20170318145442-2c501be952a3 18 Mar 2017 none MIT — Details →
v0.0.0-20160904160859-a65d4d2de4d5 04 Sep 2016 none MIT — Details →
v1.0.6 04 Sep 2016 none MIT — Details →
v1.0.6-0.20160904160859-a65d4d2de4d5 04 Sep 2016 none MIT — Details →
v1.0.6-0.20160904061112-648eed146d3f 04 Sep 2016 none MIT — Details →
v1.0.6-0.20160902131508-6a13ed3fca0e 02 Sep 2016 none MIT — Details →
v1.0.5 05 Jan 2016 none MIT — Details →
v1.0.5-0.20151220133412-a8f937e11314 20 Dec 2015 none MIT — Details →
v0.0.0-20150803153522-71acacd42f85 03 Aug 2015 none MIT — Details →
v1.0.4 03 Aug 2015 none MIT — Details →
v1.0.4-0.20150803143231-626bd0ac0fb1 03 Aug 2015 none MIT — Details →
v1.0.3 18 Jun 2015 none MIT — Details →
v1.0.3-0.20150617184059-a267fe207dba 17 Jun 2015 none MIT — Details →
v1.0.3-0.20150608134528-7cefbfaa5aab 08 Jun 2015 none MIT — Details →
v0.0.0-20150209213335-2831f11f66ff 09 Feb 2015 none MIT — Details →
v1.0.3-0.20150209213335-2831f11f66ff 09 Feb 2015 none MIT — Details →
v1.0.3-0.20150209210036-001ceef89147 09 Feb 2015 none MIT — Details →
v1.0.2 27 Jan 2015 none — — Details →
v1.0.1 27 Jan 2015 none — — Details →
v0.0.0-20140804210547-9e6aa16fb761 04 Aug 2014 none — — Details →
v0.0.0-20140802025810-32594c8b952e 02 Aug 2014 none — — Details →

All 54 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/cpuguy83/go-md2man

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/cpuguy83/go-md2man

Is github.com/cpuguy83/go-md2man safe to use?

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

Vulert scores github.com/cpuguy83/go-md2man 52/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/cpuguy83/go-md2man affected?

No. v1.0.10, 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/cpuguy83/go-md2man should I use?

v1.0.10 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/cpuguy83/go-md2man have?

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

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

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