Vulnerability Database · Go · Package report
github.com/rboyer/safeio: vulnerability history, versions and safety
github.com/rboyer/safeio 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/rboyer/safeio v0.2.3 i
Updated on 23 Oct 2026
Good news: v0.2.3, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.2.3 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.2.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.2.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 7 i
- OpenSSF scorecard 3/10 i
- Last release 38 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/rboyer/safeio, 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.2.3 26 Jul 2023
- v0.2.3-0.20230726163902-ce7e521e9947 26 Jul 2023
- v0.2.3-0.20230726163124-43faa4aaabc5 26 Jul 2023
- v0.0.0-20230307224522-d261689086ac 07 Mar 2023
- v0.2.3-0.20230307224522-d261689086ac 07 Mar 2023
- v0.2.2 31 Jan 2023
- v0.2.2-0.20201102211151-8e3b455fa790 02 Nov 2020
- v0.2.2-0.20201102211058-51ca2b9ca03a 02 Nov 2020
- v0.2.2-0.20201102210829-dc958afc43c1 02 Nov 2020
- v0.2.1 23 Apr 2020
- v0.2.0 23 Apr 2020
- v0.1.1-0.20200423212817-055586bb2b67 23 Apr 2020
- v0.0.0-20180813142905-6c213bb5b4af 13 Aug 2018
- v0.1.1-0.20180813142905-6c213bb5b4af 13 Aug 2018
- v0.1.0 12 Jul 2016
- v0.0.0-20160712012944-07dfb0fb55b0 12 Jul 2016
- v0.0.0-20160217151014-9e3bc6356198 17 Feb 2016
- v0.0.0-20150123151926-12198d38c6c8 23 Jan 2015
All 18 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/rboyer/safeio
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/rboyer/safeio
Is github.com/rboyer/safeio safe to use?
Vulert has no vulnerabilities on record for github.com/rboyer/safeio 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/rboyer/safeio's Vulert package health score?
Vulert scores github.com/rboyer/safeio 52/100, which reads as usable, but worth attention. 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/rboyer/safeio affected?
No. v0.2.3, 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/rboyer/safeio should I use?
v0.2.3 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/rboyer/safeio have?
0 vulnerabilities are recorded for github.com/rboyer/safeio 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/rboyer/safeio vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/rboyer/safeio 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/rboyer/safeio 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/rboyer/safeio for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/rboyer/safeio version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.