VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/afex/hystrix-go: vulnerability history, versions and safety

github.com/afex/hystrix-go 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.

See all github.com/afex/hystrix-go vulnerabilities

Vulert verdict on github.com/afex/hystrix-go v0.0.0-20180502004556-fa1af6a1f4f5 i

Updated on 23 Oct 2026

Good news: v0.0.0-20180502004556-fa1af6a1f4f5, the version you would install today, has no known vulnerabilities.

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

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

  • Current release v0.0.0-20180502004556-fa1af6a1f4f5 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 4,398 i
  • OpenSSF scorecard 2/10 i
  • Last release 101 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/afex/hystrix-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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.0.0-20180502004556-fa1af6a1f4f5 02 May 2018 none MIT — Details →
v0.0.0-20180502004021-0a5b8904268e 02 May 2018 none MIT — Details →
v0.0.0-20180502000930-b6b54cfdc037 02 May 2018 none MIT — Details →
v0.0.0-20180420204750-9edb73dffc6b 20 Apr 2018 none MIT — Details →
v0.0.0-20180406012432-f86abeeb9f72 06 Apr 2018 none MIT — Details →
v0.0.0-20180406011845-34d62d2895fe 06 Apr 2018 none MIT — Details →
v0.0.0-20180406005640-477cc32de045 06 Apr 2018 none MIT — Details →
v0.0.0-20180330202918-b8830e95af6f 30 Mar 2018 none MIT — Details →
v0.0.0-20180330001947-292230d8e389 30 Mar 2018 none MIT — Details →
v0.0.0-20180329224416-4847ceb883b5 29 Mar 2018 none MIT — Details →
v0.0.0-20180209233601-7259cb8853aa 09 Feb 2018 none MIT — Details →
v0.0.0-20180209013831-27fae8d30f1a 09 Feb 2018 none MIT — Details →
v0.0.0-20180208233740-6f2502b9e5a2 08 Feb 2018 none MIT — Details →
v0.0.0-20180123092206-4b693391b9af 23 Jan 2018 none MIT — Details →
v0.0.0-20180105191838-64c4571638b1 05 Jan 2018 none MIT — Details →
v0.0.0-20180105163203-ec92215247e7 05 Jan 2018 none MIT — Details →
v0.0.0-20170815234612-f118cd938f78 15 Aug 2017 none MIT — Details →
v0.0.0-20170815232938-2cfbe558257b 15 Aug 2017 none MIT — Details →
v0.0.0-20170815223210-038dd4b149f6 15 Aug 2017 none MIT — Details →
v0.0.0-20170814055546-18d99e3a00fa 14 Aug 2017 none MIT — Details →
v0.0.0-20170814054448-346dd5d85f75 14 Aug 2017 none MIT — Details →
v0.0.0-20170627102718-924f73cd1732 27 Jun 2017 none MIT — Details →
v0.0.0-20170627051330-19331b1b83d5 27 Jun 2017 none MIT — Details →
v0.0.0-20170626063210-88e906f09724 26 Jun 2017 none MIT — Details →
v0.0.0-20170625110802-662f1df1bf26 25 Jun 2017 none MIT — Details →
v0.0.0-20170228214108-47302d62213b 28 Feb 2017 none MIT — Details →
v0.0.0-20160916213518-f11eb004344a 16 Sep 2016 none MIT — Details →
v0.0.0-20160615205002-39520ddd07a9 15 Jun 2016 none MIT — Details →
v0.0.0-20160615004042-95a0c2ea98ed 15 Jun 2016 none MIT — Details →
v0.0.0-20160613233232-0e21c17f0d98 13 Jun 2016 none MIT — Details →
v0.0.0-20160613231947-7e0271c9b5fd 13 Jun 2016 none MIT — Details →
v0.0.0-20151022223553-4c323460954a 22 Oct 2015 none MIT — Details →
v0.0.0-20151022222158-0a27fa712695 22 Oct 2015 none MIT — Details →
v0.0.0-20151022211356-541f03cfcb61 22 Oct 2015 none MIT — Details →
v0.0.0-20150909034220-9351b724be39 09 Sep 2015 none MIT — Details →
v0.0.0-20150909003403-2ca3b53aac6f 09 Sep 2015 none MIT — Details →
v0.0.0-20150906213215-16f7c6ea2afb 06 Sep 2015 none MIT — Details →
v0.0.0-20150906001314-14dd7b6ba092 06 Sep 2015 none MIT — Details →
v0.0.0-20150821071006-fbe18f9a5a3b 21 Aug 2015 none MIT — Details →
v0.0.0-20150817183933-b6418c3e9b17 17 Aug 2015 none MIT — Details →
v0.0.0-20150814221601-5733f858500d 14 Aug 2015 none MIT — Details →
v0.0.0-20150814204637-15de48a75b1d 14 Aug 2015 none MIT — Details →
v0.0.0-20150814003113-4dae42a73bb1 14 Aug 2015 none MIT — Details →
v0.0.0-20150813000253-2f41336452be 13 Aug 2015 none MIT — Details →
v0.0.0-20150810224211-048338cfc691 10 Aug 2015 none MIT — Details →
v0.0.0-20150802205605-a9ec81eca474 02 Aug 2015 none MIT — Details →
v0.0.0-20150731232612-e098e75198b7 31 Jul 2015 none MIT — Details →
v0.0.0-20150730004314-09ce9126cf26 30 Jul 2015 none MIT — Details →
v0.0.0-20150729040106-249f5794977b 29 Jul 2015 none MIT — Details →
v0.0.0-20150728050202-93bb23780595 28 Jul 2015 none MIT — Details →
v0.0.0-20150724025043-7db92ce26adc 24 Jul 2015 none MIT — Details →
v0.0.0-20150716210401-f43ad79cae09 16 Jul 2015 none MIT — Details →
v0.0.0-20150708154804-6656046bf35d 08 Jul 2015 none MIT — Details →
v0.0.0-20150701221154-6c0ea844f7f6 01 Jul 2015 none MIT — Details →
v0.0.0-20150626221648-49a990ce72ca 26 Jun 2015 none MIT — Details →
v0.0.0-20150623234504-adcddc6d1888 23 Jun 2015 none MIT — Details →
v0.0.0-20150530234439-e3086300043a 30 May 2015 none MIT — Details →
v0.0.0-20150509075723-3b090d2e9935 09 May 2015 none MIT — Details →
v0.0.0-20150508035933-c59ab5d9004d 08 May 2015 none MIT — Details →
v0.0.0-20150501214335-e2951138c975 01 May 2015 none MIT — Details →
v0.0.0-20150422052216-23bcdd65fcfb 22 Apr 2015 none MIT — Details →
v0.0.0-20150417211521-91d1381f33f9 17 Apr 2015 none MIT — Details →
v0.0.0-20150416235408-1d1e67705f72 16 Apr 2015 none MIT — Details →
v0.0.0-20150416042451-6e9dbb131512 16 Apr 2015 none MIT — Details →
v0.0.0-20150414032142-50f8631de34a 14 Apr 2015 none MIT — Details →
v0.0.0-20150407022954-a5d33fe698dd 07 Apr 2015 none MIT — Details →
v0.0.0-20150401032314-2c1ca27ba53a 01 Apr 2015 none MIT — Details →
v0.0.0-20150324083815-98b0c4f6bf20 24 Mar 2015 none MIT — Details →
v0.0.0-20150303224524-c4d7077a32f2 03 Mar 2015 none MIT — Details →
v0.0.0-20150302235521-604a7f25af1d 02 Mar 2015 none MIT — Details →
v0.0.0-20150203232326-09d60b533d2b 03 Feb 2015 none MIT — Details →
v0.0.0-20150127065957-71c7af1ae77e 27 Jan 2015 none MIT — Details →
v0.0.0-20150117080432-042afefeb337 17 Jan 2015 none MIT — Details →
v0.0.0-20150117000019-5653c1622dda 17 Jan 2015 none MIT — Details →
v0.0.0-20150113215154-3cd1209e133a 13 Jan 2015 none MIT — Details →
v0.0.0-20141219224609-0076b44c8c8d 19 Dec 2014 none MIT — Details →
v0.0.0-20141219012148-09bf59ea920a 19 Dec 2014 none MIT — Details →
v0.0.0-20141218034218-28dc2179ebdb 18 Dec 2014 none MIT — Details →
v0.0.0-20141216030223-36bf4991403f 16 Dec 2014 none MIT — Details →
v0.0.0-20141202015156-a9681b36d8ab 02 Dec 2014 none MIT — Details →
v0.0.0-20141107114430-2b9c767f8172 07 Nov 2014 none MIT — Details →
v0.0.0-20141106100414-e3e3746bc8fb 06 Nov 2014 none MIT — Details →
v0.0.0-20140302204737-16aa87edc96f 02 Mar 2014 none MIT — Details →
v0.0.0-20140301091117-beafad759b4b 01 Mar 2014 none MIT — Details →
v0.0.0-20140211222753-6db3f8e4dced 11 Feb 2014 none MIT — Details →
v0.0.0-20140111201406-162d36bdfe4c 11 Jan 2014 none MIT — Details →
v0.0.0-20140105091827-6b0f6d4c7c3a 05 Jan 2014 none MIT — Details →
v0.0.0-20140101102811-ec82b23227b4 01 Jan 2014 none MIT — Details →
v0.0.0-20140101100915-f7508a7fd1e2 01 Jan 2014 none MIT — Details →
v0.0.0-20131227220150-461862232e16 27 Dec 2013 none MIT — Details →
v0.0.0-20131224210100-5b6820f288a9 24 Dec 2013 none MIT — Details →
v0.0.0-20131218093803-8ceed2648a19 18 Dec 2013 none MIT — Details →
v0.0.0-20131215090246-62a0d3ca5431 15 Dec 2013 none MIT — Details →
v0.0.0-20131215085124-05bde3e3cca4 15 Dec 2013 none MIT — Details →

All 94 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/afex/hystrix-go

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/afex/hystrix-go

Is github.com/afex/hystrix-go safe to use?

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

Vulert scores github.com/afex/hystrix-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/afex/hystrix-go affected?

No. v0.0.0-20180502004556-fa1af6a1f4f5, 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/afex/hystrix-go should I use?

v0.0.0-20180502004556-fa1af6a1f4f5 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/afex/hystrix-go have?

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

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

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