VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/mattn/goveralls: vulnerability history, versions and safety

github.com/mattn/goveralls 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/mattn/goveralls vulnerabilities

Vulert verdict on github.com/mattn/goveralls v0.0.12 i

Updated on 23 Oct 2026

Good news: v0.0.12, the version you would install today, has no known vulnerabilities.

Package health score 65/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

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

  • Current release v0.0.12 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 796 i
  • OpenSSF scorecard 3/10 i
  • Last release 41 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/mattn/goveralls, 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.13-0.20260329110320-3c566820b187 29 Mar 2026 none MIT — Details →
v0.0.12 26 Apr 2023 none MIT — Details →
v0.0.12-0.20230426122619-b03136803f26 26 Apr 2023 none MIT — Details →
v0.0.12-0.20230425121104-3fa30c79c837 25 Apr 2023 none MIT — Details →
v0.0.12-0.20230424141245-3a2df0649fdb 24 Apr 2023 none MIT — Details →
v0.0.12-0.20230424141138-e1ce097860d2 24 Apr 2023 none MIT — Details →
v0.0.12-0.20220628142807-602d73e9edb5 28 Jun 2022 none MIT — Details →
v0.0.12-0.20220628142655-c34ee2774d9b 28 Jun 2022 none MIT — Details →
v0.0.11 21 Sep 2021 none — — Details →
v0.0.10 21 Sep 2021 none — — Details →
v0.0.9 25 May 2021 none — — Details →
v0.0.8 01 Dec 2020 none — — Details →
v0.0.8-0.20201112172731-06871f92f595 12 Nov 2020 none — — Details →
v0.0.8-0.20201010230304-b5b88fcf966f 10 Oct 2020 none — — Details →
v0.0.7 08 Sep 2020 none — — Details →
v0.0.7-0.20200819115146-21feffdfd590 19 Aug 2020 none — — Details →
v0.0.6 25 May 2020 none — — Details →
v0.0.5 13 Jan 2020 none — — Details →
v0.0.5-0.20200113054754-0ff165140b8b 13 Jan 2020 none — — Details →
v0.0.5-0.20191218111940-b2bbf7ba3ef2 18 Dec 2019 none — — Details →
v0.0.5-0.20191119023345-1ebf065cc210 19 Nov 2019 none — — Details →
v0.0.4 30 Oct 2019 none — — Details →
v0.0.3 05 Jun 2019 none — — Details →
v0.0.3-0.20190605103025-4d9899298d21 05 Jun 2019 none — — Details →
v0.0.3-0.20190325144123-900af2b6e486 25 Mar 2019 none — — Details →
v0.0.3-0.20190202165311-dc71fe1ae554 02 Feb 2019 none — — Details →
v0.0.3-0.20190104065612-6d60b0f2282c 04 Jan 2019 none — — Details →
v0.0.3-0.20181003231917-722b7311a4d0 03 Oct 2018 none — — Details →
v0.0.3-0.20180927095025-09de9e3c9dd2 27 Sep 2018 none — — Details →
v0.0.3-0.20180821023734-88fc0d50edb2 21 Aug 2018 none — — Details →
v0.0.3-0.20180620004742-2dd928a4c258 20 Jun 2018 none — — Details →
v0.0.3-0.20180319021929-1c14a4061c1c 19 Mar 2018 none — — Details →
v0.0.3-0.20180301143612-a419d25dbaef 01 Mar 2018 none — — Details →
v0.0.3-0.20180119200015-9b42bb60ff6b 19 Jan 2018 none — — Details →
v0.0.2 14 Nov 2017 none — — Details →
v0.0.0-20171004103333-a32275e3b6ad 04 Oct 2017 none — — Details →
v0.0.2-0.20170813124947-0ddc65b7624a 13 Aug 2017 none — — Details →
v0.0.2-0.20170513160234-a2cbbd7cdce4 13 May 2017 none — — Details →
v0.0.0-20170311134016-a99c5ee06aee 11 Mar 2017 none — — Details →
v0.0.0-20170204120415-8482d0ebd2a6 04 Feb 2017 none — — Details →
v0.0.2-0.20170204120415-8482d0ebd2a6 04 Feb 2017 none — — Details →
v0.0.0-20161216102646-61ac1a6b48f7 16 Dec 2016 none — — Details →
v0.0.2-0.20161216102646-61ac1a6b48f7 16 Dec 2016 none — — Details →
v0.0.2-0.20161108164455-a63d65fe590e 08 Nov 2016 none — — Details →
v0.0.0-20161002124156-edf7508a2bcb 02 Oct 2016 none — — Details →
v0.0.1 12 Sep 2016 none — — Details →
v0.0.0-20160517145731-de5a843d32a9 17 May 2016 none — — Details →
v0.0.0-20160320114920-b8787b61088a 20 Mar 2016 none — — Details →
v0.0.0-20160108181729-025ace5d02b8 08 Jan 2016 none — — Details →
v0.0.0-20151102022726-7e68e2744ddc 02 Nov 2015 none — — Details →
v0.0.0-20141115163752-eddc23373103 15 Nov 2014 none — — Details →

All 51 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/mattn/goveralls

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/mattn/goveralls

Is github.com/mattn/goveralls safe to use?

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

Vulert scores github.com/mattn/goveralls 65/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/mattn/goveralls affected?

No. v0.0.12, 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/mattn/goveralls should I use?

v0.0.12 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/mattn/goveralls have?

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

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

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