Vulnerability Database · Go · Package report
github.com/corpix/uarand: vulnerability history, versions and safety
github.com/corpix/uarand 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/corpix/uarand v0.2.0 i
Updated on 23 Oct 2026
Good news: v0.2.0, 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.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.2.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 137 i
- OpenSSF scorecard 1/10 i
- Last release 53 months ago i
- Licence Unlicense 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/corpix/uarand, 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.2-0.20220517232902-742da754045f 17 May 2022
- v0.2.0 17 May 2022
- v0.1.2-0.20220517232737-6af5d037d982 17 May 2022
- v0.1.2-0.20210621231204-34af6a57a03a 21 Jun 2021
- v0.1.2-0.20210621231054-8c6d4bdf90a3 21 Jun 2021
- v0.1.2-0.20190826213412-6fd8ff1ca6b2 26 Aug 2019
- v0.1.2-0.20190826213001-0affdd100452 26 Aug 2019
- v0.1.1 26 Aug 2019
- v0.1.1-0.20190826210225-0321c942fa78 26 Aug 2019
- v0.0.0-20190418162141-e0e30101edc8 18 Apr 2019
- v0.1.1-0.20190418162141-e0e30101edc8 18 Apr 2019
- v0.1.0 18 Apr 2019
- v0.0.0 20 Nov 2018
- v0.0.0-20181120140456-37c9140f52f6 20 Nov 2018
- v0.0.0-20180829214735-1d461f02ebab 29 Aug 2018
- v0.0.0-20170903190822-2b8494104d86 03 Sep 2017
- v0.0.0-20170903190758-14832519c686 03 Sep 2017
- v0.0.0-20170723150923-031be390f409 23 Jul 2017
- v0.0.0-20170722222436-988f791f210d 22 Jul 2017
- v0.0.0-20170717200710-bec9f4e76616 17 Jul 2017
- v0.0.0-20170712210106-99aa07233de7 12 Jul 2017
- v0.0.0-20170712210038-656ff37f6da9 12 Jul 2017
- v0.0.0-20170709200027-a57882a7e86c 09 Jul 2017
- v0.0.0-20170227090421-1d58d0383c4d 27 Feb 2017
- v0.0.0-20170221203658-fb9394a49bbe 21 Feb 2017
All 25 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/corpix/uarand
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/corpix/uarand
Is github.com/corpix/uarand safe to use?
Vulert has no vulnerabilities on record for github.com/corpix/uarand 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/corpix/uarand's Vulert package health score?
Vulert scores github.com/corpix/uarand 47/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/corpix/uarand affected?
No. v0.2.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/corpix/uarand should I use?
v0.2.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/corpix/uarand have?
0 vulnerabilities are recorded for github.com/corpix/uarand 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/corpix/uarand vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/corpix/uarand 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/corpix/uarand 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/corpix/uarand for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/corpix/uarand version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.