Vulnerability Database · Go · Package report
github.com/arthurkiller/rollingwriter: vulnerability history, versions and safety
github.com/arthurkiller/rollingwriter 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.
See all github.com/arthurkiller/rollingwriter vulnerabilities
Vulert verdict on github.com/arthurkiller/rollingwriter v1.1.3 i
Updated on 23 Oct 2026
Good news: v1.1.3, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Quiet
What to do: Stay on v1.1.3 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.1.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.1.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 292 i
- OpenSSF scorecard 2/10 i
- Last release 56 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/arthurkiller/rollingwriter, 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.
- v1.1.4-0.20231016063820-3145271986bc 16 Oct 2023
- v1.1.4-0.20230202110508-965c6fc2d193 02 Feb 2023
- v1.1.4-0.20230117114440-9c5b18b3786f 17 Jan 2023
- v0.0.0-20221116035709-f044c6a501b5 16 Nov 2022
- v1.1.4-0.20221116035709-f044c6a501b5 16 Nov 2022
- v0.0.0-20221115150712-53a5ce833c21 15 Nov 2022
- v1.1.4-0.20220620032430-d363b284e593 20 Jun 2022
- v1.1.3 11 Feb 2022
- v1.1.3-0.20220211070658-c19a8e8b35be 11 Feb 2022
- v1.1.3-0.20220118032506-6afd6b6585b8 18 Jan 2022
- v1.1.3-0.20211213070902-40fb19f8564d 13 Dec 2021
- v1.1.3-0.20210825082109-f61c29bf8751 25 Aug 2021
- v1.1.3-0.20210825073344-020700694b8c 25 Aug 2021
- v1.1.3-0.20200924120901-39e8404ab060 24 Sep 2020
- v1.1.3-0.20200908112058-c2c04fc2789b 08 Sep 2020
- v1.1.3-0.20200218043043-0c781a15588e 18 Feb 2020
- v1.1.2 04 Dec 2019
- v1.1.2-0.20191204083436-560349772db9 04 Dec 2019
- v1.1.2-0.20190916035742-48c91aa3bdfb 16 Sep 2019
- v1.1.1 17 May 2019
- v1.0.2-0.20181126161630-fe05614819cc 26 Nov 2018
- v1.0.1 15 Nov 2018
- v1.0.1-0.20180904034031-e7449b1b067c 04 Sep 2018
- v1.0.0 09 Nov 2017
All 24 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/arthurkiller/rollingwriter
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/arthurkiller/rollingwriter
Is github.com/arthurkiller/rollingwriter safe to use?
Vulert has no vulnerabilities on record for github.com/arthurkiller/rollingwriter 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/arthurkiller/rollingwriter's Vulert package health score?
Vulert scores github.com/arthurkiller/rollingwriter 50/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/arthurkiller/rollingwriter affected?
No. v1.1.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/arthurkiller/rollingwriter should I use?
v1.1.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/arthurkiller/rollingwriter have?
0 vulnerabilities are recorded for github.com/arthurkiller/rollingwriter 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/arthurkiller/rollingwriter vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/arthurkiller/rollingwriter 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/arthurkiller/rollingwriter 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/arthurkiller/rollingwriter for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/arthurkiller/rollingwriter version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.