Vulnerability Database · Go · Package report
go.uber.org/ratelimit: vulnerability history, versions and safety
go.uber.org/ratelimit 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/ratelimit v0.3.1 i
Updated on 23 Oct 2026
Good news: v0.3.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Key ecosystem project
- Community Quiet
What to do: Stay on v0.3.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.3.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.3.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 4,723 i
- OpenSSF scorecard 3/10 i
- Last release 31 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/ratelimit, 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-20240430142451-3e5300c88680 30 Apr 2024
- v0.3.2-0.20240430142451-3e5300c88680 30 Apr 2024
- v0.0.0-20240304180526-61eed72d6bde 04 Mar 2024
- v0.3.1 04 Mar 2024
- v0.0.0-20230709053649-60908a3375ab 09 Jul 2023
- v0.3.1-0.20230709053649-60908a3375ab 09 Jul 2023
- v0.3.1-0.20230709043752-021eef1cf0e5 09 Jul 2023
- v0.3.0 09 Jul 2023
- v0.2.1-0.20221031031303-a12885fa6127 31 Oct 2022
- v0.0.0-20220713224938-b62b799bc9a5 13 Jul 2022
- v0.2.1-0.20220713224938-b62b799bc9a5 13 Jul 2022
- v0.2.1-0.20220710202656-af246a435e0f 10 Jul 2022
- v0.2.1-0.20220707033915-29ac3a290635 07 Jul 2022
- v0.2.1-0.20220702055956-783ade27bec6 02 Jul 2022
- v0.2.1-0.20220627221815-029273db374a 27 Jun 2022
- v0.2.1-0.20220609182557-8b3fccfbf238 09 Jun 2022
- v0.2.1-0.20220607215951-bd00da1f211d 07 Jun 2022
- v0.2.1-0.20220607213809-f04376ca0332 07 Jun 2022
- v0.2.1-0.20220606020930-bca0419e3ebf 06 Jun 2022
- v0.2.1-0.20220605221143-0fa90d22d426 05 Jun 2022
- v0.2.1-0.20220502165051-979a121132b8 02 May 2022
- v0.2.1-0.20220331025036-bf0eb9e5d634 31 Mar 2022
- v0.2.1-0.20220331022739-35504131fd8b 31 Mar 2022
- v0.2.1-0.20210307183452-20146b0c903a 07 Mar 2021
- v0.1.1-0.20210303021251-eec0063269d8 03 Mar 2021
- v0.2.0 03 Mar 2021
- v0.1.1-0.20210301150842-baf1224ab596 01 Mar 2021
- v0.1.1-0.20210225195441-7e71567d50ac 25 Feb 2021
- v0.0.0-20210125012240-296e9dcf0255 25 Jan 2021
- v0.1.1-0.20210125012240-296e9dcf0255 25 Jan 2021
- v0.1.1-0.20210119022550-688a9ec22fc1 19 Jan 2021
- v0.1.1-0.20210108031045-cc580bda3c6f 08 Jan 2021
- v0.1.1-0.20210103163905-4fc173c9d3c4 03 Jan 2021
- v0.1.1-0.20201228204745-5ab983fba9cf 28 Dec 2020
- v0.1.1-0.20201214145306-8cc6834f4d70 14 Dec 2020
- v0.1.1-0.20201210035141-bc6c3120884d 10 Dec 2020
- v0.1.1-0.20201207175807-12349e5e5235 07 Dec 2020
- v0.1.1-0.20201110185707-e86515f0dda9 10 Nov 2020
- v0.1.1-0.20201026193949-a7b5fef1e7d7 26 Oct 2020
- v0.1.1-0.20201008001144-40c185c5f857 08 Oct 2020
- v0.1.1-0.20200922212200-2cc0b02b8bda 22 Sep 2020
- v0.1.1-0.20200914212404-d55a8b2b03f1 14 Sep 2020
- v0.1.1-0.20191205214636-7895686c0825 05 Dec 2019
- v0.0.0-20191205185619-ecb970a6a3b3 05 Dec 2019
- v0.1.1-0.20191205185619-ecb970a6a3b3 05 Dec 2019
- v0.1.0 29 Jul 2019
- v0.0.0-20180316092928-c15da0234277 16 Mar 2018
- v0.0.0-20161026005643-d15fa2e2a63d 26 Oct 2016
All 48 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 go.uber.org/ratelimit
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/ratelimit
Is go.uber.org/ratelimit safe to use?
Vulert has no vulnerabilities on record for go.uber.org/ratelimit 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/ratelimit's Vulert package health score?
Vulert scores go.uber.org/ratelimit 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 go.uber.org/ratelimit affected?
No. v0.3.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/ratelimit should I use?
v0.3.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/ratelimit have?
0 vulnerabilities are recorded for go.uber.org/ratelimit 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/ratelimit vulnerabilities disclosed?
0 vulnerabilities were recorded for go.uber.org/ratelimit 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/ratelimit 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/ratelimit for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the go.uber.org/ratelimit version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.