Vulnerability Database · Go · Package report
github.com/jingyugao/rowserrcheck: vulnerability history, versions and safety
github.com/jingyugao/rowserrcheck 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/jingyugao/rowserrcheck v1.1.1 i
Updated on 23 Oct 2026
Good news: v1.1.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Inactive
What to do: Stay on v1.1.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.1.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.1.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 17 i
- OpenSSF scorecard 1/10 i
- Last release 60 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/jingyugao/rowserrcheck, 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-20220704084010-fa9179529ab8 04 Jul 2022
- v1.1.2-0.20220704084010-fa9179529ab8 04 Jul 2022
- v1.1.1 18 Oct 2021
- v1.1.1-0.20211018075540-bd4dd444ec30 18 Oct 2021
- v0.0.0-20210315055705-d907ca737bb1 15 Mar 2021
- v1.1.0 15 Mar 2021
- v0.0.0-20210314081003-080ff0b0c4c0 14 Mar 2021
- v0.0.0-20210130005344-c6a0c12dd98d 30 Jan 2021
- v0.0.0-20210129184156-3563e895b5ce 29 Jan 2021
- v0.0.0-20191204022205-72ab7603b68a 04 Dec 2019
- v0.0.0-20191116063505-6855e040dddc 16 Nov 2019
- v0.0.0-20191116062325-4815a29151e6 16 Nov 2019
- v0.0.0-20191116055745-a45cb683a0e4 16 Nov 2019
- v0.0.0-20191113115121-a3474012aacc 13 Nov 2019
- v0.0.0-20191111115803-2e29ce8441b0 11 Nov 2019
- v0.0.0-20191111081657-a3dff4d817c6 11 Nov 2019
- v0.0.0-20191109104502-9d97ac16db4e 09 Nov 2019
- v0.0.0-20191109104255-74b191d466ad 09 Nov 2019
- v0.0.0-20191109085642-da3a8bad75e0 09 Nov 2019
- v0.0.0-20191109085147-241bfea599f0 09 Nov 2019
- v0.0.0-20191109084807-725e2cbf9a1a 09 Nov 2019
- v0.0.0-20191109071649-95e4d020b1de 09 Nov 2019
- v0.0.0-20191109070513-80719221d9ba 09 Nov 2019
- v0.0.0-20191109061513-ff60c46cad51 09 Nov 2019
- v0.0.0-20191108124432-d56f06307762 08 Nov 2019
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/jingyugao/rowserrcheck
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/jingyugao/rowserrcheck
Is github.com/jingyugao/rowserrcheck safe to use?
Vulert has no vulnerabilities on record for github.com/jingyugao/rowserrcheck 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/jingyugao/rowserrcheck's Vulert package health score?
Vulert scores github.com/jingyugao/rowserrcheck 42/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/jingyugao/rowserrcheck affected?
No. v1.1.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/jingyugao/rowserrcheck should I use?
v1.1.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/jingyugao/rowserrcheck have?
0 vulnerabilities are recorded for github.com/jingyugao/rowserrcheck 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/jingyugao/rowserrcheck vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/jingyugao/rowserrcheck 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/jingyugao/rowserrcheck 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/jingyugao/rowserrcheck for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/jingyugao/rowserrcheck version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.