Vulnerability Database · Go · Package report
github.com/mikioh/tcpinfo: vulnerability history, versions and safety
github.com/mikioh/tcpinfo 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/mikioh/tcpinfo v0.0.0-20190314235526-30a79bb1804b i
Updated on 23 Oct 2026
Good news: v0.0.0-20190314235526-30a79bb1804b, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.0-20190314235526-30a79bb1804b or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20190314235526-30a79bb1804b too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20190314235526-30a79bb1804b — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 43 i
- OpenSSF scorecard 1/10 i
- Last release 91 months ago i
- Licence BSD-2-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/mikioh/tcpinfo, 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-20190314235526-30a79bb1804b 14 Mar 2019
- v0.0.0-20180831101334-131b59fef27f 31 Aug 2018
- v0.0.0-20180210234901-fd8b9a80d71e 10 Feb 2018
- v0.0.0-20170613093330-e198f0e81d5e 13 Jun 2017
- v0.0.0-20170128005504-6df8d3bc682f 28 Jan 2017
- v0.0.0-20161217003350-75ccd103501d 17 Dec 2016
- v0.0.0-20161020062831-48c91579c432 20 Oct 2016
- v0.0.0-20160728220557-ee24b4520f20 28 Jul 2016
- v0.0.0-20160715092703-128f5c64bc87 15 Jul 2016
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.0.0-20190314235526-30a79bb1804b | 14 Mar 2019 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20180831101334-131b59fef27f | 31 Aug 2018 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20180210234901-fd8b9a80d71e | 10 Feb 2018 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20170613093330-e198f0e81d5e | 13 Jun 2017 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20170128005504-6df8d3bc682f | 28 Jan 2017 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20161217003350-75ccd103501d | 17 Dec 2016 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20161020062831-48c91579c432 | 20 Oct 2016 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20160728220557-ee24b4520f20 | 28 Jul 2016 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20160715092703-128f5c64bc87 | 15 Jul 2016 | none | BSD-2-Clause | — | 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/mikioh/tcpinfo
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/mikioh/tcpinfo
Is github.com/mikioh/tcpinfo safe to use?
Vulert has no vulnerabilities on record for github.com/mikioh/tcpinfo 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/mikioh/tcpinfo's Vulert package health score?
Vulert scores github.com/mikioh/tcpinfo 42/100, which reads as risky. 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/mikioh/tcpinfo affected?
No. v0.0.0-20190314235526-30a79bb1804b, 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/mikioh/tcpinfo should I use?
v0.0.0-20190314235526-30a79bb1804b 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/mikioh/tcpinfo have?
0 vulnerabilities are recorded for github.com/mikioh/tcpinfo 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/mikioh/tcpinfo vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/mikioh/tcpinfo 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/mikioh/tcpinfo 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/mikioh/tcpinfo for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/mikioh/tcpinfo version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.