Vulnerability Database · Go · Package report
go.uber.org/config: vulnerability history, versions and safety
go.uber.org/config 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 go.uber.org/config v1.4.1 i
Updated on 23 Oct 2026
Good news: v1.4.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
What to do: Stay on v1.4.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.4.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.4.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 479 i
- OpenSSF scorecard 3/10 i
- Last release 5 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 go.uber.org/config, 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.
- v1.4.1 12 May 2026
- v1.4.1-0.20240122203422-a067eb1464b5 22 Jan 2024
- v1.4.1-0.20231026191756-3e6a980c2c65 26 Oct 2023
- v1.4.1-0.20230223181005-4a896bb4754b 23 Feb 2023
- v1.4.1-0.20220927162202-8c66ea44617a 27 Sep 2022
- v0.0.0-20220316003856-f57942f2e5c8 16 Mar 2022
- v1.4.1-0.20220316003856-f57942f2e5c8 16 Mar 2022
- v1.4.1-0.20220315213858-02b5670bb414 15 Mar 2022
- v1.4.1-0.20210525225937-1ab480fe347f 25 May 2021
- v1.4.1-0.20210525190805-4758647a8225 25 May 2021
- v1.4.1-0.20210517221301-efa332a7e2d2 17 May 2021
- v1.4.1-0.20200415164933-7eebe84240ad 15 Apr 2020
- v1.4.1-0.20200415041401-6621e2d59bb4 15 Apr 2020
- v1.4.1-0.20191120195739-0036d92e30bd 20 Nov 2019
- v0.0.0-20191120195638-c917157c9ba9 20 Nov 2019
- v1.4.0 20 Nov 2019
- v0.0.0-20190430173543-773b5421bfe9 30 Apr 2019
- v1.3.2-0.20190430173543-773b5421bfe9 30 Apr 2019
- v1.3.1 22 Oct 2018
- v1.3.0 29 Aug 2018
- v1.2.2 12 Jul 2018
- v1.2.1 06 Jul 2018
- v1.2.0 03 Jul 2018
- v0.0.0-20180620220459-46dea54a68b3 20 Jun 2018
- v1.1.1-0.20180620220459-46dea54a68b3 20 Jun 2018
- v1.1.0 28 Sep 2017
- v1.0.2 17 Aug 2017
- v1.0.1 04 Aug 2017
- v1.0.0 31 Jul 2017
- v1.0.0-rc1 26 Jun 2017
- v0.1.0 12 Jun 2017
All 31 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 go.uber.org/config
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 go.uber.org/config
Is go.uber.org/config safe to use?
Vulert has no vulnerabilities on record for go.uber.org/config 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 go.uber.org/config's Vulert package health score?
Vulert scores go.uber.org/config 70/100, which reads as in good shape. 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 go.uber.org/config affected?
No. v1.4.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 go.uber.org/config should I use?
v1.4.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 go.uber.org/config have?
0 vulnerabilities are recorded for go.uber.org/config 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 go.uber.org/config vulnerabilities disclosed?
0 vulnerabilities were recorded for go.uber.org/config 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 go.uber.org/config 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 go.uber.org/config for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the go.uber.org/config version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.