Vulnerability Database · Go · Package report

github.com/natefinch/lumberjack: vulnerability history, versions and safety

github.com/natefinch/lumberjack 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/natefinch/lumberjack v2.0.0+incompatible i

Updated on 23 Oct 2026

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

Package health score 59/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release v2.0.0+incompatible — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 5,478 i
  • OpenSSF scorecard 1/10 i
  • Last release 98 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/natefinch/lumberjack, 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-20230119042236-215739b3bcdc 19 Jan 2023 none MIT — Details →
v0.0.0-20201021141957-47ffae23317c 21 Oct 2020 none MIT — Details →
v0.0.0-20190411184413-94d9e492cc53 11 Apr 2019 none MIT — Details →
v2.0.1-0.20190411184413-94d9e492cc53+incompatible 11 Apr 2019 none MIT — Details →
v2.0.1-0.20190411183718-4b74a4dba98b+incompatible 11 Apr 2019 none MIT — Details →
v2.0.1-0.20190411144226-2e8fbeea3f9e+incompatible 11 Apr 2019 none MIT — Details →
v0.0.0-20180817145747-7d6a1875575e 17 Aug 2018 none MIT — Details →
v2.0.0+incompatible 17 Aug 2018 none MIT — Details →
v0.0.0-20170911140457-aee462912944 11 Sep 2017 none MIT — Details →
v0.0.0-20170531180850-df99d62fd42d 31 May 2017 none MIT — Details →
v0.0.0-20170531160350-a96e63847dc3 31 May 2017 none MIT — Details →
v2.0.0-20170531160350-a96e63847dc3+incompatible 31 May 2017 none MIT — Details →
v0.0.0-20161104145732-dd45e6a67c53 04 Nov 2016 none MIT — Details →
v2.0.0-20161104145732-dd45e6a67c53+incompatible 04 Nov 2016 none MIT — Details →
v0.0.0-20161007184028-e21e5cbec0cd 07 Oct 2016 none MIT — Details →
v0.0.0-20160125111749-514cbda263a7 25 Jan 2016 none MIT — Details →
v0.0.0-20160125041909-3cfd7a4e7479 25 Jan 2016 none MIT — Details →
v0.0.0-20151013014448-600ceb4523e5 13 Oct 2015 none MIT — Details →
v0.0.0-20150622162204-20b71e5b60d7 22 Jun 2015 none MIT — Details →
v2.0.0-20150622162204-20b71e5b60d7+incompatible 22 Jun 2015 none MIT — Details →
v0.0.0-20150521015918-588a21fb0fa0 21 May 2015 none MIT — Details →
v0.0.0-20150411233054-6d54cbc97d7e 11 Apr 2015 none MIT — Details →
v0.0.0-20140725205133-d28785c2f27c 25 Jul 2014 none MIT — Details →
v0.0.0-20140725200019-6d3dfa6c0e13 25 Jul 2014 none MIT — Details →
v0.0.0-20140723094604-8b224001f481 23 Jul 2014 none MIT — Details →
v0.0.0-20140718202335-2837c0edfbaf 18 Jul 2014 none MIT — Details →
v0.0.0-20140624125125-a6f35bab25c9 24 Jun 2014 none MIT — Details →
v0.0.0-20140618183000-8ec9c6b748e0 18 Jun 2014 none MIT — Details →
v0.0.0-20140618120940-72cc861377da 18 Jun 2014 none MIT — Details →
v0.0.0-20140616135257-03e9c77b42d6 16 Jun 2014 none MIT — Details →
v0.0.0-20140615105723-1bb33e2fca29 15 Jun 2014 none MIT — Details →
v0.0.0-20140614115717-1c3db7d9eaa6 14 Jun 2014 none MIT — Details →

All 32 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/natefinch/lumberjack

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/natefinch/lumberjack

Is github.com/natefinch/lumberjack safe to use?

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

Vulert scores github.com/natefinch/lumberjack 59/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/natefinch/lumberjack affected?

No. v2.0.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/natefinch/lumberjack should I use?

v2.0.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/natefinch/lumberjack have?

0 vulnerabilities are recorded for github.com/natefinch/lumberjack 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/natefinch/lumberjack vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/natefinch/lumberjack 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/natefinch/lumberjack 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/natefinch/lumberjack for upcoming vulnerabilities?

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