Vulnerability Database · Go · Package report

github.com/rifflock/lfshook: vulnerability history, versions and safety

github.com/rifflock/lfshook 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/rifflock/lfshook v0.0.0-20180920164130-b9218ef580f5 i

Updated on 23 Oct 2026

Good news: v0.0.0-20180920164130-b9218ef580f5, the version you would install today, has no known vulnerabilities.

Package health score 50/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Quiet

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

  • Current release v0.0.0-20180920164130-b9218ef580f5 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 415 i
  • OpenSSF scorecard 2/10 i
  • Last release 97 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/rifflock/lfshook, 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-20180920164130-b9218ef580f5 20 Sep 2018 none MIT — Details →
v2.0.0-20180920164130-b9218ef580f5+incompatible 20 Sep 2018 none MIT — Details →
v0.0.0-20180919232726-978b66d19420 19 Sep 2018 none MIT — Details →
v0.0.0-20180313183424-62f5e0662816 13 Mar 2018 none MIT — Details →
v0.0.0-20180227222202-bf539943797a 27 Feb 2018 none MIT — Details →
v0.0.0-20171219153109-1fdc019a3514 19 Dec 2017 none MIT — Details →
v0.0.0-20171213113526-8299919091f9 13 Dec 2017 none MIT — Details →
v0.0.0-20171212201755-1e6869029fcb 12 Dec 2017 none MIT — Details →
v0.0.0-20171212034441-83da2467e40d 12 Dec 2017 none MIT — Details →
v0.0.0-20171210132504-4c0e6d6bf843 10 Dec 2017 none MIT — Details →
v0.0.0-20171210131122-2cc9e6b4adda 10 Dec 2017 none MIT — Details →
v0.0.0-20171210093846-eaaa9d2efa83 10 Dec 2017 none MIT — Details →
v0.0.0-20171206232842-765177c893cc 06 Dec 2017 none MIT — Details →
v2.0.0-20171206232842-765177c893cc+incompatible 06 Dec 2017 none MIT — Details →
v0.0.0-20171130175801-bd08170fdd38 30 Nov 2017 none MIT — Details →
v0.0.0-20170910022531-3bcf86f879c7 10 Sep 2017 none MIT — Details →
v0.0.0-20170910022116-469f9bd4a1f5 10 Sep 2017 none MIT — Details →
v0.0.0-20170713173721-271f86636484 13 Jul 2017 none MIT — Details →
v0.0.0-20170713173605-cb480fb23761 13 Jul 2017 none MIT — Details →
v0.0.0-20170601165600-6844c808343c 01 Jun 2017 none MIT — Details →
v0.0.0-20170531073650-d01b26ad36d1 31 May 2017 none MIT — Details →
v0.0.0-20170411202324-2adb3e0c4ddd 11 Apr 2017 none MIT — Details →
v0.0.0-20170411193406-becf357cb6c4 11 Apr 2017 none MIT — Details →
v0.0.0-20170215182608-1ae91782cf87 15 Feb 2017 none MIT — Details →
v0.0.0-20170215180543-b4c2a431353c 15 Feb 2017 none MIT — Details →
v0.0.0-20170215083308-ddcd56ce9d10 15 Feb 2017 none MIT — Details →
v0.0.0-20170215072111-996836e56e78 15 Feb 2017 none MIT — Details →
v0.0.0-20170123215949-7088bad6ba66 23 Jan 2017 none MIT — Details →
v0.0.0-20170121114302-d78eea40bef7 21 Jan 2017 none MIT — Details →
v0.0.0-20161216150210-24f7833daaff 16 Dec 2016 none MIT — Details →
v0.0.0-20161216145954-b1def10f8fe9 16 Dec 2016 none MIT — Details →
v0.0.0-20161216094650-40267097ec38 16 Dec 2016 none MIT — Details →
v0.0.0-20161215205719-2c953db8b9bb 15 Dec 2016 none MIT — Details →
v0.0.0-20160909042548-3f9d976bd740 09 Sep 2016 none MIT — Details →
v0.0.0-20160909005128-9f5980103018 09 Sep 2016 none MIT — Details →
v0.0.0-20160828012841-2b69fc4ea95c 28 Aug 2016 none MIT — Details →
v0.0.0-20160801122928-f157ed46c2c7 01 Aug 2016 none MIT — Details →
v0.0.0-20160801122139-32dadb02df2f 01 Aug 2016 none MIT — Details →
v0.0.0-20160727070009-f9d14dda07b1 27 Jul 2016 none MIT — Details →
v0.0.0-20160727065923-8d5227f6329c 27 Jul 2016 none MIT — Details →
v0.0.0-20160727063531-67c92736ac30 27 Jul 2016 none MIT — Details →
v0.0.0-20160725174530-3dd00509ee1d 25 Jul 2016 none — — Details →
v0.0.0-20151117030957-7123e85b2442 17 Nov 2015 none — — Details →
v0.0.0-20150626160445-1fe094813ceb 26 Jun 2015 none — — Details →
v0.0.0-20150602234202-05a24e24fa8d 02 Jun 2015 none — — Details →
v0.0.0-20150602223451-d1f118e1d973 02 Jun 2015 none — — Details →
v0.0.0-20150602014843-19e44e47efc7 02 Jun 2015 none — — Details →

All 47 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/rifflock/lfshook

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/rifflock/lfshook

Is github.com/rifflock/lfshook safe to use?

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

Vulert scores github.com/rifflock/lfshook 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/rifflock/lfshook affected?

No. v0.0.0-20180920164130-b9218ef580f5, 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/rifflock/lfshook should I use?

v0.0.0-20180920164130-b9218ef580f5 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/rifflock/lfshook have?

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

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

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