Vulnerability Database · Go · Package report
github.com/akutz/memconn: vulnerability history, versions and safety
github.com/akutz/memconn 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/akutz/memconn v0.1.0 i
Updated on 23 Oct 2026
Good news: v0.1.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Inactive
What to do: Stay on v0.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.1.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 550 i
- OpenSSF scorecard 1/10 i
- Last release 101 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/akutz/memconn, 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.1.1-0.20211110233653-dae351d188b3 10 Nov 2021
- v0.1.1-0.20211110231607-c507408148fd 10 Nov 2021
- v0.0.0-20180504174903-e0a19f53d865 04 May 2018
- v0.1.1-0.20180504174903-e0a19f53d865 04 May 2018
- v0.1.0 01 May 2018
- v0.0.0-20180501210650-13112ae2930b 01 May 2018
- v0.0.0-20180420175728-b1cba0b83639 20 Apr 2018
- v0.0.0-20180419222919-3211c0dc95c7 19 Apr 2018
- v0.0.0-20180418174133-13058736b5af 18 Apr 2018
- v0.0.0-20180403195521-2ab2f7b29490 03 Apr 2018
- v0.0.0-20180403001142-a430f99d66e3 03 Apr 2018
- v0.0.0-20180329144632-fc5b2b722d62 29 Mar 2018
- v0.0.0-20180329001654-56a9f1229181 29 Mar 2018
- v0.0.0-20180326180924-1d39d98edc3a 26 Mar 2018
- v0.0.0-20180118181749-6d806d44b3dd 18 Jan 2018
All 15 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/akutz/memconn
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/akutz/memconn
Is github.com/akutz/memconn safe to use?
Vulert has no vulnerabilities on record for github.com/akutz/memconn 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/akutz/memconn's Vulert package health score?
Vulert scores github.com/akutz/memconn 54/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/akutz/memconn affected?
No. v0.1.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/akutz/memconn should I use?
v0.1.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/akutz/memconn have?
0 vulnerabilities are recorded for github.com/akutz/memconn 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/akutz/memconn vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/akutz/memconn 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/akutz/memconn 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/akutz/memconn for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/akutz/memconn version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.