Vulnerability Database · Go · Package report

github.com/sethvargo/go-retry: vulnerability history, versions and safety

github.com/sethvargo/go-retry is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/sethvargo/go-retry v0.5.0 i

Updated on 23 Oct 2026

Good news: v0.5.0, the version you would install today, has no known vulnerabilities.

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

What to do: Stay on v0.5.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.5.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v0.5.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 722 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence Apache-2.0 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/sethvargo/go-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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.5.0 05 Oct 2026 none Apache-2.0 — Details →
v0.4.1-0.20260904142243-f6b3e1a9f1c5 04 Sep 2026 none Apache-2.0 — Details →
v0.4.0 17 Jul 2026 none Apache-2.0 — Details →
v0.3.1-0.20260717175525-00248028a1b1 17 Jul 2026 none Apache-2.0 — Details →
v0.0.0-20260122033141-a324c6800a61 22 Jan 2026 none Apache-2.0 — Details →
v0.3.1-0.20260122033141-a324c6800a61 22 Jan 2026 none Apache-2.0 — Details →
v0.0.0-20251028204102-05bfdd60879e 28 Oct 2025 none Apache-2.0 — Details →
v0.3.1-0.20251028204102-05bfdd60879e 28 Oct 2025 none Apache-2.0 — Details →
v0.2.5-0.20240730211104-9bf6450b891a 30 Jul 2024 none Apache-2.0 — Details →
v0.3.0 30 Jul 2024 none Apache-2.0 — Details →
v0.0.0-20230315170441-a99f7cdbe5d1 15 Mar 2023 none Apache-2.0 — Details →
v0.2.5-0.20230315170441-a99f7cdbe5d1 15 Mar 2023 none Apache-2.0 — Details →
v0.2.5-0.20221231221458-234ac59736bc 31 Dec 2022 none Apache-2.0 — Details →
v0.2.4 14 Dec 2022 none Apache-2.0 — Details →
v0.0.0-20220210193137-009eed153ec9 10 Feb 2022 none Apache-2.0 — Details →
v0.2.3 10 Feb 2022 none Apache-2.0 — Details →
v0.2.3-0.20220205155602-7a0bb9fc5c81 05 Feb 2022 none Apache-2.0 — Details →
v0.2.3-0.20220115151641-f691e5cece11 15 Jan 2022 none Apache-2.0 — Details →
v0.2.2 08 Jan 2022 none Apache-2.0 — Details →
v0.2.2-0.20220104142455-e6dbee7990f9 04 Jan 2022 none Apache-2.0 — Details →
v0.2.1 04 Jan 2022 none Apache-2.0 — Details →
v0.1.1-0.20220103210320-e436cb14c0f0 03 Jan 2022 none Apache-2.0 — Details →
v0.1.1-0.20220103202947-2ee2801fc803 03 Jan 2022 none Apache-2.0 — Details →
v0.2.0 03 Jan 2022 none Apache-2.0 — Details →
v0.1.1-0.20211202144925-80daa4ebfa8b 02 Dec 2021 none Apache-2.0 — Details →
v0.1.1-0.20210407011123-eb868fa054ca 07 Apr 2021 none Apache-2.0 — Details →
v0.1.1-0.20200930180057-51bca52e94d3 30 Sep 2020 none Apache-2.0 — Details →
v0.0.0-20200703220808-e83b4a86bf8f 03 Jul 2020 none Apache-2.0 — Details →
v0.1.0 03 Jul 2020 none Apache-2.0 — Details →
v0.0.0-20200703211810-8390cace92d3 03 Jul 2020 none Apache-2.0 — Details →
v0.0.0-20200703183017-78d82d8eeba7 03 Jul 2020 none Apache-2.0 — Details →

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.

03 Vulnerabilities

Recorded vulnerabilities for github.com/sethvargo/go-retry

No vulnerability write-ups match this view

Search all 0 in the database →

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/sethvargo/go-retry

Is github.com/sethvargo/go-retry safe to use?

Vulert has no vulnerabilities on record for github.com/sethvargo/go-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/sethvargo/go-retry's Vulert package health score?

Vulert scores github.com/sethvargo/go-retry 80/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/sethvargo/go-retry affected?

No. v0.5.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/sethvargo/go-retry should I use?

v0.5.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/sethvargo/go-retry have?

0 vulnerabilities are recorded for github.com/sethvargo/go-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/sethvargo/go-retry vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/sethvargo/go-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/sethvargo/go-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/sethvargo/go-retry for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/sethvargo/go-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.