Vulnerability Database · Go · Package report
rsc.io/goversion: vulnerability history, versions and safety
rsc.io/goversion 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 rsc.io/goversion v1.2.0 i
Updated on 23 Oct 2026
Good news: v1.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 v1.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.2.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 271 i
- OpenSSF scorecard 1/10 i
- Last release 102 months ago i
- Licence BSD-3-Clause 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 rsc.io/goversion, 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-20230309153236-3a30cee7003e 09 Mar 2023
- v1.2.1-0.20230309153236-3a30cee7003e 09 Mar 2023
- v0.0.0-20180404140801-597212e462da 04 Apr 2018
- v1.2.0 04 Apr 2018
- v1.1.0 09 Mar 2018
- v1.0.1-0.20170920182744-b792656d1049 20 Sep 2017
- v1.0.0 02 Sep 2017
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.0.0-20230309153236-3a30cee7003e | 09 Mar 2023 | none | BSD-3-Clause | — | Details → |
| v1.2.1-0.20230309153236-3a30cee7003e | 09 Mar 2023 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20180404140801-597212e462da | 04 Apr 2018 | none | BSD-3-Clause | — | Details → |
| v1.2.0 | 04 Apr 2018 | none | BSD-3-Clause | — | Details → |
| v1.1.0 | 09 Mar 2018 | none | BSD-3-Clause | — | Details → |
| v1.0.1-0.20170920182744-b792656d1049 | 20 Sep 2017 | none | BSD-3-Clause | — | Details → |
| v1.0.0 | 02 Sep 2017 | none | BSD-3-Clause | — | Details → |
All 7 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.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for rsc.io/goversion
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 rsc.io/goversion
Is rsc.io/goversion safe to use?
Vulert has no vulnerabilities on record for rsc.io/goversion 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 rsc.io/goversion's Vulert package health score?
Vulert scores rsc.io/goversion 49/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 rsc.io/goversion affected?
No. v1.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 rsc.io/goversion should I use?
v1.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 rsc.io/goversion have?
0 vulnerabilities are recorded for rsc.io/goversion 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 rsc.io/goversion vulnerabilities disclosed?
0 vulnerabilities were recorded for rsc.io/goversion 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 rsc.io/goversion 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 rsc.io/goversion for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the rsc.io/goversion version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.