VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/kataras/golog: vulnerability history, versions and safety

github.com/kataras/golog 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.

See all github.com/kataras/golog vulnerabilities

Vulert verdict on github.com/kataras/golog v0.2.0 i

Updated on 23 Oct 2026

Good news: v0.2.0, the version you would install today, has no known vulnerabilities.

Package health score 73/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • 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 339 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month ago i
  • Licence BSD-3-Clause 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/kataras/golog, 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.2.1-0.20261005094119-13ba24aaa3c5 05 Oct 2026 none BSD-3-Clause — Details →
v0.2.0 11 Sep 2026 none BSD-3-Clause — Details →
v0.1.16-0.20260115122621-768605c801e1 15 Jan 2026 none BSD-3-Clause — Details →
v0.1.15 24 Aug 2025 none BSD-3-Clause — Details →
v0.1.15-0.20250824075244-b1529551b5f1 24 Aug 2025 none BSD-3-Clause — Details →
v0.1.14 24 Aug 2025 none BSD-3-Clause — Details →
v0.1.13 29 Mar 2025 none BSD-3-Clause — Details →
v0.1.13-0.20240424144420-a8efabd46b9e 24 Apr 2024 none BSD-3-Clause — Details →
v0.1.12 24 Apr 2024 none BSD-3-Clause — Details →
v0.1.12-0.20240121092228-cc1dbac0b907 21 Jan 2024 none BSD-3-Clause — Details →
v0.1.11 01 Nov 2023 none BSD-3-Clause — Details →
v0.1.9-0.20231101183446-ec2064d8b0b0 01 Nov 2023 none BSD-3-Clause — Details →
v0.1.9 24 Jun 2023 none BSD-3-Clause — Details →
v0.1.9-0.20230624202029-74c7c01c8d74 24 Jun 2023 none BSD-3-Clause — Details →
v0.1.9-0.20230624201804-fa0b1afcdfb0 24 Jun 2023 none BSD-3-Clause — Details →
v0.1.9-0.20230624201546-ab1356bf4c0d 24 Jun 2023 none BSD-3-Clause — Details →
v0.1.9-0.20221224062154-5890d89b09d5 24 Dec 2022 none BSD-3-Clause — Details →
v0.1.8 29 Oct 2022 none BSD-3-Clause — Details →
v0.1.8-0.20220920151453-350ad62100f4 20 Sep 2022 none BSD-3-Clause — Details →
v0.1.8-0.20220718173637-5ca7ba3c36f6 18 Jul 2022 none BSD-3-Clause — Details →
v0.1.7 13 Feb 2021 none BSD-3-Clause — Details →
v0.1.6 09 Dec 2020 none BSD-3-Clause — Details →
v0.1.6-0.20201201221444-133471d4f4c6 01 Dec 2020 none BSD-3-Clause — Details →
v0.1.6-0.20201201083027-06b93e3b74cb 01 Dec 2020 none BSD-3-Clause — Details →
v0.1.6-0.20200906220535-cef6d14c2033 06 Sep 2020 none BSD-3-Clause — Details →
v0.1.5 06 Sep 2020 none BSD-3-Clause — Details →
v0.1.4 06 Sep 2020 none BSD-3-Clause — Details →
v0.1.3 06 Sep 2020 none BSD-3-Clause — Details →
v0.1.2 15 Aug 2020 none BSD-3-Clause — Details →
v0.1.1 15 Aug 2020 none BSD-3-Clause — Details →
v0.0.19 14 Aug 2020 none BSD-3-Clause — Details →
v0.1.0 14 Aug 2020 none BSD-3-Clause — Details →
v0.0.19-0.20200619031135-459a30fcb67a 19 Jun 2020 none BSD-3-Clause — Details →
v0.0.18 09 Jun 2020 none BSD-3-Clause — Details →
v0.0.17 09 Jun 2020 none BSD-3-Clause — Details →
v0.0.16 06 Jun 2020 none BSD-3-Clause — Details →
v0.0.15 17 May 2020 none BSD-3-Clause — Details →
v0.0.14 17 May 2020 none BSD-3-Clause — Details →
v0.0.14-0.20200517185005-6850998fc49a 17 May 2020 none BSD-3-Clause — Details →
v0.0.13 29 Apr 2020 none BSD-3-Clause — Details →
v0.0.12 27 Apr 2020 none BSD-3-Clause — Details →
v0.0.11 26 Apr 2020 none BSD-3-Clause — Details →
v0.0.11-0.20200426004835-fccaa50d3533 26 Apr 2020 none BSD-3-Clause — Details →
v0.0.11-0.20191222150202-6c00b7bb83e5 22 Dec 2019 none BSD-3-Clause — Details →
v0.0.10 12 Dec 2019 none BSD-3-Clause — Details →
v0.0.9 16 Oct 2019 none BSD-3-Clause — Details →
v0.0.0-20190624001437-99c81de45f40 24 Jun 2019 none BSD-3-Clause — Details →
v0.0.0-20190620222301-4851375e24d4 20 Jun 2019 none BSD-3-Clause — Details →
v0.0.0-20181017085856-bab903f801af 17 Oct 2018 none BSD-3-Clause — Details →
v0.0.0-20180321173939-03be10146386 21 Mar 2018 none BSD-3-Clause — Details →
v0.0.0-20180311153849-dd676348ce75 11 Mar 2018 none BSD-3-Clause — Details →
v0.0.0-20180108072316-85424b54aeb6 08 Jan 2018 none BSD-3-Clause — Details →
v0.0.0-20170811121246-2ed680e7b1f3 11 Aug 2017 none BSD-3-Clause — Details →
v0.0.0-20170804160814-30109a297fcf 04 Aug 2017 none BSD-3-Clause — Details →
v0.0.0-20170802120918-e73fe6622c2b 02 Aug 2017 none BSD-3-Clause — Details →
v0.0.0-20170802012040-8fb26c26481a 02 Aug 2017 none BSD-3-Clause — Details →
v0.0.0-20170730160837-5982a8e10bd1 30 Jul 2017 none BSD-3-Clause — Details →
v0.0.0-20170728150824-ef5bc1d282ec 28 Jul 2017 none BSD-3-Clause — Details →
v0.0.0-20170727115810-98764ae5998c 27 Jul 2017 none BSD-3-Clause — Details →
v0.0.0-20170726115440-d6bddd509262 26 Jul 2017 none BSD-3-Clause — Details →
v0.0.0-20170726113853-f28891140be2 26 Jul 2017 none BSD-3-Clause — Details →

All 61 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/kataras/golog

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/kataras/golog

Is github.com/kataras/golog safe to use?

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

Vulert scores github.com/kataras/golog 73/100, which reads as in good shape. 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/kataras/golog 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/kataras/golog 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/kataras/golog have?

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

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

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