Vulnerability Database · Go · Package report

github.com/lestrrat-go/file-rotatelogs: vulnerability history, versions and safety

github.com/lestrrat-go/file-rotatelogs is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/lestrrat-go/file-rotatelogs v2.4.0+incompatible i

Updated on 23 Oct 2026

Good news: v2.4.0+incompatible, the version you would install today, has no known vulnerabilities.

Package health score 57/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Widely used
  • Community Quiet

What to do: Stay on v2.4.0+incompatible or newer. This can change: a vulnerability disclosed tomorrow can affect v2.4.0+incompatible too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v2.4.0+incompatible — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 980 i
  • OpenSSF scorecard 2/10 i
  • Last release 73 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/lestrrat-go/file-rotatelogs, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.0.0-20210718223510-fa6221d6e82a 18 Jul 2021 none MIT — Details →
v0.0.0-20201218081348-f6ef97f4d6da 18 Dec 2020 none MIT — Details →
v0.0.0-20201029035330-b789b39afbd7 29 Oct 2020 none MIT — Details →
v0.0.0-20201029034320-582074b65dd4 29 Oct 2020 none MIT — Details →
v0.0.0-20201029000401-c9c9ed090800 29 Oct 2020 none MIT — Details →
v0.0.0-20200908100331-f962e9de32ae 08 Sep 2020 none MIT — Details →
v2.4.0+incompatible 08 Sep 2020 none MIT — Details →
v2.3.1-0.20200907231458-dc2f7d20d426+incompatible 07 Sep 2020 none MIT — Details →
v2.3.1-0.20200819073132-d086d5566641+incompatible 19 Aug 2020 none MIT — Details →
v2.3.1-0.20200701224615-73e5d4231a2b+incompatible 01 Jul 2020 none MIT — Details →
v2.3.1-0.20200701200536-925e1d518f36+incompatible 01 Jul 2020 none MIT — Details →
v0.0.0-20200409032425-0b0a5762632f 09 Apr 2020 none MIT — Details →
v2.3.1-0.20200409032425-0b0a5762632f+incompatible 09 Apr 2020 none MIT — Details →
v0.0.0-20190718000351-e0a88b0fe840 18 Jul 2019 none MIT — Details →
v2.2.1-0.20190718000351-e0a88b0fe840+incompatible 18 Jul 2019 none MIT — Details →
v2.3.0+incompatible 18 Jul 2019 none MIT — Details →
v2.2.1-0.20190717185349-e92e07d07467+incompatible 17 Jul 2019 none MIT — Details →
v0.0.0-20190604011245-cf4bc193a5a5 04 Jun 2019 none MIT — Details →
v2.2.1-0.20190604011245-cf4bc193a5a5+incompatible 04 Jun 2019 none MIT — Details →
v2.2.1-0.20190603064757-4c352163c22b+incompatible 03 Jun 2019 none MIT — Details →
v0.0.0-20181019123106-4ce522c92b91 19 Oct 2018 none MIT — Details →
v2.2.1-0.20181019123106-4ce522c92b91+incompatible 19 Oct 2018 none MIT — Details →
v0.0.0-20181019114346-8446d0915b62 19 Oct 2018 none MIT — Details →
v2.2.1-0.20181019114346-8446d0915b62+incompatible 19 Oct 2018 none MIT — Details →
v0.0.0-20180926095352-d72d6cf46fc8 26 Sep 2018 none MIT — Details →
v2.2.1-0.20180926095352-d72d6cf46fc8+incompatible 26 Sep 2018 none MIT — Details →
v0.0.0-20180607094457-00616292e771 07 Jun 2018 none MIT — Details →
v2.2.1-0.20180607094457-00616292e771+incompatible 07 Jun 2018 none MIT — Details →
v0.0.0-20180602110308-3b4f34a036f3 02 Jun 2018 none MIT — Details →
v2.2.0+incompatible 02 Jun 2018 none MIT — Details →
v0.0.0-20180414115738-81893a53aa4f 14 Apr 2018 none MIT — Details →
v2.1.1-0.20180414115738-81893a53aa4f+incompatible 14 Apr 2018 none MIT — Details →
v0.0.0-20180319023937-31912ebef06a 19 Mar 2018 none MIT — Details →
v2.1.1-0.20180319023937-31912ebef06a+incompatible 19 Mar 2018 none MIT — Details →
v0.0.0-20180223000850-2116cfc2a65a 23 Feb 2018 none MIT — Details →
v2.1.1-0.20180223000850-2116cfc2a65a+incompatible 23 Feb 2018 none MIT — Details →
v2.1.1-0.20171228224303-337122620255+incompatible 28 Dec 2017 none MIT — Details →
v2.1.0+incompatible 01 May 2017 none MIT — Details →
v2.0.1-0.20161229111242-1a56ff6225fd+incompatible 29 Dec 2016 none MIT — Details →
v0.0.0-20160915080032-ab335c655133 15 Sep 2016 none MIT — Details →
v2.0.0+incompatible 15 Sep 2016 none MIT — Details →
v0.0.0-20160915055009-3f1621334ce8 15 Sep 2016 none MIT — Details →
v0.0.0-20150118073402-bb1d28fd5ac7 18 Jan 2015 none MIT — Details →

All 43 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/lestrrat-go/file-rotatelogs

No vulnerability write-ups match this view

Search all 0 in the database →

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/lestrrat-go/file-rotatelogs

Is github.com/lestrrat-go/file-rotatelogs safe to use?

Vulert has no vulnerabilities on record for github.com/lestrrat-go/file-rotatelogs 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/lestrrat-go/file-rotatelogs's Vulert package health score?

Vulert scores github.com/lestrrat-go/file-rotatelogs 57/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/lestrrat-go/file-rotatelogs affected?

No. v2.4.0+incompatible, 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/lestrrat-go/file-rotatelogs should I use?

v2.4.0+incompatible 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/lestrrat-go/file-rotatelogs have?

0 vulnerabilities are recorded for github.com/lestrrat-go/file-rotatelogs 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/lestrrat-go/file-rotatelogs vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/lestrrat-go/file-rotatelogs 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/lestrrat-go/file-rotatelogs 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/lestrrat-go/file-rotatelogs for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/lestrrat-go/file-rotatelogs version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.