Vulnerability Database · Go · Package report
github.com/korovkin/limiter: vulnerability history, versions and safety
github.com/korovkin/limiter 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/korovkin/limiter v0.0.0-20260306054425-004398ae7895 i
Updated on 23 Oct 2026
Good news: v0.0.0-20260306054425-004398ae7895, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Inactive
What to do: Stay on v0.0.0-20260306054425-004398ae7895 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20260306054425-004398ae7895 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20260306054425-004398ae7895 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 271 i
- OpenSSF scorecard 1/10 i
- Last release 7 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/korovkin/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.
- v0.0.0-20260306054425-004398ae7895 06 Mar 2026
- v0.0.0-20260224234706-f268eb6774ed 24 Feb 2026
- v0.0.0-20260224234058-420a689648ad 24 Feb 2026
- v0.0.0-20260224233837-f75054df4753 24 Feb 2026
- v0.0.0-20230407193026-e77dd126126b 07 Apr 2023
- v0.0.0-20230307205149-3d4b2b34c99d 07 Mar 2023
- v0.0.0-20230101005513-bfac7ca56b5a 01 Jan 2023
- v0.0.0-20221015170604-22eb1ceceddc 15 Oct 2022
- v0.0.0-20220422174850-01f593e64cf7 22 Apr 2022
- v0.0.0-20220422174411-d5661f034263 22 Apr 2022
- v0.0.0-20220422172309-938ddcc20e07 22 Apr 2022
- v0.0.0-20220321204241-2880bd9cecaf 21 Mar 2022
- v0.0.0-20220319000737-efebc0f7ccb6 19 Mar 2022
- v0.0.0-20220319000528-3f4ce5ffbc7c 19 Mar 2022
- v0.0.0-20190919045942-dac5a6b2a536 19 Sep 2019
- v0.0.0-20190816224620-1105f4dda562 16 Aug 2019
- v0.0.0-20170610225302-6b837f5fd496 10 Jun 2017
All 17 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/korovkin/limiter
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/korovkin/limiter
Is github.com/korovkin/limiter safe to use?
Vulert has no vulnerabilities on record for github.com/korovkin/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/korovkin/limiter's Vulert package health score?
Vulert scores github.com/korovkin/limiter 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/korovkin/limiter affected?
No. v0.0.0-20260306054425-004398ae7895, 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/korovkin/limiter should I use?
v0.0.0-20260306054425-004398ae7895 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/korovkin/limiter have?
0 vulnerabilities are recorded for github.com/korovkin/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/korovkin/limiter vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/korovkin/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/korovkin/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/korovkin/limiter for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/korovkin/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.