Vulnerability Database · Go · Package report

github.com/influxdata/influxdb1-client: vulnerability history, versions and safety

Q: How do I monitor github.com/influxdata/influxdb1-client for upcoming vulnerabilities?

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

github.com/influxdata/influxdb1-client is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/influxdata/influxdb1-client vulnerabilities

Vulert verdict on github.com/influxdata/influxdb1-client v0.0.0-20220302092344-a9ab5670611c i

Updated on 23 Oct 2026

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

Package health score 52/100

Security Minor issues
Maintenance Unmaintained
Popularity Niche
Community Quiet

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

Current release v0.0.0-20220302092344-a9ab5670611c — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Stars 191 i
OpenSSF scorecard 2/10 i
Last release 55 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/influxdata/influxdb1-client, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
v0.0.0-20220302092344-a9ab5670611c	02 Mar 2022	none	MIT	—	Details →
v2.0.0-20220302092344-a9ab5670611c+incompatible	02 Mar 2022	none	MIT	—	Details →
v0.0.0-20220302090925-8cd114df900e	02 Mar 2022	none	MIT	—	Details →
v0.0.0-20220302083831-2bbe214a3425	02 Mar 2022	none	MIT	—	Details →
v0.0.0-20220302065315-720b92ca52ba	02 Mar 2022	none	MIT	—	Details →
v0.0.0-20220302061501-1a68547ae730	02 Mar 2022	none	MIT	—	Details →
v0.0.0-20201203182823-27900d6a5b15	03 Dec 2020	none	MIT	—	Details →
v0.0.0-20200827194710-b269163b24ab	27 Aug 2020	none	MIT	—	Details →
v2.0.0-20200827194710-b269163b24ab+incompatible	27 Aug 2020	none	MIT	—	Details →
v0.0.0-20200730163929-c33ff87ddc0e	30 Jul 2020	none	MIT	—	Details →
v0.0.0-20200515024757-02f0bf5dbca3	15 May 2020	none	MIT	—	Details →
v0.0.0-20200512030928-2a12b7ac1f17	12 May 2020	none	MIT	—	Details →
v0.0.0-20191209144304-8bf82d3c094d	09 Dec 2019	none	MIT	—	Details →
v2.0.0-20191209144304-8bf82d3c094d+incompatible	09 Dec 2019	none	MIT	—	Details →
v0.0.0-20191122122105-db7b4d63c762	22 Nov 2019	none	MIT	—	Details →
v0.0.0-20190809212627-fc22c7df067e	09 Aug 2019	none	MIT	—	Details →
v0.0.0-20190809211812-581c91b8f41b	09 Aug 2019	none	MIT	—	Details →
v0.0.0-20190407163858-c6d6702cd1e1	07 Apr 2019	none	MIT	—	Details →
v0.0.0-20190402204710-8ff2fc3824fc	02 Apr 2019	none	MIT	—	Details →
v0.0.0-20190228152810-e5622a15865b	28 Feb 2019	none	MIT	—	Details →
v0.0.0-20190124185755-16c852ea613f	24 Jan 2019	none	MIT	—	Details →
v0.0.0-20190119191251-a9df3917e7ee	19 Jan 2019	none	MIT	—	Details →
v0.0.0-20190118215656-f8cdb5d5f175	18 Jan 2019	none	MIT	—	Details →
v0.0.0-20190112215518-e237d47d0fc8	12 Jan 2019	none	MIT	—	Details →
v0.0.0-20190112215408-96e0cd5d8fc0	12 Jan 2019	none	MIT	—	Details →
v0.0.0-20190112212842-614f9e1532ce	12 Jan 2019	none	MIT	—	Details →

All 26 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for github.com/influxdata/influxdb1-client

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/influxdb1-client

Is github.com/influxdata/influxdb1-client safe to use?

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

Vulert scores github.com/influxdata/influxdb1-client 52/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/influxdata/influxdb1-client affected?

No. v0.0.0-20220302092344-a9ab5670611c, 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/influxdb1-client should I use?

v0.0.0-20220302092344-a9ab5670611c 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/influxdb1-client have?

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

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

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