VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

github.com/sethvargo/go-limiter 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/sethvargo/go-limiter vulnerabilities

Vulert verdict on github.com/sethvargo/go-limiter v1.2.0 i

Updated on 23 Oct 2026

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

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

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

  • Current release v1.2.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 726 i
  • OpenSSF scorecard 3/10 i
  • Last release 3 months ago 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-limiter, 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-20261005004043-cd11927274b6 05 Oct 2026 none Apache-2.0 — Details →
v1.2.1-0.20261005004043-cd11927274b6 05 Oct 2026 none Apache-2.0 — Details →
v0.0.0-20260907234342-20781e3e1a01 07 Sep 2026 none Apache-2.0 — Details →
v1.2.1-0.20260907234342-20781e3e1a01 07 Sep 2026 none Apache-2.0 — Details →
v0.0.0-20260717215302-294f8d8824cf 17 Jul 2026 none Apache-2.0 — Details →
v1.2.0 17 Jul 2026 none Apache-2.0 — Details →
v0.0.0-20251117181013-1e0fbd3f4f9b 17 Nov 2025 none Apache-2.0 — Details →
v1.1.0 17 Nov 2025 none Apache-2.0 — Details →
v1.0.1-0.20250412144437-fa26982c7e1a 12 Apr 2025 none Apache-2.0 — Details →
v1.0.1-0.20241217151428-351bc32b6fe9 17 Dec 2024 none Apache-2.0 — Details →
v0.0.0-20240325210013-1a742f09dc99 25 Mar 2024 none Apache-2.0 — Details →
v1.0.0 25 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20221215130607-54af081863cf 15 Dec 2022 none Apache-2.0 — Details →
v0.7.3-0.20221215130607-54af081863cf 15 Dec 2022 none Apache-2.0 — Details →
v0.7.3-0.20221215130556-04baaf3407bb 15 Dec 2022 none Apache-2.0 — Details →
v0.7.2 25 Sep 2021 none Apache-2.0 — Details →
v0.7.2-0.20210925032410-01bdc3538563 25 Sep 2021 none Apache-2.0 — Details →
v0.7.1 10 Sep 2021 none Apache-2.0 — Details →
v0.0.0-20210727160312-748ae80bc179 27 Jul 2021 none Apache-2.0 — Details →
v0.7.0 27 Jul 2021 none Apache-2.0 — Details →
v0.6.0 02 Oct 2020 none Apache-2.0 — Details →
v0.5.3-0.20200930180004-ee970c75d686 30 Sep 2020 none Apache-2.0 — Details →
v0.5.2 16 Sep 2020 none Apache-2.0 — Details →
v0.5.2-0.20200915001326-21f2ea74d7d4 15 Sep 2020 none Apache-2.0 — Details →
v0.5.1 14 Sep 2020 none Apache-2.0 — Details →
v0.4.1 26 Aug 2020 none Apache-2.0 — Details →
v0.4.0 18 Aug 2020 none Apache-2.0 — Details →
v0.0.0-20200818185929-f9ab9053588b 18 Aug 2020 none Apache-2.0 — Details →
v0.3.2-0.20200818185929-f9ab9053588b 18 Aug 2020 none Apache-2.0 — Details →
v0.3.1 11 Aug 2020 none Apache-2.0 — Details →
v0.3.0 09 Aug 2020 none Apache-2.0 — Details →
v0.2.4 07 Aug 2020 none Apache-2.0 — Details →
v0.2.3 24 Jul 2020 none Apache-2.0 — Details →
v0.2.3-0.20200716123632-42b041eecb4a 16 Jul 2020 none Apache-2.0 — Details →
v0.2.2 14 Jul 2020 none Apache-2.0 — Details →
v0.2.1 14 Jul 2020 none Apache-2.0 — Details →
v0.2.0 13 Jul 2020 none Apache-2.0 — Details →
v0.1.0 10 Jul 2020 none Apache-2.0 — Details →

All 38 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-limiter

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-limiter

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

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

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

No. v1.2.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-limiter should I use?

v1.2.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-limiter have?

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

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

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