Vulnerability Database · Go · Package report

github.com/apex/log: vulnerability history, versions and safety

github.com/apex/log 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/apex/log v1.9.0 i

Updated on 23 Oct 2026

Good news: v1.9.0, 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 v1.9.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.9.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v1.9.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,373 i
  • OpenSSF scorecard 2/10 i
  • Last release 74 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/apex/log, 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
v1.9.1-0.20231011205830-7280ce65c65a 11 Oct 2023 none MIT — Details →
v0.0.0-20200818134502-8da83152b5d6 18 Aug 2020 none MIT — Details →
v1.9.1-0.20200818134502-8da83152b5d6 18 Aug 2020 none MIT — Details →
v1.9.1-0.20200818102134-3a286a68b4dc 18 Aug 2020 none MIT — Details →
v1.9.1-0.20200818074053-2e51804d3963 18 Aug 2020 none MIT — Details →
v1.9.0 18 Aug 2020 none MIT — Details →
v1.8.1-0.20200817094143-421394d88c94 17 Aug 2020 none MIT — Details →
v1.8.1-0.20200812224917-55b535718b57 12 Aug 2020 none MIT — Details →
v1.8.0 05 Aug 2020 none MIT — Details →
v1.7.2-0.20200805104159-d6b7f1edde21 05 Aug 2020 none MIT — Details →
v1.7.1 05 Aug 2020 none MIT — Details →
v1.7.0 03 Aug 2020 none MIT — Details →
v1.6.0 13 Jul 2020 none MIT — Details →
v1.5.0 11 Jul 2020 none MIT — Details →
v1.4.1-0.20200711131616-452a4d9de886 11 Jul 2020 none MIT — Details →
v1.4.1-0.20200710115502-ffc41c1d1b33 10 Jul 2020 none MIT — Details →
v1.4.1-0.20200710114705-c907318d562b 10 Jul 2020 none MIT — Details →
v1.4.0 16 Jun 2020 none MIT — Details →
v1.3.1-0.20200616105656-c6d0f24fc845 16 Jun 2020 none MIT — Details →
v1.3.0 26 May 2020 none MIT — Details →
v1.2.0 26 May 2020 none MIT — Details →
v1.1.4 22 Apr 2020 none MIT — Details →
v1.1.3 22 Apr 2020 none MIT — Details →
v0.0.0-20200129140850-bef999bc8ce8 29 Jan 2020 none MIT — Details →
v1.1.2 29 Jan 2020 none MIT — Details →
v0.0.0-20190827100214-baa5455d1012 27 Aug 2019 none MIT — Details →
v1.1.2-0.20190827100214-baa5455d1012 27 Aug 2019 none MIT — Details →
v0.0.0-20190624134102-295021f518f7 24 Jun 2019 none MIT — Details →
v1.1.1 24 Jun 2019 none MIT — Details →
v1.1.1-0.20190617123514-064e581013a5 17 Jun 2019 none MIT — Details →
v0.0.0-20181011164637-d6c5facec1f2 11 Oct 2018 none MIT — Details →
v1.1.1-0.20181011164637-d6c5facec1f2 11 Oct 2018 none MIT — Details →
v0.0.0-20180702155952-941dea75d3eb 02 Jul 2018 none MIT — Details →
v1.1.0 02 Jul 2018 none MIT — Details →
v0.0.0-20180118050619-ff0f66940b82 18 Jan 2018 none MIT — Details →
v1.0.1-0.20180118050619-ff0f66940b82 18 Jan 2018 none MIT — Details →
v1.0.1-0.20180118043647-29fc76b07a83 18 Jan 2018 none MIT — Details →
v0.0.0-20180117203512-17c1d7658c4e 17 Jan 2018 none MIT — Details →
v1.0.1-0.20180117203512-17c1d7658c4e 17 Jan 2018 none MIT — Details →
v0.0.0-20171226182705-bf81de4b2280 26 Dec 2017 none MIT — Details →
v1.0.1-0.20171226182705-bf81de4b2280 26 Dec 2017 none MIT — Details →
v1.0.1-0.20171226045026-bbcce6279c0d 26 Dec 2017 none MIT — Details →
v0.0.0-20170726180745-0296d6eb16bb 26 Jul 2017 none MIT — Details →
v1.0.0 26 Jul 2017 none MIT — Details →
v0.0.0-20170720193420-d9b960447bfa 20 Jul 2017 none MIT — Details →
v0.0.0-20170720183523-087239faff55 20 Jul 2017 none MIT — Details →
v0.0.0-20170521205426-8f3a15d95392 21 May 2017 none MIT — Details →
v0.0.0-20170506225138-7259ed75bd8d 06 May 2017 none MIT — Details →
v0.0.0-20170427190657-603945f16991 27 Apr 2017 none MIT — Details →
v0.0.0-20170412164658-a0bcece0a725 12 Apr 2017 none MIT — Details →
v0.0.0-20170412164342-0530cf591101 12 Apr 2017 none MIT — Details →
v0.0.0-20170222070341-a97903d84569 22 Feb 2017 none MIT — Details →
v0.0.0-20170222042259-3339a4318c4c 22 Feb 2017 none MIT — Details →
v0.0.0-20170216004756-fac6c51185bc 16 Feb 2017 none MIT — Details →
v0.0.0-20170215222736-77d8f9c0f26a 15 Feb 2017 none MIT — Details →
v0.0.0-20170126183024-afb2e76037a5 26 Jan 2017 none MIT — Details →
v0.0.0-20170126181533-89ce6f11b2dc 26 Jan 2017 none MIT — Details →
v0.0.0-20161221001535-f0aad537c25e 21 Dec 2016 none MIT — Details →
v0.0.0-20161220235703-07bdde05c100 20 Dec 2016 none MIT — Details →
v0.0.0-20161218223524-51632129bde5 18 Dec 2016 none MIT — Details →
v0.0.0-20161214180122-994011249d68 14 Dec 2016 none MIT — Details →
v0.0.0-20160905151304-4ea85e918cc8 05 Sep 2016 none MIT — Details →
v0.0.0-20160905151231-42b454a06d71 05 Sep 2016 none MIT — Details →
v0.0.0-20160804142100-8eba30e44295 04 Aug 2016 none MIT — Details →
v0.0.0-20160721172613-2dafa85a923a 21 Jul 2016 none MIT — Details →
v0.0.0-20160716152336-17e941aeaa64 16 Jul 2016 none MIT — Details →
v0.0.0-20160716041830-cc8db835f4f1 16 Jul 2016 none MIT — Details →
v0.0.0-20160608212515-b1e791337602 08 Jun 2016 none MIT — Details →
v0.0.0-20160524203224-a999c1b29c98 24 May 2016 none MIT — Details →
v0.0.0-20160519202103-56b598dd62b8 19 May 2016 none MIT — Details →
v0.0.0-20160429161324-c20bfcdb771b 29 Apr 2016 none MIT — Details →
v0.0.0-20160418142454-560a983048f4 18 Apr 2016 none MIT — Details →
v0.0.0-20160416192700-707788e1e5ea 16 Apr 2016 none MIT — Details →
v0.0.0-20160414194602-bf54a9c88ad2 14 Apr 2016 none MIT — Details →
v0.0.0-20160229211424-a43e30f42fc3 29 Feb 2016 none MIT — Details →
v0.0.0-20160127132855-81a19e5c0054 27 Jan 2016 none MIT — Details →
v0.0.0-20160127124821-7bd718bbfa8b 27 Jan 2016 none MIT — Details →
v0.0.0-20160125201922-bfe8c3f75160 25 Jan 2016 none MIT — Details →
v0.0.0-20160117233535-0df6dd6f3beb 17 Jan 2016 none MIT — Details →
v0.0.0-20160114152710-02bedee0fb94 14 Jan 2016 none MIT — Details →
v0.0.0-20151224172158-68dfb102958d 24 Dec 2015 none MIT — Details →
v0.0.0-20151223224852-97d7815d77a7 23 Dec 2015 none MIT — Details →
v0.0.0-20151221202627-242e996f8e50 21 Dec 2015 none MIT — Details →

All 83 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/apex/log

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/apex/log

Is github.com/apex/log safe to use?

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

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

No. v1.9.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/apex/log should I use?

v1.9.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/apex/log have?

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

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

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