Vulnerability Database · Go · Package report
gopkg.in/validator.v2: vulnerability history, versions and safety
gopkg.in/validator.v2 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 gopkg.in/validator.v2 v2.0.1 i
Updated on 23 Oct 2026
Good news: v2.0.1, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Unmaintained
- Popularity Not enough data
- Community Not enough data
What to do: Stay on v2.0.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v2.0.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v2.0.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Last release 54 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 gopkg.in/validator.v2, 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.
- v2.0.0-20220405145527-849d4e5cae3c 05 Apr 2022
- v2.0.1 05 Apr 2022
- v2.0.0-20210331031555-b37d688a7fb0 31 Mar 2021
- v2.0.0-20210331025828-c73a627d7361 31 Mar 2021
- v2.0.0-20200605151824-2b28d334fa05 05 Jun 2020
- v2.0.0-20191107172027-c3144fdedc21 07 Nov 2019
- v2.0.0-20191029180049-30e574a82075 29 Oct 2019
- v2.0.0-20191008145730-5614e8810ea7 08 Oct 2019
- v2.0.0-20190827175613-1a84e0480e5b 27 Aug 2019
- v2.0.0-20190826203917-07057546915e 26 Aug 2019
- v2.0.0-20190822201109-3e97113cc9be 22 Aug 2019
- v2.0.0-20190822200131-d62d7f39f9a1 22 Aug 2019
- v2.0.0-20180514200540-135c24b11c19 14 May 2018
- v2.0.0-20180328152636-a1c202c4a952 28 Mar 2018
- v2.0.0-20180205153750-59c90c7046f6 05 Feb 2018
- v2.0.0-20170814132753-460c83432a98 14 Aug 2017
- v2.0.0-20170509203904-07ffaad256c8 09 May 2017
- v2.0.0-20170102155238-2227f4d85f69 02 Jan 2017
- v2.0.0-20160824142509-0a9835d809fb 24 Aug 2016
- v2.0.0-20160201165114-3e4f037f12a1 01 Feb 2016
- v2.0.0-20160112115406-894306663cbe 12 Jan 2016
- v2.0.0-20141123095626-8e445b9dc14a 23 Nov 2014
- v2.0.0-20140827171050-277e608355a8 27 Aug 2014
All 23 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 gopkg.in/validator.v2
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 gopkg.in/validator.v2
Is gopkg.in/validator.v2 safe to use?
Vulert has no vulnerabilities on record for gopkg.in/validator.v2 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 gopkg.in/validator.v2's Vulert package health score?
Vulert scores gopkg.in/validator.v2 67/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 gopkg.in/validator.v2 affected?
No. v2.0.1, 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 gopkg.in/validator.v2 should I use?
v2.0.1 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 gopkg.in/validator.v2 have?
0 vulnerabilities are recorded for gopkg.in/validator.v2 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 gopkg.in/validator.v2 vulnerabilities disclosed?
0 vulnerabilities were recorded for gopkg.in/validator.v2 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 gopkg.in/validator.v2 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 gopkg.in/validator.v2 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the gopkg.in/validator.v2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.