Vulnerability Database · Go · Package report

github.com/eapache/go-resiliency: vulnerability history, versions and safety

github.com/eapache/go-resiliency 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/eapache/go-resiliency v1.7.0 i

Updated on 23 Oct 2026

Good news: v1.7.0, the version you would install today, has no known vulnerabilities.

Package health score 66/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release v1.7.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2,369 i
  • OpenSSF scorecard 2/10 i
  • Last release 27 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/eapache/go-resiliency, 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.0.0-20250223201106-39c0aa4a7ec8 23 Feb 2025 none MIT — Details →
v1.7.1-0.20250223201106-39c0aa4a7ec8 23 Feb 2025 none MIT — Details →
v1.7.1-0.20240918192435-bc8cfd2492ce 18 Sep 2024 none MIT — Details →
v1.6.1-0.20240719185318-ad3d1cf2b1be 19 Jul 2024 none MIT — Details →
v1.7.0 19 Jul 2024 none MIT — Details →
v1.6.1-0.20240719184742-96d183b7dd94 19 Jul 2024 none MIT — Details →
v1.6.1-0.20240718160402-029d178001d1 18 Jul 2024 none MIT — Details →
v1.6.1-0.20240507131401-2c8fcf4fb92b 07 May 2024 none MIT — Details →
v1.6.1-0.20240221024907-6a6d489242da 21 Feb 2024 none MIT — Details →
v1.5.1-0.20240219161023-98401f26ee95 19 Feb 2024 none MIT — Details →
v1.6.0 19 Feb 2024 none MIT — Details →
v1.5.1-0.20240219154930-18a61733e60e 19 Feb 2024 none MIT — Details →
v1.5.1-0.20240114171747-2a81223d6517 14 Jan 2024 none MIT — Details →
v1.5.1-0.20240113163650-808c606f6104 13 Jan 2024 none MIT — Details →
v1.5.1-0.20240113163609-18dde48c600f 13 Jan 2024 none MIT — Details →
v1.4.1-0.20231214200154-b912f08afda8 14 Dec 2023 none MIT — Details →
v1.5.0 14 Dec 2023 none MIT — Details →
v1.4.1-0.20231213204100-27a8f90d0b74 13 Dec 2023 none MIT — Details →
v1.4.1-0.20231211102919-1d4a97f7bea2 11 Dec 2023 none MIT — Details →
v0.0.0-20231204181734-fdb9523214d0 04 Dec 2023 none MIT — Details →
v1.4.1-0.20231204181734-fdb9523214d0 04 Dec 2023 none MIT — Details →
v1.3.1-0.20230814210312-1bc136c77065 14 Aug 2023 none MIT — Details →
v1.4.0 14 Aug 2023 none MIT — Details →
v1.3.1-0.20230809162906-7756df1a471e 09 Aug 2023 none MIT — Details →
v1.3.1-0.20230202171514-83b926b9feca 02 Feb 2023 none MIT — Details →
v1.3.1-0.20230202160147-2e37f4ce57c4 02 Feb 2023 none MIT — Details →
v1.3.0 28 Jun 2022 none MIT — Details →
v1.2.1-0.20220628005640-03aceede925d 28 Jun 2022 none MIT — Details →
v1.2.1-0.20210917104313-1db5bca020fe 17 Sep 2021 none MIT — Details →
v1.2.1-0.20210714134625-a5f7c76c0c4f 14 Jul 2021 none MIT — Details →
v0.0.0-20190716143035-b98ce2825f72 16 Jul 2019 none MIT — Details →
v1.2.1-0.20190716143035-b98ce2825f72 16 Jul 2019 none MIT — Details →
v1.2.1-0.20190715182333-eadf0b025980 15 Jul 2019 none MIT — Details →
v0.0.0-20190614154724-5efd2ed019fd 14 Jun 2019 none MIT — Details →
v1.2.0 14 Jun 2019 none MIT — Details →
v0.0.0-20190208162553-842e16ec2c98 08 Feb 2019 none MIT — Details →
v1.1.1-0.20190208162553-842e16ec2c98 08 Feb 2019 none MIT — Details →
v1.1.1-0.20190208133023-5a6c539a7111 08 Feb 2019 none MIT — Details →
v1.1.1-0.20190207104016-0e5aea613d17 07 Feb 2019 none MIT — Details →
v0.0.0-20181214162408-487be0453c7b 14 Dec 2018 none MIT — Details →
v1.1.1-0.20181214162408-487be0453c7b 14 Dec 2018 none MIT — Details →
v1.1.1-0.20181214161851-2c68be121cc3 14 Dec 2018 none MIT — Details →
v0.0.0-20180326132423-ea41b0fad310 26 Mar 2018 none MIT — Details →
v1.1.0 26 Mar 2018 none MIT — Details →
v0.0.0-20180101203313-ef9aaa7ea8bd 01 Jan 2018 none MIT — Details →
v1.0.1-0.20180101203313-ef9aaa7ea8bd 01 Jan 2018 none MIT — Details →
v1.0.1-0.20180101202736-0dd30b754aaf 01 Jan 2018 none MIT — Details →
v0.0.0-20170607163615-b1fe83b5b03f 07 Jun 2017 none MIT — Details →
v1.0.1-0.20170607163615-b1fe83b5b03f 07 Jun 2017 none MIT — Details →
v1.0.1-0.20170607144650-989f237b04ac 07 Jun 2017 none MIT — Details →
v0.0.0-20160104191539-b86b1ec0dd42 04 Jan 2016 none MIT — Details →
v1.0.1-0.20160104191539-b86b1ec0dd42 04 Jan 2016 none MIT — Details →
v0.0.0-20151006145146-f341fb4dca45 06 Oct 2015 none MIT — Details →
v1.0.1-0.20151006145146-f341fb4dca45 06 Oct 2015 none MIT — Details →
v1.0.1-0.20151006144648-be546bcf2919 06 Oct 2015 none MIT — Details →
v0.0.0-20150416121643-ed0319b32e66 16 Apr 2015 none MIT — Details →
v1.0.1-0.20150416121643-ed0319b32e66 16 Apr 2015 none MIT — Details →
v0.0.0-20150213202315-6800482f2c81 13 Feb 2015 none MIT — Details →
v1.0.0 13 Feb 2015 none MIT — Details →
v0.0.0-20150123020357-5b8ad6c0f610 23 Jan 2015 none MIT — Details →
v0.0.0-20150123020248-5178b4174a3d 23 Jan 2015 none MIT — Details →
v0.0.0-20150121220912-0fdc44480871 21 Jan 2015 none MIT — Details →
v0.0.0-20141223211111-779a811c89f2 23 Dec 2014 none MIT — Details →
v0.0.0-20141222191337-1a4790d272f9 22 Dec 2014 none MIT — Details →
v0.0.0-20141222190818-a5cb3f2b7dae 22 Dec 2014 none MIT — Details →
v0.0.0-20141211153822-ba73ce34de8e 11 Dec 2014 none MIT — Details →
v0.0.0-20141210160750-8947dd8d6a40 10 Dec 2014 none MIT — Details →
v0.0.0-20141205150930-164d336eab65 05 Dec 2014 none MIT — Details →
v0.0.0-20141203202901-4d1b054cf041 03 Dec 2014 none MIT — Details →
v0.0.0-20141129133332-008c74ab45c7 29 Nov 2014 none MIT — Details →
v0.0.0-20141129045514-4dc187abf140 29 Nov 2014 none MIT — Details →

All 71 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/eapache/go-resiliency

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/eapache/go-resiliency

Is github.com/eapache/go-resiliency safe to use?

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

Vulert scores github.com/eapache/go-resiliency 66/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/eapache/go-resiliency affected?

No. v1.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/eapache/go-resiliency should I use?

v1.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/eapache/go-resiliency have?

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

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

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/eapache/go-resiliency version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.