Vulnerability Database · Go · Package report
github.com/Rican7/retry: vulnerability history, versions and safety
github.com/Rican7/retry 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/Rican7/retry 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 Unmaintained
- Popularity Niche
- 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 479 i
- OpenSSF scorecard 2/10 i
- Last release 62 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/Rican7/retry, 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-20230214204936-7b112df374c6 14 Feb 2023
- v0.3.2-0.20230214204936-7b112df374c6 14 Feb 2023
- v0.3.2-0.20230214204621-001900d97a9d 14 Feb 2023
- v0.3.2-0.20210831003737-4377ba7c86c2 31 Aug 2021
- v0.3.1 12 Aug 2021
- v0.3.1-0.20210812002037-3673af575c10 12 Aug 2021
- v0.3.0 01 Aug 2021
- v0.2.1-0.20210801013845-14765b872058 01 Aug 2021
- v0.2.1-0.20210728082828-b3e62f24fefd 28 Jul 2021
- v0.2.1-0.20210728082125-029cc633165d 28 Jul 2021
- v0.2.1-0.20210727072130-7efc7287b3e9 27 Jul 2021
- v0.2.1-0.20210727071503-adf9f0e808ab 27 Jul 2021
- v0.2.0 27 Jul 2021
- v0.0.0-20160712041035-272ad122d6e5 12 Jul 2016
- v0.1.1-0.20160712041035-272ad122d6e5 12 Jul 2016
- v0.1.1-0.20160712025254-e7232b1f78fb 12 Jul 2016
- v0.1.0 11 Jul 2016
- v0.0.0-20160625013056-d4321d9bb0bf 25 Jun 2016
All 18 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/Rican7/retry
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/Rican7/retry
Is github.com/Rican7/retry safe to use?
Vulert has no vulnerabilities on record for github.com/Rican7/retry 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/Rican7/retry's Vulert package health score?
Vulert scores github.com/Rican7/retry 50/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/Rican7/retry 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 github.com/Rican7/retry 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 github.com/Rican7/retry have?
0 vulnerabilities are recorded for github.com/Rican7/retry 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/Rican7/retry vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/Rican7/retry 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/Rican7/retry 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/Rican7/retry for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/Rican7/retry version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.