Vulnerability Database · Go · Package report
github.com/mitchellh/gox: vulnerability history, versions and safety
github.com/mitchellh/gox 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/mitchellh/gox v1.0.1 i
Updated on 23 Oct 2026
Good news: v1.0.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Key ecosystem project
- Community Quiet
What to do: Stay on v1.0.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.0.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 4,571 i
- OpenSSF scorecard 3/10 i
- Last release 90 months ago i
- Licence MPL-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/mitchellh/gox, 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-20220701044238-9f712387e2d2 01 Jul 2022
- v0.4.1-0.20220701044238-9f712387e2d2 01 Jul 2022
- v1.0.2-0.20220701044238-9f712387e2d2 01 Jul 2022
- v1.0.2-0.20210311182516-8c3b2b9e647d 11 Mar 2021
- v1.0.2-0.20210311010033-667903a68511 11 Mar 2021
- v0.0.0-20190410150203-d8caaff5a9dc 10 Apr 2019
- v1.0.1 10 Apr 2019
- v0.0.0-20181025215326-9cc487598128 25 Oct 2018
- v1.0.0 25 Oct 2018
- v0.4.1-0.20180824035937-51ed453898ca 24 Aug 2018
- v0.4.1-0.20180103152619-0d65d8b8c2d1 03 Jan 2018
- v0.4.0 25 Jul 2016
- v0.3.1-0.20160512164837-6e9ee79eab7b 12 May 2016
- v0.0.0-20160505160858-07260c36cdd9 05 May 2016
- v0.3.1-0.20160505160858-07260c36cdd9 05 May 2016
- v0.3.1-0.20160331001216-dc474e55926b 31 Mar 2016
- v0.0.0-20151230230934-39862d88e853 30 Dec 2015
- v0.3.1-0.20151230230934-39862d88e853 30 Dec 2015
- v0.3.1-0.20151209171340-e072e401448d 09 Dec 2015
- v0.0.0-20151015193848-770c39f64e66 15 Oct 2015
- v0.3.1-0.20151015193848-770c39f64e66 15 Oct 2015
- v0.3.1-0.20140904183246-e8e6fd4fe125 04 Sep 2014
- v0.0.0-20131124033940-54b619477e89 24 Nov 2013
- v0.3.0 24 Nov 2013
- v0.2.0 19 Nov 2013
- v0.1.0 18 Nov 2013
All 26 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/mitchellh/gox
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/mitchellh/gox
Is github.com/mitchellh/gox safe to use?
Vulert has no vulnerabilities on record for github.com/mitchellh/gox 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/mitchellh/gox's Vulert package health score?
Vulert scores github.com/mitchellh/gox 62/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/mitchellh/gox affected?
No. v1.0.1, 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/mitchellh/gox should I use?
v1.0.1 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/mitchellh/gox have?
0 vulnerabilities are recorded for github.com/mitchellh/gox 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/mitchellh/gox vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/mitchellh/gox 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/mitchellh/gox 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/mitchellh/gox for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/mitchellh/gox version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.