Vulnerability Database · Go · Package report
github.com/mwitkow/go-proto-validators: vulnerability history, versions and safety
github.com/mwitkow/go-proto-validators 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.
See all github.com/mwitkow/go-proto-validators vulnerabilities
Vulert verdict on github.com/mwitkow/go-proto-validators v0.3.2 i
Updated on 23 Oct 2026
Good news: v0.3.2, 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 v0.3.2 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.3.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.3.2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 1,101 i
- OpenSSF scorecard 1/10 i
- Last release 74 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 github.com/mwitkow/go-proto-validators, 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-20221024084913-875cb952c25c 24 Oct 2022
- v0.3.3-0.20221024084913-875cb952c25c 24 Oct 2022
- v0.3.3-0.20220116182411-cbb9a62f179f 16 Jan 2022
- v0.3.3-0.20200819190808-07328cb5aa02 19 Aug 2020
- v0.3.2 14 Aug 2020
- v0.3.1 11 Aug 2020
- v0.3.1-0.20200805174138-b3c7c064fabe 05 Aug 2020
- v0.3.1-0.20200803145412-e240e1621c57 03 Aug 2020
- v0.3.1-0.20200608075855-03d0cea8158a 08 Jun 2020
- v0.3.0 24 Dec 2019
- v0.2.1-0.20191111084321-3ad4d6c6d367 11 Nov 2019
- v0.0.0-20190920080900-9a5874edf402 20 Sep 2019
- v0.2.1-0.20190920080900-9a5874edf402 20 Sep 2019
- v0.2.0 17 Sep 2019
- v0.1.1-0.20190917150859-9b3550400536 17 Sep 2019
- v0.1.0 08 Aug 2019
- v0.0.0-20190709101305-c00cd28f239a 09 Jul 2019
- v0.0.0-20190709081949-fef10b927e0a 09 Jul 2019
- v0.0.0-20190709080137-372f141c805f 09 Jul 2019
- v0.0.0-20190708224541-f9b289b217ec 08 Jul 2019
- v0.0.0-20190708214746-fbdcedf3a555 08 Jul 2019
- v0.0.0-20190708211921-2072a03ac661 08 Jul 2019
- v0.0.0-20190212092829-1f388280e944 12 Feb 2019
- v0.0.0-20180618151004-b314e1726426 18 Jun 2018
- v0.0.0-20180403085117-0950a7990007 03 Apr 2018
- v0.0.0-20180331120546-646922ec4d2a 31 Mar 2018
- v0.0.0-20170220212302-a55ca57f374a 20 Feb 2017
- v0.0.0-20170123084445-338b36f732eb 23 Jan 2017
- v0.0.0-20161212141758-32cf83ab001c 12 Dec 2016
- v0.0.0-20161209092243-76e7ba899896 09 Dec 2016
- v0.0.0-20161209075702-144902977ba1 09 Dec 2016
- v0.0.0-20161208234652-92e8677c7260 08 Dec 2016
- v0.0.0-20161203155911-05efc88b4588 03 Dec 2016
- v0.0.0-20161202095651-fdd685c52c05 02 Dec 2016
- v0.0.0-20161201223613-96bfd7c2daf8 01 Dec 2016
- v0.0.0-20161116154657-306642928dd0 16 Nov 2016
- v0.0.0-20161111112029-487331a85b48 11 Nov 2016
- v0.0.0-20160812081404-3a714787fdc0 12 Aug 2016
- v0.0.0-20160812080825-247a6ad8a200 12 Aug 2016
- v0.0.0-20160706092908-05df47b4b6e4 06 Jul 2016
- v0.0.0-20160609152920-8e2d33a74593 09 Jun 2016
- v0.0.0-20160608131317-b4779a049de4 08 Jun 2016
- v0.0.0-20160505140742-a2fe1dc89cbb 05 May 2016
- v0.0.0-20160328213806-6c390a0e7327 28 Mar 2016
- v0.0.0-20160327232534-04609ab6da14 27 Mar 2016
- v0.0.0-20160327225848-0be4e4cef857 27 Mar 2016
All 46 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/mwitkow/go-proto-validators
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 github.com/mwitkow/go-proto-validators
Is github.com/mwitkow/go-proto-validators safe to use?
Vulert has no vulnerabilities on record for github.com/mwitkow/go-proto-validators 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/mwitkow/go-proto-validators's Vulert package health score?
Vulert scores github.com/mwitkow/go-proto-validators 55/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/mwitkow/go-proto-validators affected?
No. v0.3.2, 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/mwitkow/go-proto-validators should I use?
v0.3.2 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/mwitkow/go-proto-validators have?
0 vulnerabilities are recorded for github.com/mwitkow/go-proto-validators 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/mwitkow/go-proto-validators vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/mwitkow/go-proto-validators 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/mwitkow/go-proto-validators 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/mwitkow/go-proto-validators for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/mwitkow/go-proto-validators version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.