Vulnerability Database · Go · Package report
github.com/avast/retry-go: vulnerability history, versions and safety
github.com/avast/retry-go 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/avast/retry-go v3.0.0+incompatible i
Updated on 23 Oct 2026
Good news: v3.0.0+incompatible, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Key ecosystem project
- Community Quiet
What to do: Stay on v3.0.0+incompatible or newer. This can change: a vulnerability disclosed tomorrow can affect v3.0.0+incompatible too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v3.0.0+incompatible — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 2,965 i
- OpenSSF scorecard 2/10 i
- Last release 72 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 github.com/avast/retry-go, 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-20210601081617-d8dc92da5170 01 Jun 2021
- v0.0.0-20210513123357-b6d0474d5612 13 May 2021
- v0.0.0-20210512094549-709661014a04 12 May 2021
- v3.0.1-0.20201014082023-106564001754+incompatible 14 Oct 2020
- v3.0.0+incompatible 13 Oct 2020
- v2.7.1-0.20201012072612-b009386d45b1+incompatible 12 Oct 2020
- v2.7.1-0.20201010183512-7062aab0b084+incompatible 10 Oct 2020
- v2.7.1-0.20201009155703-76de2fdaf171+incompatible 09 Oct 2020
- v0.0.0-20201009104749-d5890ce880dc 09 Oct 2020
- v2.7.0+incompatible 09 Oct 2020
- v2.6.2-0.20201009103013-7b7365c9f616+incompatible 09 Oct 2020
- v2.6.2-0.20201009074023-1472dd7da3ea+incompatible 09 Oct 2020
- v2.6.1+incompatible 17 Sep 2020
- v2.6.1-0.20200916232822-c0babf77ced9+incompatible 16 Sep 2020
- v2.6.0+incompatible 25 Feb 2020
- v2.4.4-0.20200218155735-5ea276bca4ec+incompatible 18 Feb 2020
- v2.5.0+incompatible 28 Jan 2020
- v0.0.0-20200128203150-88a508dc7f6d 28 Jan 2020
- v2.4.4-0.20200128203150-88a508dc7f6d+incompatible 28 Jan 2020
- v2.4.4-0.20200109205857-b05e677998a8+incompatible 09 Jan 2020
- v0.0.0-20191127195934-f9a5f3752008 27 Nov 2019
- v2.4.3+incompatible 27 Nov 2019
- v2.4.3-0.20191126123141-2c27f348908b+incompatible 26 Nov 2019
- v2.4.2+incompatible 23 Oct 2019
- v2.4.2-0.20191006194229-639c9f1948ff+incompatible 06 Oct 2019
- v2.4.1+incompatible 13 Jul 2019
- v2.4.0+incompatible 13 Jul 2019
- v2.3.1-0.20190712165500-35826417300d+incompatible 12 Jul 2019
- v0.0.0-20190712165355-9007ab3d45fd 12 Jul 2019
- v2.3.1-0.20190712165355-9007ab3d45fd+incompatible 12 Jul 2019
- v2.3.0+incompatible 29 Apr 2019
- v2.2.1-0.20190322164118-4181b4d40bc2+incompatible 22 Mar 2019
- v0.0.0-20190122112038-08d411bf8302 22 Jan 2019
- v2.2.0+incompatible 22 Jan 2019
- v2.1.1-0.20190119143510-13bfda1721cf+incompatible 19 Jan 2019
- v2.1.1-0.20190118171411-16037201f734+incompatible 18 Jan 2019
- v2.1.0+incompatible 11 Jan 2019
- v2.0.0+incompatible 03 Dec 2018
- v0.0.0-20181203110558-4ffe19f1ab61 03 Dec 2018
- v0.0.0-20180502193734-611bd93c6d74 02 May 2018
- v0.0.0-20180429091953-d640a3b29a0e 29 Apr 2018
- v0.0.0-20180319101611-5469272a8171 19 Mar 2018
- v0.0.0-20180319085322-0a80beffee5d 19 Mar 2018
- v0.0.0-20180308123348-7411cd0c72f2 08 Mar 2018
- v0.0.0-20171124144729-5e4735226698 24 Nov 2017
- v0.0.0-20171110130359-4ac64a5c749f 10 Nov 2017
- v0.0.0-20170927120039-370b1f85123c 27 Sep 2017
- v0.0.0-20170926103459-73ec6370158a 26 Sep 2017
- v0.0.0-20170728075039-8ea1249ed2dd 28 Jul 2017
- v0.0.0-20170724153528-0aca03e2b3e2 24 Jul 2017
All 50 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/avast/retry-go
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/avast/retry-go
Is github.com/avast/retry-go safe to use?
Vulert has no vulnerabilities on record for github.com/avast/retry-go 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/avast/retry-go's Vulert package health score?
Vulert scores github.com/avast/retry-go 60/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/avast/retry-go affected?
No. v3.0.0+incompatible, 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/avast/retry-go should I use?
v3.0.0+incompatible 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/avast/retry-go have?
0 vulnerabilities are recorded for github.com/avast/retry-go 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/avast/retry-go vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/avast/retry-go 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/avast/retry-go 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/avast/retry-go for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/avast/retry-go version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.