Vulnerability Database · Go · Package report
github.com/themihai/gomemcache: vulnerability history, versions and safety
github.com/themihai/gomemcache 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/themihai/gomemcache v0.0.0-20180902122335-24332e2d58ab i
Updated on 23 Oct 2026
Good news: v0.0.0-20180902122335-24332e2d58ab, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.0-20180902122335-24332e2d58ab or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20180902122335-24332e2d58ab too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20180902122335-24332e2d58ab — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 1 i
- Last release 97 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/themihai/gomemcache, 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-20180902122335-24332e2d58ab 02 Sep 2018
- v0.0.0-20180710155616-bc664df96737 10 Jul 2018
- v0.0.0-20180627213657-7886924cd2b3 27 Jun 2018
- v0.0.0-20170208213004-1952afaa557d 08 Feb 2017
- v0.0.0-20161127232302-2fafb84a66c4 27 Nov 2016
- v0.0.0-20160117192205-fb1f79c6b65a 17 Jan 2016
- v0.0.0-20141108204336-72a68649ba71 08 Nov 2014
- v0.0.0-20140526142026-4faecadd4f69 26 May 2014
- v0.0.0-20110711034434-3d39f3a295e1 11 Jul 2011
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.0.0-20180902122335-24332e2d58ab | 02 Sep 2018 | none | Apache-2.0 | — | Details → |
| v0.0.0-20180710155616-bc664df96737 | 10 Jul 2018 | none | Apache-2.0 | — | Details → |
| v0.0.0-20180627213657-7886924cd2b3 | 27 Jun 2018 | none | Apache-2.0 | — | Details → |
| v0.0.0-20170208213004-1952afaa557d | 08 Feb 2017 | none | Apache-2.0 | — | Details → |
| v0.0.0-20161127232302-2fafb84a66c4 | 27 Nov 2016 | none | Apache-2.0 | — | Details → |
| v0.0.0-20160117192205-fb1f79c6b65a | 17 Jan 2016 | none | Apache-2.0 | — | Details → |
| v0.0.0-20141108204336-72a68649ba71 | 08 Nov 2014 | none | Apache-2.0 | — | Details → |
| v0.0.0-20140526142026-4faecadd4f69 | 26 May 2014 | none | Apache-2.0 | — | Details → |
| v0.0.0-20110711034434-3d39f3a295e1 | 11 Jul 2011 | none | — | — | Details → |
All 9 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/themihai/gomemcache
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/themihai/gomemcache
Is github.com/themihai/gomemcache safe to use?
Vulert has no vulnerabilities on record for github.com/themihai/gomemcache 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/themihai/gomemcache's Vulert package health score?
Vulert scores github.com/themihai/gomemcache 52/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/themihai/gomemcache affected?
No. v0.0.0-20180902122335-24332e2d58ab, 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/themihai/gomemcache should I use?
v0.0.0-20180902122335-24332e2d58ab 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/themihai/gomemcache have?
0 vulnerabilities are recorded for github.com/themihai/gomemcache 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/themihai/gomemcache vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/themihai/gomemcache 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/themihai/gomemcache 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/themihai/gomemcache for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/themihai/gomemcache version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.