Vulnerability Database · Go · Package report
github.com/PaesslerAG/gval: vulnerability history, versions and safety
github.com/PaesslerAG/gval 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 github.com/PaesslerAG/gval v1.2.4 i
Updated on 23 Oct 2026
Good news: v1.2.4, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Widely used
- Community Quiet
What to do: Stay on v1.2.4 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.2.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.2.4 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 818 i
- OpenSSF scorecard 2/10 i
- Last release 22 months ago i
- Licence BSD-3-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/PaesslerAG/gval, 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-20260913070656-c622ea2f0e82 13 Sep 2026
- v1.2.5-0.20260913070656-c622ea2f0e82 13 Sep 2026
- v1.2.5-0.20260812073424-052b3b19436d 12 Aug 2026
- v1.2.5-0.20250804142123-a769652e8e42 04 Aug 2025
- v0.0.0-20241128111336-8faea0debb79 28 Nov 2024
- v1.2.4 28 Nov 2024
- v1.2.4-0.20241128111336-8faea0debb79 28 Nov 2024
- v1.2.3 18 Oct 2024
- v1.2.3-0.20241018111408-916246706be2 18 Oct 2024
- v1.2.3-0.20240523111506-121093f3c9a6 23 May 2024
- v1.2.3-0.20230303073635-cd026a3dee26 03 Mar 2023
- v1.2.3-0.20230206123858-d0a223b971ae 06 Feb 2023
- v1.2.2 06 Feb 2023
- v1.2.1 21 Sep 2022
- v1.2.0 18 May 2022
- v1.1.3-0.20211205135508-12d4df2a647a 05 Dec 2021
- v1.1.3-0.20211102102452-9d17f6740463 02 Nov 2021
- v1.1.2 21 Oct 2021
- v1.1.2-0.20211021203136-bfa8e95b8038 21 Oct 2021
- v0.0.0-20210603215850-2be8504728c9 03 Jun 2021
- v1.1.1 03 Jun 2021
- v1.1.1-0.20210603215850-2be8504728c9 03 Jun 2021
- v0.0.0-20210429131240-4f5f9c091d78 29 Apr 2021
- v1.1.1-0.20210429131240-4f5f9c091d78 29 Apr 2021
- v0.0.0-20210318134951-2271a5ad3968 18 Mar 2021
- v1.1.1-0.20210318134951-2271a5ad3968 18 Mar 2021
- v0.0.0-20201218133124-6ca878f8a063 18 Dec 2020
- v1.1.1-0.20201218133124-6ca878f8a063 18 Dec 2020
- v1.1.1-0.20201214170736-bd491efd3bf9 14 Dec 2020
- v1.1.1-0.20201115211348-c11e94ed6586 15 Nov 2020
- v1.1.1-0.20201105054200-485801dccbc5 05 Nov 2020
- v1.1.1-0.20201104175134-7847ed0c7671 04 Nov 2020
- v1.1.1-0.20200928185736-dbbd36716939 28 Sep 2020
- v1.1.0 08 Sep 2020
- v0.0.0-20190803062529-6fceb06ca162 03 Aug 2019
- v1.0.2-0.20190803062529-6fceb06ca162 03 Aug 2019
- v1.0.1 16 May 2019
- v1.0.0 16 May 2019
- v0.0.0-20190418102600-4f1cfd4aa412 18 Apr 2019
- v0.1.3-0.20190318081406-c0a6c7684e43 18 Mar 2019
- v0.1.2 13 Mar 2019
- v0.1.2-0.20190218163138-39dc85f08264 18 Feb 2019
- v0.1.2-0.20180925085313-d70448cce1b7 25 Sep 2018
- v0.1.1 18 Sep 2018
- v0.1.0 24 Oct 2017
- v0.0.0-20171012113103-e7b2bbc8abb7 12 Oct 2017
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/PaesslerAG/gval
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/PaesslerAG/gval
Is github.com/PaesslerAG/gval safe to use?
Vulert has no vulnerabilities on record for github.com/PaesslerAG/gval 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/PaesslerAG/gval's Vulert package health score?
Vulert scores github.com/PaesslerAG/gval 68/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/PaesslerAG/gval affected?
No. v1.2.4, 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/PaesslerAG/gval should I use?
v1.2.4 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/PaesslerAG/gval have?
0 vulnerabilities are recorded for github.com/PaesslerAG/gval 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/PaesslerAG/gval vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/PaesslerAG/gval 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/PaesslerAG/gval 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/PaesslerAG/gval for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/PaesslerAG/gval version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.