Vulnerability Database · Go · Package report
github.com/avast/retry-go/v4: vulnerability history, versions and safety
github.com/avast/retry-go/v4 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/v4 v4.7.0 i
Updated on 23 Oct 2026
Good news: v4.7.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Key ecosystem project
- Community Quiet
What to do: Stay on v4.7.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v4.7.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v4.7.0 — 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 12 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/v4, 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.
- v4.7.1-0.20251031135138-b41ba704799c 31 Oct 2025
- v4.7.1-0.20251015070326-1f760099a796 15 Oct 2025
- v4.7.0 14 Oct 2025
- v4.0.0-20250321095328-cbf4dbfb37a5 21 Mar 2025
- v4.6.2-0.20250321095328-cbf4dbfb37a5 21 Mar 2025
- v4.6.1 24 Feb 2025
- v4.6.1-0.20250222100116-8d7cef7bde8a 22 Feb 2025
- v4.6.1-0.20250221185055-79a35c406f45 21 Feb 2025
- v4.6.1-0.20240418080110-01d7e0007ca2 18 Apr 2024
- v4.6.0 18 Apr 2024
- v4.5.1 14 Nov 2023
- v4.5.1-0.20231114095315-64083c1a1ed7 14 Nov 2023
- v4.5.1-0.20231114000602-6d7679da9c22 14 Nov 2023
- v4.5.1-0.20231012114724-a9809a7cb753 12 Oct 2023
- v4.5.1-0.20230828070808-abb9e3aafb34 28 Aug 2023
- v4.5.1-0.20230827022601-f570e772db9c 27 Aug 2023
- v4.5.1-0.20230814121449-7172c58f4140 14 Aug 2023
- v4.5.1-0.20230812132324-c51342aebf3c 12 Aug 2023
- v4.4.1-0.20230807071046-ff662bda00ed 07 Aug 2023
- v4.5.0 07 Aug 2023
- v4.3.5-0.20230804165516-fdadb7c575e3 04 Aug 2023
- v4.4.0 04 Aug 2023
- v4.3.5-0.20230803190302-7855000d8736 03 Aug 2023
- v4.3.4-0.20230422194809-377d1c394549 22 Apr 2023
- v4.3.4 21 Apr 2023
- v4.3.4-0.20230421081800-a9a7017a966d 21 Apr 2023
- v4.3.4-0.20230212222740-f2a78f266334 12 Feb 2023
- v4.3.3 08 Feb 2023
- v4.3.3-0.20230208091923-0407c196c204 08 Feb 2023
- v4.3.3-0.20230202183933-f5406120a2f1 02 Feb 2023
- v4.3.2 03 Jan 2023
- v4.3.1 15 Nov 2022
- v4.3.1-0.20221115101254-affbf8f1c615 15 Nov 2022
- v4.3.1-0.20221024152559-f0085d265928 24 Oct 2022
- v4.3.0 19 Oct 2022
- v4.2.0 19 Oct 2022
- v4.0.5-0.20221017145908-1b8d49e1eab2 17 Oct 2022
- v4.0.5-0.20221004070709-40b68b304421 04 Oct 2022
- v4.1.0 10 Jun 2022
- v4.0.5-0.20220610114546-2616d604291f 10 Jun 2022
- v4.0.5 18 May 2022
- v4.0.5-0.20220518135145-36a8ffcf6b08 18 May 2022
- v4.0.4 11 Apr 2022
- v4.0.3 31 Jan 2022
- v4.0.2 11 Dec 2021
- v4.0.1 18 Nov 2021
- v4.0.1-0.20211116141156-5b1a0aa685ea 16 Nov 2021
- v4.0.1-0.20211108102850-3e8006a03651 08 Nov 2021
- v4.0.0 08 Nov 2021
All 49 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/v4
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/v4
Is github.com/avast/retry-go/v4 safe to use?
Vulert has no vulnerabilities on record for github.com/avast/retry-go/v4 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/v4's Vulert package health score?
Vulert scores github.com/avast/retry-go/v4 77/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 github.com/avast/retry-go/v4 affected?
No. v4.7.0, 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/v4 should I use?
v4.7.0 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/v4 have?
0 vulnerabilities are recorded for github.com/avast/retry-go/v4 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/v4 vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/avast/retry-go/v4 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/v4 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/v4 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/v4 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.