Vulnerability Database · Go · Package report
github.com/leesper/go_rng: vulnerability history, versions and safety
github.com/leesper/go_rng 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/leesper/go_rng v0.0.0-20190531154944-a612b043e353 i
Updated on 23 Oct 2026
Good news: v0.0.0-20190531154944-a612b043e353, 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-20190531154944-a612b043e353 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20190531154944-a612b043e353 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20190531154944-a612b043e353 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 114 i
- OpenSSF scorecard 1/10 i
- Last release 88 months ago i
- Licence Apache-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/leesper/go_rng, 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-20190531154944-a612b043e353 31 May 2019
- v0.0.0-20190507055134-621d7363b204 07 May 2019
- v0.0.0-20171009123644-5344a9259b21 09 Oct 2017
- v0.0.0-20171009053301-e30b76597cd8 09 Oct 2017
- v0.0.0-20170109010011-edc201f107a8 09 Jan 2017
- v0.0.0-20170108175755-3f93de458169 08 Jan 2017
- v0.0.0-20170106060614-cac3e6c1e4d7 06 Jan 2017
- v0.0.0-20160728073239-87bae24106c5 28 Jul 2016
- v0.0.0-20160420235759-045f69b0fb19 20 Apr 2016
- v0.0.0-20160420212718-6513a9f0f060 20 Apr 2016
- v0.0.0-20160214061512-0816572ea28b 14 Feb 2016
- v0.0.0-20160207144859-9a1cd988cab7 07 Feb 2016
- v0.0.0-20160207132152-2cfafd178f08 07 Feb 2016
- v0.0.0-20160205151145-bcb829956ed7 05 Feb 2016
- v0.0.0-20160205150344-5f6f8a92193f 05 Feb 2016
- v0.0.0-20140328134322-20e0c02c4b6b 28 Mar 2014
All 16 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/leesper/go_rng
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/leesper/go_rng
Is github.com/leesper/go_rng safe to use?
Vulert has no vulnerabilities on record for github.com/leesper/go_rng 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/leesper/go_rng's Vulert package health score?
Vulert scores github.com/leesper/go_rng 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/leesper/go_rng affected?
No. v0.0.0-20190531154944-a612b043e353, 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/leesper/go_rng should I use?
v0.0.0-20190531154944-a612b043e353 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/leesper/go_rng have?
0 vulnerabilities are recorded for github.com/leesper/go_rng 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/leesper/go_rng vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/leesper/go_rng 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/leesper/go_rng 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/leesper/go_rng for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/leesper/go_rng version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.