Vulnerability Database · Go · Package report
github.com/heroku/rollrus: vulnerability history, versions and safety
github.com/heroku/rollrus 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/heroku/rollrus v0.2.0 i
Updated on 23 Oct 2026
Good news: v0.2.0, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Quiet
What to do: Stay on v0.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.2.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 25 i
- Last release 75 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/heroku/rollrus, 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.1-0.20250715152011-805419be67d6 15 Jul 2025
- v0.2.1-0.20211012141745-90a065c078dd 12 Oct 2021
- v0.1.2-0.20200626153655-de91b1ac2b67 26 Jun 2020
- v0.2.0 26 Jun 2020
- v0.1.2-0.20200612232900-1842e4814129 12 Jun 2020
- v0.1.2-0.20190923180503-0dcf4818b63d 23 Sep 2019
- v0.1.1 19 Sep 2019
- v0.1.0 17 Sep 2019
- v0.0.3 16 Sep 2019
- v0.0.2 10 Sep 2019
- v0.0.0-20190808224608-721edf0fc039 08 Aug 2019
- v0.0.1 08 Aug 2019
- v0.0.0-20190808011023-dab213917630 08 Aug 2019
- v0.0.0-20190808001249-79b7be99f486 08 Aug 2019
- v0.0.0-20190402185137-fde2a6b0b07d 02 Apr 2019
- v0.0.0-20190401180037-23b8b807783a 01 Apr 2019
- v0.0.0-20190314210611-5a638e9d3b33 14 Mar 2019
- v0.0.0-20180515183152-fc0cef2ff331 15 May 2018
- v0.0.0-20180305210051-7e6df3d078fc 05 Mar 2018
- v0.0.0-20170818212624-8c4f82380151 18 Aug 2017
- v0.0.0-20170705232004-7e04048459f4 05 Jul 2017
- v0.0.0-20160824233412-d20e35b8f913 24 Aug 2016
- v0.0.0-20150928223731-6effdcf9a2a4 28 Sep 2015
- v0.0.0-20150312230033-9a0cd307107e 12 Mar 2015
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/heroku/rollrus
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/heroku/rollrus
Is github.com/heroku/rollrus safe to use?
Vulert has no vulnerabilities on record for github.com/heroku/rollrus 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/heroku/rollrus's Vulert package health score?
Vulert scores github.com/heroku/rollrus 56/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/heroku/rollrus affected?
No. v0.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 github.com/heroku/rollrus should I use?
v0.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 github.com/heroku/rollrus have?
0 vulnerabilities are recorded for github.com/heroku/rollrus 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/heroku/rollrus vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/heroku/rollrus 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/heroku/rollrus 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/heroku/rollrus for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/heroku/rollrus version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.