Vulnerability Database · Go · Package report
github.com/cenkalti/backoff: vulnerability history, versions and safety
github.com/cenkalti/backoff 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/cenkalti/backoff v2.2.1+incompatible i
Updated on 23 Oct 2026
Good news: v2.2.1+incompatible, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Key ecosystem project
- Community Quiet
What to do: Stay on v2.2.1+incompatible or newer. This can change: a vulnerability disclosed tomorrow can affect v2.2.1+incompatible too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v2.2.1+incompatible — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 4,086 i
- OpenSSF scorecard 3/10 i
- Last release 87 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/cenkalti/backoff, 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-20191212183906-671f609f1d9d 12 Dec 2019
- v1.1.1-0.20191212183906-671f609f1d9d 12 Dec 2019
- v0.0.0-20190717104821-5267b6dd4d26 17 Jul 2019
- v2.2.1+incompatible 17 Jul 2019
- v2.2.2-0.20190717104821-5267b6dd4d26+incompatible 17 Jul 2019
- v0.0.0-20190506075156-2146c9339422 06 May 2019
- v1.1.1-0.20190506075156-2146c9339422 06 May 2019
- v0.0.0-20190106105822-1e4cf3da5598 06 Jan 2019
- v1.0.1-0.20190106105822-1e4cf3da5598 06 Jan 2019
- v2.1.1+incompatible 06 Jan 2019
- v0.0.0-20181003080854-62661b46c409 03 Oct 2018
- v1.1.1-0.20181003080854-62661b46c409 03 Oct 2018
- v2.0.1-0.20181003080854-62661b46c409+incompatible 03 Oct 2018
- v2.1.0+incompatible 03 Oct 2018
- v0.0.0-20180921064520-adb73d5bf0d9 21 Sep 2018
- v2.0.1-0.20180921064520-adb73d5bf0d9+incompatible 21 Sep 2018
- v0.0.0-20180801153208-b7325b0f3f10 01 Aug 2018
- v1.1.1-0.20180801153208-b7325b0f3f10 01 Aug 2018
- v2.0.1-0.20180801153208-b7325b0f3f10+incompatible 01 Aug 2018
- v0.0.0-20180725110945-66e726b43552 25 Jul 2018
- v2.0.1-0.20180725110945-66e726b43552+incompatible 25 Jul 2018
- v0.0.0-20180723203840-c3d0f108be64 23 Jul 2018
- v2.0.1-0.20180723203840-c3d0f108be64+incompatible 23 Jul 2018
- v0.0.0-20180518090649-f756bc9a37f8 18 May 2018
- v1.1.1-0.20180518090649-f756bc9a37f8 18 May 2018
- v2.0.1-0.20180518090649-f756bc9a37f8+incompatible 18 May 2018
- v2.0.1-0.20180518085541-4f7ab5a597bd+incompatible 18 May 2018
- v0.0.0-20171224164212-2ea60e5f0944 24 Dec 2017
- v2.0.0+incompatible 24 Dec 2017
- v0.0.0-20171020064038-309aa717adbf 20 Oct 2017
- v1.1.1-0.20171020064038-309aa717adbf 20 Oct 2017
- v0.0.0-20170921171023-61ba96c4d100 21 Sep 2017
- v1.1.1-0.20170921171023-61ba96c4d100 21 Sep 2017
- v0.0.0-20170918082838-80e08cb804a3 18 Sep 2017
- v1.1.1-0.20170918082838-80e08cb804a3 18 Sep 2017
- v0.0.0-20170711220223-61153c768f31 11 Jul 2017
- v1.1.0 11 Jul 2017
- v1.0.1-0.20170708170325-8736fff6b3da 08 Jul 2017
- v1.0.1-0.20170705210519-1f265abe2f46 05 Jul 2017
- v0.0.0-20170329104900-5d150e7eec02 29 Mar 2017
- v1.0.1-0.20170329104900-5d150e7eec02 29 Mar 2017
- v0.0.0-20170309153948-3db60c813733 09 Mar 2017
- v1.0.1-0.20170309153948-3db60c813733 09 Mar 2017
- v1.0.1-0.20170309074744-8bd6a0cc881a 09 Mar 2017
- v0.0.0-20161020194410-b02f2bbce11d 20 Oct 2016
- v1.0.1-0.20161020194410-b02f2bbce11d 20 Oct 2016
- v0.0.0-20160904140958-8edc80b07f38 04 Sep 2016
- v1.0.1-0.20160904140958-8edc80b07f38 04 Sep 2016
- v1.0.1-0.20160904112009-03dc30e3986a 04 Sep 2016
- v0.0.0-20160610100912-cdf48bbc1eb7 10 Jun 2016
- v1.0.1-0.20160610100912-cdf48bbc1eb7 10 Jun 2016
- v0.0.0-20160526204934-a6030178a585 26 May 2016
- v1.0.1-0.20160526204934-a6030178a585 26 May 2016
- v1.0.1-0.20160526204209-5cbdd8fad5eb 26 May 2016
- v0.0.0-20160427170756-c29158af3181 27 Apr 2016
- v1.0.1-0.20160427170756-c29158af3181 27 Apr 2016
- v0.0.0-20160321131554-32cd0c5b3aef 21 Mar 2016
- v1.0.0 21 Mar 2016
- v0.0.0-20160320082725-a3a66cc95837 20 Mar 2016
- v0.0.0-20150814094333-4dc77674acea 14 Aug 2015
- v0.0.0-20150813121954-0b43d6bb3a2e 13 Aug 2015
- v0.0.0-20150522193654-6c45d6bc1e78 22 May 2015
- v0.0.0-20141124221459-9831e1e25c87 24 Nov 2014
- v0.0.0-20141124221138-7b004bb18e86 24 Nov 2014
- v0.0.0-20141021115448-6a458ae422d1 21 Oct 2014
- v0.0.0-20141015190045-9b3b0d8135f5 15 Oct 2014
- v0.0.0-20140921075531-c201004c081d 21 Sep 2014
- v0.0.0-20140917043324-d0aa33a32997 17 Sep 2014
- v0.0.0-20140914203719-8515d639f226 14 Sep 2014
- v0.0.0-20140908034806-5f3c2f1109dd 08 Sep 2014
- v0.0.0-20140905160450-3f9cf898b934 05 Sep 2014
- v0.0.0-20140902075524-055596b28b75 02 Sep 2014
- v0.0.0-20140829120218-2cccdbd43f62 29 Aug 2014
- v0.0.0-20140822162348-0337cbf9500d 22 Aug 2014
- v0.0.0-20140713073939-f402310eb716 13 Jul 2014
- v0.0.0-20140530155105-798ddbde3c10 30 May 2014
- v0.0.0-20140530115620-0f88078e5ff9 30 May 2014
- v0.0.0-20140527203857-b8c6496cfefb 27 May 2014
- v0.0.0-20140514145035-005a2dacc739 14 May 2014
- v0.0.0-20140227070837-0d5eecb72f25 27 Feb 2014
- v0.0.0-20140227070250-316fc0f4e270 27 Feb 2014
- v0.0.0-20140226044050-2d183d20cebb 26 Feb 2014
- v0.0.0-20140226000016-460939a79b45 26 Feb 2014
All 83 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/cenkalti/backoff
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/cenkalti/backoff
Is github.com/cenkalti/backoff safe to use?
Vulert has no vulnerabilities on record for github.com/cenkalti/backoff 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/cenkalti/backoff's Vulert package health score?
Vulert scores github.com/cenkalti/backoff 62/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/cenkalti/backoff affected?
No. v2.2.1+incompatible, 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/cenkalti/backoff should I use?
v2.2.1+incompatible 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/cenkalti/backoff have?
0 vulnerabilities are recorded for github.com/cenkalti/backoff 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/cenkalti/backoff vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/cenkalti/backoff 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/cenkalti/backoff 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/cenkalti/backoff for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/cenkalti/backoff version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.