VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

github.com/docopt/docopt-go 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.

See all github.com/docopt/docopt-go vulnerabilities

Vulert verdict on github.com/docopt/docopt-go v0.0.0-20180111231733-ee0de3bc6815 i

Updated on 23 Oct 2026

Good news: v0.0.0-20180111231733-ee0de3bc6815, the version you would install today, has no known vulnerabilities.

Package health score 69/100
  • Security No known security issues
  • Maintenance Unmaintained
  • Popularity Widely used
  • Community Moderate

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

  • Current release v0.0.0-20180111231733-ee0de3bc6815 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,443 i
  • Last release 105 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/docopt/docopt-go, 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-20180111231733-ee0de3bc6815 11 Jan 2018 none MIT — Details →
v0.0.0-20180109104340-e4ebb8fef9d6 09 Jan 2018 none MIT — Details →
v0.0.0-20180107170356-18be18be6ccf 07 Jan 2018 none MIT — Details →
v0.0.0-20180103153630-541df4fef4db 03 Jan 2018 none MIT — Details →
v0.0.0-20170612005551-65b50539475d 12 Jun 2017 none MIT — Details →
v0.0.0-20170612000544-0bcb9abb885d 12 Jun 2017 none MIT — Details →
v0.0.0-20161219145411-333d7a2d454d 19 Dec 2016 none MIT — Details →
v0.0.0-20161219145358-7042aa85dad3 19 Dec 2016 none MIT — Details →
v0.0.0-20161215162946-edcfa93ddbba 15 Dec 2016 none MIT — Details →
v0.0.0-20161208024159-1d48af9adc46 08 Dec 2016 none MIT — Details →
v0.0.0-20161205132051-f3a752914a4f 05 Dec 2016 none MIT — Details →
v0.0.0-20161201192009-00fbbf0e542a 01 Dec 2016 none MIT — Details →
v0.0.0-20161201181551-1077e5116cd2 01 Dec 2016 none MIT — Details →
v0.0.0-20161109174230-4dd9d7c5ad6d 09 Nov 2016 none MIT — Details →
v0.0.0-20161107202009-6af82220160d 07 Nov 2016 none MIT — Details →
v0.0.0-20160216232012-784ddc588536 16 Feb 2016 none MIT — Details →
v0.0.0-20160216224016-265a104c4a74 16 Feb 2016 none MIT — Details →
v0.0.0-20141211223326-f7b99ad9384d 11 Dec 2014 none MIT — Details →
v0.0.0-20141128170934-854c423c8108 28 Nov 2014 none MIT — Details →
v0.0.0-20141128163207-34a18d83a3a5 28 Nov 2014 none MIT — Details →
v0.0.0-20141126214142-4cb69f7c3be1 26 Nov 2014 none MIT — Details →
v0.0.0-20140806175443-c5dac5363019 06 Aug 2014 none MIT — Details →
v0.0.0-20140526175517-7fb3e6472805 26 May 2014 none MIT — Details →
v0.0.0-20140425015413-a7ddcdd6c754 25 Apr 2014 none MIT — Details →
v0.0.0-20140420171950-b74119e4500c 20 Apr 2014 none MIT — Details →
v0.0.0-20140420165956-326192fcd8b0 20 Apr 2014 none MIT — Details →
v0.0.0-20131112070533-717d0bc993e7 12 Nov 2013 none MIT — Details →
v0.0.0-20131008070323-0cef38b87f89 08 Oct 2013 none MIT — Details →
v0.0.0-20130916223135-13e13e65a1d8 16 Sep 2013 none MIT — Details →
v0.0.0-20130915202357-5590636c1495 15 Sep 2013 none MIT — Details →
v0.0.0-20130907191909-4dcfb5a0ed42 07 Sep 2013 none MIT — Details →
v0.0.0-20130903014608-5049e98f754f 03 Sep 2013 none MIT — Details →
v0.0.0-20130830202956-add161be265c 30 Aug 2013 none MIT — Details →
v0.0.0-20130830194734-31e3220e578c 30 Aug 2013 none MIT — Details →
v0.0.0-20130830014409-09700dc72ed2 30 Aug 2013 none MIT — Details →

All 35 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/docopt/docopt-go

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/docopt/docopt-go

Is github.com/docopt/docopt-go safe to use?

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

Vulert scores github.com/docopt/docopt-go 69/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/docopt/docopt-go affected?

No. v0.0.0-20180111231733-ee0de3bc6815, 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/docopt/docopt-go should I use?

v0.0.0-20180111231733-ee0de3bc6815 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/docopt/docopt-go have?

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

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

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