Vulnerability Database · Go · Package report
github.com/mediocregopher/radix/v4: vulnerability history, versions and safety
github.com/mediocregopher/radix/v4 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/mediocregopher/radix/v4 v4.1.5 i
Updated on 23 Oct 2026
Good news: v4.1.5, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Widely used
- Community Quiet
What to do: Stay on v4.1.5 or newer. This can change: a vulnerability disclosed tomorrow can affect v4.1.5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v4.1.5 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 636 i
- OpenSSF scorecard 2/10 i
- Last release 5 months ago i
- Licence MIT 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/mediocregopher/radix/v4, 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.
- v4.1.5 13 May 2026
- v4.1.5-0.20231130075151-8f4868bc5351 30 Nov 2023
- v4.1.5-0.20230906203445-b91b73204fc0 06 Sep 2023
- v4.1.4 25 Aug 2023
- v4.1.4-0.20230825121021-0c69f31269e3 25 Aug 2023
- v4.1.3 03 Jul 2023
- v4.1.2 21 Jan 2023
- v4.1.2-0.20230117162541-ca99d67484e3 17 Jan 2023
- v4.1.2-0.20221213191501-84dff11dc040 13 Dec 2022
- v4.1.2-0.20221212205155-77067511c2ca 12 Dec 2022
- v4.1.2-0.20221209144448-6b55a59ba8fc 09 Dec 2022
- v4.1.2-0.20221126182419-de9fba43818d 26 Nov 2022
- v4.1.1 13 Aug 2022
- v4.1.1-0.20220801222044-d1a6a71693c3 01 Aug 2022
- v4.1.1-0.20220617165711-66ad70f443c0 17 Jun 2022
- v4.1.0 18 Apr 2022
- v4.0.0 15 Oct 2021
- v4.0.0-beta.1.0.20210828174855-30c3db11b3e5 28 Aug 2021
- v4.0.0-beta.1.0.20210726230805-d62fa1b2e3cb 26 Jul 2021
- v4.0.0-beta.1.0.20210622215007-883255ada404 22 Jun 2021
- v4.0.0-beta.1.0.20210606132330-06f1f6836b60 06 Jun 2021
- v4.0.0-beta.1.0.20210603143710-45242c487bc8 03 Jun 2021
- v4.0.0-beta.1.0.20210530205509-8d45a17a6f03 30 May 2021
- v4.0.0-beta.1.0.20210512125036-6b97df97e70b 12 May 2021
- v4.0.0-beta.1.0.20210309001510-bcfb640342e3 09 Mar 2021
- v4.0.0-beta.1.0.20210208230724-28481b9a8e0f 08 Feb 2021
- v4.0.0-beta.1.0.20210119005354-9f32b1f5a691 19 Jan 2021
- v4.0.0-beta.1.0.20210117001606-9b8ee0e8032b 17 Jan 2021
- v4.0.0-beta.1.0.20201231181512-c9469b763991 31 Dec 2020
- v4.0.0-beta.0.0.20201229232413-b6cae26a5d6b 29 Dec 2020
- v4.0.0-beta.1 29 Dec 2020
- v4.0.0-20201004182601-240db84e7528 04 Oct 2020
- v4.0.0-beta.0 04 Oct 2020
All 33 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/mediocregopher/radix/v4
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/mediocregopher/radix/v4
Is github.com/mediocregopher/radix/v4 safe to use?
Vulert has no vulnerabilities on record for github.com/mediocregopher/radix/v4 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/mediocregopher/radix/v4's Vulert package health score?
Vulert scores github.com/mediocregopher/radix/v4 74/100, which reads as in good shape. 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/mediocregopher/radix/v4 affected?
No. v4.1.5, 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/mediocregopher/radix/v4 should I use?
v4.1.5 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/mediocregopher/radix/v4 have?
0 vulnerabilities are recorded for github.com/mediocregopher/radix/v4 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/mediocregopher/radix/v4 vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/mediocregopher/radix/v4 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/mediocregopher/radix/v4 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/mediocregopher/radix/v4 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/mediocregopher/radix/v4 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.