Vulnerability Database · Go · Package report

github.com/influxdata/tail: vulnerability history, versions and safety

github.com/influxdata/tail 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/influxdata/tail v1.0.0 i

Updated on 23 Oct 2026

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

Package health score 44/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v1.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 11 i
  • OpenSSF scorecard 1/10 i
  • Last release 125 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/influxdata/tail, 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.0.1-0.20241014115250-3e0015cb677a 14 Oct 2024 none MIT — Details →
v1.0.1-0.20241010210018-7b1551f18204 10 Oct 2024 none MIT — Details →
v1.0.1-0.20240719165826-3c9d721090d2 19 Jul 2024 none MIT — Details →
v1.0.1-0.20221209053931-97db2a1a2721 09 Dec 2022 none MIT — Details →
v0.0.0-20221130111531-19b97bffd978 30 Nov 2022 none MIT — Details →
v1.0.1-0.20221130111531-19b97bffd978 30 Nov 2022 none MIT — Details →
v1.0.1-0.20221116125329-ca3b55c4b8df 16 Nov 2022 none MIT — Details →
v0.0.0-20220120171240-b08fcc60453c 20 Jan 2022 none MIT — Details →
v1.0.1-0.20220120171240-b08fcc60453c 20 Jan 2022 none MIT — Details →
v0.0.0-20210707231403-b283181d1fa7 07 Jul 2021 none MIT — Details →
v1.0.1-0.20210707231403-b283181d1fa7 07 Jul 2021 none MIT — Details →
v1.0.1-0.20201208111917-9ddddda047d4 08 Dec 2020 none MIT — Details →
v1.0.1-0.20201104214644-a732c2948fb3 04 Nov 2020 none MIT — Details →
v1.0.1-0.20200707181643-03a791b270e4 07 Jul 2020 none MIT — Details →
v1.0.1-0.20200707024018-5a449acc01e2 07 Jul 2020 none MIT — Details →
v0.0.0-20180327235535-c43482518d41 27 Mar 2018 none MIT — Details →
v1.0.1-0.20180327235535-c43482518d41 27 Mar 2018 none MIT — Details →
v1.0.1-0.20180327235002-e3cde39d67e0 27 Mar 2018 none MIT — Details →
v1.0.1-0.20170814160653-37f427138745 14 Aug 2017 none MIT — Details →
v1.0.1-0.20170803230729-66928beff07e 03 Aug 2017 none MIT — Details →
v1.0.1-0.20170707194310-a927b6857fc7 07 Jul 2017 none MIT — Details →
v1.0.1-0.20170707194152-854fb555107b 07 Jul 2017 none MIT — Details →
v1.0.1-0.20170707191911-cd5bbb3d4d72 07 Jul 2017 none MIT — Details →
v1.0.1-0.20170707191547-2b56f8711f06 07 Jul 2017 none MIT — Details →
v0.0.0-20170420232535-a395bf99fe07 20 Apr 2017 none MIT — Details →
v1.0.1-0.20170420232535-a395bf99fe07 20 Apr 2017 none MIT — Details →
v1.0.1-0.20170329205032-e9ef7e826daf 29 Mar 2017 none MIT — Details →
v1.0.1-0.20170329202855-b4143c2b9991 29 Mar 2017 none MIT — Details →
v1.0.1-0.20170329202845-517cb795fd98 29 Mar 2017 none MIT — Details →
v1.0.1-0.20170321010826-2e7937785196 21 Mar 2017 none MIT — Details →
v1.0.1-0.20170321005007-669c44045ef6 21 Mar 2017 none MIT — Details →
v1.0.1-0.20170320003919-a294104811bb 20 Mar 2017 none MIT — Details →
v1.0.1-0.20170318212517-b0c08f203088 18 Mar 2017 none MIT — Details →
v1.0.1-0.20170305105554-89ee1afdf508 05 Mar 2017 none MIT — Details →
v1.0.1-0.20170207023346-faf842bde7ed 07 Feb 2017 none MIT — Details →
v1.0.1-0.20170207023204-33107f39d57e 07 Feb 2017 none MIT — Details →
v1.0.1-0.20170207021257-7c9bfffc210b 07 Feb 2017 none MIT — Details →
v1.0.1-0.20170207021211-46ed7f0315f3 07 Feb 2017 none MIT — Details →
v1.0.1-0.20161222030332-87e6317929c4 22 Dec 2016 none MIT — Details →
v1.0.1-0.20161214010615-74e17d03abd6 14 Dec 2016 none MIT — Details →
v1.0.1-0.20161125181710-915e5feba042 25 Nov 2016 none MIT — Details →
v1.0.1-0.20160909080724-bf39eb4f5114 09 Sep 2016 none MIT — Details →
v1.0.1-0.20160902201529-9c97d7511f34 02 Sep 2016 none MIT — Details →
v1.0.1-0.20160801065852-48cd00098ff2 01 Aug 2016 none MIT — Details →
v1.0.1-0.20160801065821-3ca1edc9ed33 01 Aug 2016 none MIT — Details →
v1.0.1-0.20160503002404-dbbd48186485 03 May 2016 none MIT — Details →
v1.0.0 28 Apr 2016 none MIT — Details →
v0.0.0-20160428001643-5d92327bc2b1 28 Apr 2016 none MIT — Details →
v0.0.0-20160427235903-c323fd4fa99e 27 Apr 2016 none MIT — Details →
v0.0.0-20160427232940-166d4e4826a0 27 Apr 2016 none MIT — Details →
v0.0.0-20160427001555-fff2f2d9e039 27 Apr 2016 none MIT — Details →
v0.0.0-20160426233749-9d956fd2bbf0 26 Apr 2016 none MIT — Details →
v0.0.0-20160426233013-865a91f5096d 26 Apr 2016 none MIT — Details →
v0.0.0-20160426231615-86ea7df4bc34 26 Apr 2016 none MIT — Details →
v0.0.0-20160426224746-34db8a6edfc8 26 Apr 2016 none MIT — Details →
v0.0.0-20160426222154-a7c1263528de 26 Apr 2016 none MIT — Details →
v0.0.0-20160426192322-26dc82c746b1 26 Apr 2016 none MIT — Details →
v0.0.0-20160426183020-308ca466808b 26 Apr 2016 none MIT — Details →
v0.0.0-20160426175750-04356b27e165 26 Apr 2016 none MIT — Details →
v0.0.0-20160426175605-425bce90fde6 26 Apr 2016 none MIT — Details →
v0.0.0-20160415000539-b2940955ab8b 15 Apr 2016 none MIT — Details →
v0.0.0-20160408233303-adca23eea0fe 08 Apr 2016 none MIT — Details →
v0.0.0-20160408232940-5e2d004af5a4 08 Apr 2016 none MIT — Details →
v0.0.0-20160408232940-ac5972aca8e9 08 Apr 2016 none MIT — Details →
v0.0.0-20160408195807-f4e225082618 08 Apr 2016 none MIT — Details →
v0.0.0-20160408184725-b58ee27c6635 08 Apr 2016 none MIT — Details →
v0.0.0-20151107005508-922a9f6f1796 07 Nov 2015 none MIT — Details →
v0.0.0-20131113010820-15d13d69b266 13 Nov 2013 none MIT — Details →
v2.10.6-bug100770-inotify-leak+incompatible 13 Nov 2013 none MIT — Details →

All 69 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/influxdata/tail

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/influxdata/tail

Is github.com/influxdata/tail safe to use?

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

Vulert scores github.com/influxdata/tail 44/100, which reads as risky. 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/influxdata/tail affected?

No. v1.0.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/influxdata/tail should I use?

v1.0.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/influxdata/tail have?

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

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

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