Vulnerability Database · Go · Package report
gotest.tools: vulnerability history, versions and safety
gotest.tools 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 gotest.tools v2.2.0+incompatible i
Updated on 23 Oct 2026
Good news: v2.2.0+incompatible, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on v2.2.0+incompatible or newer. This can change: a vulnerability disclosed tomorrow can affect v2.2.0+incompatible too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v2.2.0+incompatible — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 576 i
- OpenSSF scorecard 3/10 i
- Last release 95 months ago i
- Licence Apache-2.0 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 gotest.tools, 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-20190807191733-04b215eaa79d 07 Aug 2019
- v1.4.1-0.20190807191733-04b215eaa79d 07 Aug 2019
- v0.0.0-20190807125525-85ad333a7715 07 Aug 2019
- v0.0.0-20190719212235-400e4d0d57c4 19 Jul 2019
- v1.4.1-0.20190719212235-400e4d0d57c4 19 Jul 2019
- v0.0.0-20190624233834-05ebafbffc79 24 Jun 2019
- v1.4.1-0.20190624233834-05ebafbffc79 24 Jun 2019
- v0.0.0-20190315080153-d1a6560d983a 15 Mar 2019
- v1.4.1-0.20190315080153-d1a6560d983a 15 Mar 2019
- v0.0.0-20190311073145-20c9fe7f37cf 11 Mar 2019
- v0.0.0-20190305074754-797fe34a8dd8 05 Mar 2019
- v0.0.0-20190213003422-d9c679ca0fef 13 Feb 2019
- v1.4.1-0.20190213003422-d9c679ca0fef 13 Feb 2019
- v0.0.0-20181223230014-1083505acf35 23 Dec 2018
- v1.4.1-0.20181223230014-1083505acf35 23 Dec 2018
- v2.2.1-0.20181205041756-bfe3ac532784+incompatible 05 Dec 2018
- v1.4.1-0.20181123051433-bcbf6e613274 23 Nov 2018
- v2.2.1-0.20181123051433-bcbf6e613274+incompatible 23 Nov 2018
- v3.0.0-20181123051433-bcbf6e613274+incompatible 23 Nov 2018
- v2.2.1-0.20181116163740-781e95fa3197+incompatible 16 Nov 2018
- v2.2.1-0.20181112171127-e829457826b8+incompatible 12 Nov 2018
- v2.2.1-0.20181112170402-13f9b0e945ed+incompatible 12 Nov 2018
- v2.2.1-0.20181112154112-6785feebd132+incompatible 12 Nov 2018
- v0.0.0-20181111182905-7c797b5133e5 11 Nov 2018
- v2.2.0+incompatible 11 Nov 2018
- v0.0.0-20181001141646-317cc193f525 01 Oct 2018
- v1.4.1-0.20181001141646-317cc193f525 01 Oct 2018
- v2.1.1-0.20181001141646-317cc193f525+incompatible 01 Oct 2018
- v3.0.0-20181001141646-317cc193f525+incompatible 01 Oct 2018
- v2.1.1-0.20180906153803-92091b3f341b+incompatible 06 Sep 2018
- v2.1.1-0.20180812162729-63bb51ce9126+incompatible 12 Aug 2018
- v2.1.1-0.20180805170218-7ddeb7f3244a+incompatible 05 Aug 2018
- v0.0.0-20180727082649-9526f90d185d 27 Jul 2018
- v2.1.1-0.20180709135822-38c0997bbdeb+incompatible 09 Jul 2018
- v2.1.1-0.20180624202818-5adb669c8ca0+incompatible 24 Jun 2018
- v2.1.1-0.20180619024631-1a97cc67d075+incompatible 19 Jun 2018
- v0.0.0-20180522130415-b6e20af1ed07 22 May 2018
- v2.1.0+incompatible 22 May 2018
- v2.0.0+incompatible 03 May 2018
- v1.4.0 21 Mar 2018
- v1.3.0 20 Feb 2018
- v1.2.0 11 Sep 2017
- v1.1.0 23 Aug 2017
- v1.0.0 14 Aug 2017
All 44 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.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for gotest.tools
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 gotest.tools
Is gotest.tools safe to use?
Vulert has no vulnerabilities on record for gotest.tools 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 gotest.tools's Vulert package health score?
Vulert scores gotest.tools 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 gotest.tools affected?
No. v2.2.0+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 gotest.tools should I use?
v2.2.0+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 gotest.tools have?
0 vulnerabilities are recorded for gotest.tools 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 gotest.tools vulnerabilities disclosed?
0 vulnerabilities were recorded for gotest.tools 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 gotest.tools 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 gotest.tools for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the gotest.tools version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.