Vulnerability Database · Go · Package report
github.com/phayes/freeport: vulnerability history, versions and safety
github.com/phayes/freeport 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/phayes/freeport v0.0.0-20220201140144-74d24b5ae9f5 i
Updated on 23 Oct 2026
Good news: v0.0.0-20220201140144-74d24b5ae9f5, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Inactive
What to do: Stay on v0.0.0-20220201140144-74d24b5ae9f5 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20220201140144-74d24b5ae9f5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20220201140144-74d24b5ae9f5 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 368 i
- OpenSSF scorecard 1/10 i
- Last release 56 months ago i
- Licence BSD-3-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/phayes/freeport, 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-20220201140144-74d24b5ae9f5 01 Feb 2022
- v0.0.0-20220125200003-36de848f1bc3 25 Jan 2022
- v0.0.0-20180830031419-95f893ade6f2 30 Aug 2018
- v0.0.0-20180111143855-e5b3e0bfffdf 11 Jan 2018
- v0.0.0-20171002185219-e27662a4a9d6 02 Oct 2017
- v0.0.0-20171002184309-09c03d47cbe2 02 Oct 2017
- v0.0.0-20171002183030-2a385832a115 02 Oct 2017
- v0.0.0-20171002181615-b8543db493a5 02 Oct 2017
- v0.0.0-20171002181216-d417362077fa 02 Oct 2017
- v0.0.0-20171002180655-ce0a25f8fb13 02 Oct 2017
- v0.0.0-20171002163600-838dc301e91d 02 Oct 2017
- v0.0.0-20171002161421-1bde80a115a3 02 Oct 2017
- v0.0.0-20141201041908-e7681b376149 01 Dec 2014
- v0.0.0-20141112210135-0130d9925ee9 12 Nov 2014
- v0.0.0-20141106212150-04f25dec028a 06 Nov 2014
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/phayes/freeport
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/phayes/freeport
Is github.com/phayes/freeport safe to use?
Vulert has no vulnerabilities on record for github.com/phayes/freeport 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/phayes/freeport's Vulert package health score?
Vulert scores github.com/phayes/freeport 49/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/phayes/freeport affected?
No. v0.0.0-20220201140144-74d24b5ae9f5, 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/phayes/freeport should I use?
v0.0.0-20220201140144-74d24b5ae9f5 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/phayes/freeport have?
0 vulnerabilities are recorded for github.com/phayes/freeport 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/phayes/freeport vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/phayes/freeport 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/phayes/freeport 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/phayes/freeport for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/phayes/freeport version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.