VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

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

Vulert verdict on github.com/go-check/check v2.0.0-20190902080502-41f04d3bba15+incompatible i

Updated on 23 Oct 2026

Good news: v2.0.0-20190902080502-41f04d3bba15+incompatible, the version you would install today, has no known vulnerabilities.

Package health score 57/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Widely used
  • Community Quiet

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

  • Current release v2.0.0-20190902080502-41f04d3bba15+incompatible — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 694 i
  • OpenSSF scorecard 2/10 i
  • Last release 85 months ago i
  • Licence BSD-2-Clause 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/go-check/check, 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-20201128035030-22ab2dfb190c 28 Nov 2020 none BSD-2-Clause — Details →
v0.0.0-20200902074654-038fdea0a05b 02 Sep 2020 none BSD-2-Clause — Details →
v0.0.0-20200227125254-8fa46927fb4f 27 Feb 2020 none BSD-2-Clause — Details →
v0.0.0-20190902080502-41f04d3bba15 02 Sep 2019 none BSD-2-Clause — Details →
v2.0.0-20190902080502-41f04d3bba15+incompatible 02 Sep 2019 none BSD-2-Clause — Details →
v0.0.0-20180628173108-788fd7840127 28 Jun 2018 none BSD-2-Clause — Details →
v0.0.0-20161208181325-20d25e280405 08 Dec 2016 none BSD-2-Clause — Details →
v0.0.0-20161122135753-aa8c43564278 22 Nov 2016 none BSD-2-Clause — Details →
v0.0.0-20161122135549-c02a90fcd860 22 Nov 2016 none BSD-2-Clause — Details →
v0.0.0-20160105164936-4f90aeace3a2 05 Jan 2016 none BSD-2-Clause — Details →
v0.0.0-20151214180844-7a665ab06bf1 14 Dec 2015 none BSD-2-Clause — Details →
v0.0.0-20151209162144-1b52f533ff42 09 Dec 2015 none BSD-2-Clause — Details →
v0.0.0-20150729080431-11d3bc7aa68e 29 Jul 2015 none BSD-2-Clause — Details →
v0.0.0-20150729024625-0674b0d5cf19 29 Jul 2015 none BSD-2-Clause — Details →
v0.0.0-20150626105028-b3d3430320d4 26 Jun 2015 none BSD-2-Clause — Details →
v0.0.0-20150617050919-758efeaadfba 17 Jun 2015 none BSD-2-Clause — Details →
v0.0.0-20150610233030-8d49746f13e4 10 Jun 2015 none BSD-2-Clause — Details →
v0.0.0-20141024133853-64131543e789 24 Oct 2014 none BSD-2-Clause — Details →
v0.0.0-20141023170815-5300ee662a31 23 Oct 2014 none BSD-2-Clause — Details →
v0.0.0-20141020161553-119e19957362 20 Oct 2014 none BSD-2-Clause — Details →
v0.0.0-20140827135841-91ae5f88a67b 27 Aug 2014 none BSD-2-Clause — Details →
v0.0.0-20140724151337-a35d312565c0 24 Jul 2014 none BSD-2-Clause — Details →
v0.0.0-20140709144134-5b76b26efe7f 09 Jul 2014 none BSD-2-Clause — Details →
v0.0.0-20140703180401-5586b28e002e 03 Jul 2014 none BSD-2-Clause — Details →
v0.0.0-20140703175111-7bf927bda568 03 Jul 2014 none BSD-2-Clause — Details →
v0.0.0-20140401160002-871360013c92 01 Apr 2014 none BSD-2-Clause — Details →
v0.0.0-20140401040844-163297374fe1 01 Apr 2014 none — — Details →
v0.0.0-20140401032107-95981eb8e2c8 01 Apr 2014 none BSD-2-Clause — Details →
v0.0.0-20140401031510-30a6840d0976 01 Apr 2014 none BSD-2-Clause — Details →
v0.0.0-20140401012801-7001e3a65c8a 01 Apr 2014 none BSD-2-Clause — Details →
v0.0.0-20140401012214-6cce186aca8d 01 Apr 2014 none BSD-2-Clause — Details →
v0.0.0-20140225173054-eb6ee6f84d0a 25 Feb 2014 none BSD-2-Clause — Details →
v0.0.0-20140225171317-2368793def62 25 Feb 2014 none BSD-2-Clause — Details →
v0.0.0-20140225165218-5368c0b8e953 25 Feb 2014 none BSD-2-Clause — Details →
v0.0.0-20140218170259-294310f73988 18 Feb 2014 none BSD-2-Clause — Details →
v0.0.0-20140218161900-9571945b7827 18 Feb 2014 none BSD-2-Clause — Details →
v0.0.0-20140127131816-e54ca221ea41 27 Jan 2014 none BSD-2-Clause — Details →
v0.0.0-20130302024745-894c6356ad94 02 Mar 2013 none BSD-3-Clause — Details →
v0.0.0-20130301225647-10bfe0586b48 01 Mar 2013 none BSD-3-Clause — Details →
v0.0.0-20130301202038-11552f46f646 01 Mar 2013 none BSD-3-Clause — Details →
v0.0.0-20121211023052-df04ba4bf45c 11 Dec 2012 none BSD-3-Clause — Details →
v0.0.0-20121207015649-a3853f57e807 07 Dec 2012 none BSD-3-Clause — Details →
v0.0.0-20121206045948-2e67dd435007 06 Dec 2012 none BSD-3-Clause — Details →
v0.0.0-20121206045127-ca7658329481 06 Dec 2012 none BSD-3-Clause — Details →
v0.0.0-20120828194703-80938f99130b 28 Aug 2012 none BSD-3-Clause — Details →
v0.0.0-20120828193657-87cd250bf99b 28 Aug 2012 none BSD-3-Clause — Details →
v0.0.0-20120724193107-a6ae344c3dd3 24 Jul 2012 none BSD-3-Clause — Details →
v0.0.0-20120722215800-3819dcd4d76f 22 Jul 2012 none BSD-3-Clause — Details →
v0.0.0-20120722012253-f5929abb35e8 22 Jul 2012 none BSD-3-Clause — Details →
v0.0.0-20120322135907-a7521c2bee25 22 Mar 2012 none BSD-3-Clause — Details →
v0.0.0-20120314142229-71b0e18ccc8f 14 Mar 2012 none BSD-3-Clause — Details →
v0.0.0-20120228105955-2444dcad6f5c 28 Feb 2012 none BSD-3-Clause — Details →
v0.0.0-20120225190212-91ccb3415f34 25 Feb 2012 none BSD-3-Clause — Details →
v0.0.0-20120225165837-0ef35b5956b3 25 Feb 2012 none BSD-3-Clause — Details →
v0.0.0-20120217015702-f6a24a909ca8 17 Feb 2012 none BSD-3-Clause — Details →
v0.0.0-20111213211104-884dd149c8d5 13 Dec 2011 none BSD-3-Clause — Details →
v0.0.0-20111202160822-5012cda146dc 02 Dec 2011 none BSD-3-Clause — Details →
v0.0.0-20111111011013-c1f6926cbef7 11 Nov 2011 none BSD-3-Clause — Details →
v0.0.0-20111109172304-658635c78a59 09 Nov 2011 none BSD-3-Clause — Details →
v0.0.0-20111108150950-e0769641a5ce 08 Nov 2011 none BSD-3-Clause — Details →
v0.0.0-20111019185426-25bfe07a2316 19 Oct 2011 none BSD-3-Clause — Details →
v0.0.0-20110910025417-19301ede7abc 10 Sep 2011 none BSD-3-Clause — Details →
v0.0.0-20110704133843-cbdd56501054 04 Jul 2011 none BSD-3-Clause — Details →
v0.0.0-20110624214526-30bc90d0eed9 24 Jun 2011 none BSD-3-Clause — Details →
v0.0.0-20110428110215-629f604619a7 28 Apr 2011 none BSD-3-Clause — Details →
v0.0.0-20110415031846-7b2d3d1676cd 15 Apr 2011 none BSD-3-Clause — Details →
v0.0.0-20110414114536-0c7a6063dde7 14 Apr 2011 none BSD-3-Clause — Details →
v0.0.0-20110407172702-0a454d9aac03 07 Apr 2011 none BSD-3-Clause — Details →
v0.0.0-20110407070226-fc963093a7ec 07 Apr 2011 none BSD-3-Clause — Details →
v0.0.0-20110315010856-2ec1a84a3bd6 15 Mar 2011 none BSD-3-Clause — Details →
v0.0.0-20110201101315-bac48700aad5 01 Feb 2011 none BSD-3-Clause — Details →
v0.0.0-20110201012516-a6e05a01a23a 01 Feb 2011 none BSD-3-Clause — Details →
v0.0.0-20110131022216-2f30592f7cb0 31 Jan 2011 none BSD-3-Clause — Details →
v0.0.0-20110117234448-af184e246399 17 Jan 2011 none BSD-3-Clause — Details →
v0.0.0-20110116181039-1973cb8f28dd 16 Jan 2011 none BSD-3-Clause — Details →
v0.0.0-20110115193340-71665545c151 15 Jan 2011 none BSD-3-Clause — Details →
v0.0.0-20101226160527-281f40d6fb75 26 Dec 2010 none BSD-3-Clause — Details →
v0.0.0-20101224190212-a3c39e2de4b9 24 Dec 2010 none BSD-3-Clause — Details →
v0.0.0-20101222053924-20280675a781 22 Dec 2010 none BSD-3-Clause — Details →
v0.0.0-20101119225710-cea0917d633e 19 Nov 2010 none BSD-3-Clause — Details →
v0.0.0-20101117182712-3b013b8583be 17 Nov 2010 none BSD-3-Clause — Details →
v0.0.0-20101115191702-05117828ea4c 15 Nov 2010 none — — Details →
v0.0.0-20101108022346-b3effdb75b00 08 Nov 2010 none — — Details →
v0.0.0-20101107184613-761c5a6009f7 07 Nov 2010 none — — Details →
v0.0.0-20101023213658-8c61cdfcdba0 23 Oct 2010 none — — Details →
v0.0.0-20100703202944-a64e59509297 03 Jul 2010 none — — Details →
v0.0.0-20100629040438-4484550226d1 29 Jun 2010 none — — Details →
v0.0.0-20100629012914-71971acd9449 29 Jun 2010 none — — Details →

All 88 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/go-check/check

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

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

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

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

No. v2.0.0-20190902080502-41f04d3bba15+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/go-check/check should I use?

v2.0.0-20190902080502-41f04d3bba15+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/go-check/check have?

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

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

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