VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/throttled/throttled/v2: vulnerability history, versions and safety

github.com/throttled/throttled/v2 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/throttled/throttled/v2 vulnerabilities

Vulert verdict on github.com/throttled/throttled/v2 v2.15.0 i

Updated on 23 Oct 2026

Good news: v2.15.0, the version you would install today, has no known vulnerabilities.

Package health score 69/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

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

  • Current release v2.15.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,599 i
  • OpenSSF scorecard 2/10 i
  • Last release 14 months ago i
  • Licence BSD-3-Clause 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/throttled/throttled/v2, 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
v2.15.1-0.20260413131603-24e4d7715364 13 Apr 2026 none BSD-3-Clause — Details →
v2.15.1-0.20250828173236-d5ee505c72a4 28 Aug 2025 none BSD-3-Clause — Details →
v2.15.0 23 Aug 2025 none BSD-3-Clause — Details →
v2.14.0 23 Aug 2025 none BSD-3-Clause — Details →
v2.13.1-0.20250823004526-298ec2130fde 23 Aug 2025 none BSD-3-Clause — Details →
v2.13.0 23 Jan 2025 none BSD-3-Clause — Details →
v2.11.1-0.20230629173503-71af276faafa 29 Jun 2023 none BSD-3-Clause — Details →
v2.12.0 29 Jun 2023 none BSD-3-Clause — Details →
v2.11.1-0.20230629173317-5099566efcde 29 Jun 2023 none BSD-3-Clause — Details →
v2.11.0 06 Apr 2023 none BSD-3-Clause — Details →
v2.10.0 25 Mar 2023 none BSD-3-Clause — Details →
v2.9.2-0.20230325200751-0427dce15f04 25 Mar 2023 none BSD-3-Clause — Details →
v2.9.2-0.20230224023607-ec275dade393 24 Feb 2023 none BSD-3-Clause — Details →
v2.9.2-0.20230223062058-cd8043ecf5eb 23 Feb 2023 none BSD-3-Clause — Details →
v2.9.2-0.20220808150944-9d679626235d 08 Aug 2022 none BSD-3-Clause — Details →
v2.9.2-0.20220808150724-0b13f7936849 08 Aug 2022 none BSD-3-Clause — Details →
v2.9.2-0.20220529181952-2e83d97bffc2 29 May 2022 none BSD-3-Clause — Details →
v2.9.2-0.20220526223806-efccce976dd3 26 May 2022 none BSD-3-Clause — Details →
v2.7.2-0.20220216003254-eef0076db706 16 Feb 2022 none BSD-3-Clause — Details →
v2.9.1 16 Feb 2022 none BSD-3-Clause — Details →
v2.9.1-0.20220216003019-47399910777c 16 Feb 2022 none BSD-3-Clause — Details →
v2.6.1-0.20210717200414-c1d2c0097301 17 Jul 2021 none BSD-3-Clause — Details →
v2.9.0 17 Jul 2021 none BSD-3-Clause — Details →
v2.8.1-0.20210705085214-c47c008fd9ce 05 Jul 2021 none BSD-3-Clause — Details →
v2.8.0 12 Jun 2021 none BSD-3-Clause — Details →
v2.7.3-0.20210611232555-e08fbdec1e43 11 Jun 2021 none BSD-3-Clause — Details →
v2.7.2 18 May 2021 none BSD-3-Clause — Details →
v2.7.2-0.20210518231618-04334c7d6b95 18 May 2021 none BSD-3-Clause — Details →
v2.7.2-0.20210430154521-9224b4a8e1cb 30 Apr 2021 none BSD-3-Clause — Details →
v2.7.2-0.20210107054812-997638e242b4 07 Jan 2021 none BSD-3-Clause — Details →
v2.7.1 12 Nov 2020 none BSD-3-Clause — Details →
v2.7.1-0.20201111175116-4768ebde488e 11 Nov 2020 none BSD-3-Clause — Details →
v2.7.0 09 Oct 2020 none BSD-3-Clause — Details →
v2.6.1-0.20201009124507-1f3599207b17 09 Oct 2020 none BSD-3-Clause — Details →
v2.6.0 04 Aug 2020 none BSD-3-Clause — Details →
v2.5.1-0.20200804144821-07d3e89e30ce 04 Aug 2020 none BSD-3-Clause — Details →
v2.5.0 02 Aug 2020 none BSD-3-Clause — Details →

All 37 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/throttled/throttled/v2

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/throttled/throttled/v2

Is github.com/throttled/throttled/v2 safe to use?

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

Vulert scores github.com/throttled/throttled/v2 69/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/throttled/throttled/v2 affected?

No. v2.15.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/throttled/throttled/v2 should I use?

v2.15.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/throttled/throttled/v2 have?

0 vulnerabilities are recorded for github.com/throttled/throttled/v2 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/throttled/throttled/v2 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/throttled/throttled/v2 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/throttled/throttled/v2 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/throttled/throttled/v2 for upcoming vulnerabilities?

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