Vulnerability Database · npm · Package report
@influxdata/influxdb-client: vulnerability history, versions and safety
@influxdata/influxdb-client is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on @influxdata/influxdb-client 1.35.0 i
Updated on 23 Oct 2026
Good news: 1.35.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Niche
- Community Quiet
What to do: Stay on 1.35.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.35.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 1.35.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 157 packages i
- Stars 353 i
- OpenSSF scorecard 4/10 i
- Last release 26 months ago i
- Licence MIT i
Version list, release dates, licence and dependants published by the npm registry, 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 @influxdata/influxdb-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.
- 1.36.0-nightly.9028 02 Sep 2026
- 1.36.0-nightly.9017 01 Sep 2026
- 1.36.0-nightly.9010 01 Sep 2026
- 1.36.0-nightly.9000 01 Sep 2026
- 1.36.0-nightly.8990 01 Sep 2026
- 1.36.0-nightly.8979 01 Sep 2026
- 1.36.0-nightly.8958 01 Sep 2026
- 1.36.0-nightly.8941 01 Sep 2026
- 1.36.0-nightly.8916 01 Sep 2026
- 1.36.0-nightly.8887 01 Sep 2026
- 1.36.0-nightly.8853 01 Sep 2026
- 1.36.0-nightly.8813 08 Aug 2026
- 1.36.0-nightly.8799 04 Aug 2026
- 1.36.0-nightly.8786 04 Aug 2026
- 1.36.0-nightly.8769 04 Aug 2026
- 1.36.0-nightly.8756 01 Aug 2026
- 1.36.0-nightly.8742 01 Aug 2026
- 1.36.0-nightly.8727 01 Aug 2026
- 1.36.0-nightly.8706 01 Aug 2026
- 1.36.0-nightly.8680 01 Aug 2026
- 1.36.0-nightly.8651 01 Aug 2026
- 1.36.0-nightly.8619 01 Aug 2026
- 1.36.0-nightly.8586 01 Aug 2026
- 1.36.0-nightly.8543 24 Jul 2026
- 1.36.0-nightly.8536 24 Jul 2026
- 1.36.0-nightly.8523 01 Jul 2026
- 1.36.0-nightly.8510 01 Jul 2026
- 1.36.0-nightly.8493 01 Jul 2026
- 1.36.0-nightly.8472 01 Jul 2026
- 1.36.0-nightly.8447 01 Jul 2026
- 1.36.0-nightly.8418 01 Jul 2026
- 1.36.0-nightly.8393 30 Jun 2026
- 1.36.0-nightly.8384 30 Jun 2026
- 1.36.0-nightly.7576 21 Nov 2025
- 1.36.0-nightly.7497 18 Aug 2025
- 1.36.0-nightly.7482 18 Aug 2025
- 1.36.0-nightly.7469 18 Aug 2025
- 1.36.0-nightly.7460 18 Aug 2025
- 1.36.0-nightly.7445 01 Aug 2025
- 1.36.0-nightly.7431 01 Aug 2025
- 1.36.0-nightly.7421 01 Aug 2025
- 1.36.0-nightly.7393 25 Jul 2025
- 1.36.0-nightly.7345 16 Jun 2025
- 1.36.0-nightly.7344 16 Jun 2025
- 1.36.0-nightly.7195 14 Feb 2025
- 1.36.0-nightly.7186 14 Feb 2025
- 1.36.0-nightly.7177 14 Feb 2025
- 1.36.0-nightly.7164 14 Feb 2025
- 1.36.0-nightly.7151 14 Feb 2025
- 1.36.0-nightly.7134 14 Feb 2025
- 1.36.0-nightly.7121 14 Feb 2025
- 1.36.0-nightly.7108 14 Feb 2025
- 1.36.0-nightly.6999 07 Jan 2025
- 1.36.0-nightly.6994 07 Jan 2025
- 1.36.0-nightly.6985 07 Jan 2025
- 1.36.0-nightly.6976 07 Jan 2025
- 1.36.0-nightly.6967 07 Jan 2025
- 1.36.0-nightly.6962 06 Jan 2025
- 1.36.0-nightly.6961 06 Jan 2025
- 1.36.0-nightly.6920 05 Dec 2024
- 1.36.0-nightly.6915 05 Dec 2024
- 1.36.0-nightly.6902 05 Dec 2024
- 1.36.0-nightly.6901 05 Dec 2024
- 1.36.0-nightly.6896 05 Dec 2024
- 1.36.0-nightly.6887 05 Dec 2024
- 1.36.0-nightly.6882 05 Dec 2024
- 1.36.0-nightly.6877 05 Dec 2024
- 1.36.0-nightly.6824 19 Nov 2024
- 1.36.0-nightly.6815 13 Nov 2024
- 1.36.0-nightly.6814 13 Nov 2024
- 1.36.0-nightly.6801 13 Nov 2024
- 1.36.0-nightly.6800 13 Nov 2024
- 1.36.0-nightly.6798 13 Nov 2024
- 1.36.0-nightly.6777 13 Nov 2024
- 1.36.0-nightly.6776 13 Nov 2024
- 1.36.0-nightly.6771 13 Nov 2024
- 1.36.0-nightly.6766 13 Nov 2024
- 1.36.0-nightly.6709 02 Oct 2024
- 1.36.0-nightly.6704 02 Oct 2024
- 1.36.0-nightly.6703 02 Oct 2024
- 1.36.0-nightly.6702 02 Oct 2024
- 1.36.0-nightly.6701 02 Oct 2024
- 1.36.0-nightly.6696 02 Oct 2024
- 1.36.0-nightly.6695 02 Oct 2024
- 1.36.0-nightly.6694 02 Oct 2024
- 1.36.0-nightly.6693 02 Oct 2024
- 1.36.0-nightly.6672 02 Oct 2024
- 1.36.0-nightly.6611 24 Sep 2024
- 1.36.0-nightly.6602 13 Sep 2024
- 1.36.0-nightly.6593 02 Sep 2024
- 1.36.0-nightly.6592 02 Sep 2024
- 1.36.0-nightly.6583 02 Sep 2024
- 1.36.0-nightly.6581 02 Sep 2024
- 1.36.0-nightly.6582 02 Sep 2024
- 1.36.0-nightly.6580 02 Sep 2024
- 1.36.0-nightly.6575 02 Sep 2024
- 1.36.0-nightly.6574 02 Sep 2024
- 1.36.0-nightly.6561 02 Sep 2024
- 1.36.0-nightly.6548 02 Sep 2024
- 1.36.0-nightly.6495 19 Aug 2024
- 1.36.0-nightly.6490 15 Aug 2024
- 1.35.0 15 Aug 2024
- 1.35.0-nightly.6481 14 Aug 2024
- 1.35.0-nightly.6456 13 Aug 2024
- 1.35.0-nightly.6451 13 Aug 2024
- 1.35.0-nightly.6450 13 Aug 2024
- 1.35.0-nightly.6444 13 Aug 2024
- 1.35.0-nightly.6443 13 Aug 2024
- 1.35.0-nightly.6438 13 Aug 2024
- 1.35.0-nightly.6433 13 Aug 2024
- 1.35.0-nightly.6428 13 Aug 2024
- 1.35.0-nightly.6363 05 Aug 2024
- 1.35.0-nightly.6350 05 Aug 2024
- 1.35.0-nightly.6341 05 Aug 2024
- 1.35.0-nightly.6336 05 Aug 2024
- 1.35.0-nightly.6327 05 Aug 2024
- 1.35.0-nightly.6321 05 Aug 2024
- 1.35.0-nightly.6322 05 Aug 2024
- 1.35.0-nightly.6320 05 Aug 2024
- 1.35.0-nightly.6275 05 Aug 2024
The newest 120 of 783 versions Vulert tracks. 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 @influxdata/influxdb-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
Questions
About @influxdata/influxdb-client
Is @influxdata/influxdb-client safe to use?
Vulert has no vulnerabilities on record for @influxdata/influxdb-client in npm 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 @influxdata/influxdb-client's Vulert package health score?
Vulert scores @influxdata/influxdb-client 63/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 @influxdata/influxdb-client affected?
No. 1.35.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 @influxdata/influxdb-client should I use?
1.35.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 @influxdata/influxdb-client have?
0 vulnerabilities are recorded for @influxdata/influxdb-client in the npm 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 @influxdata/influxdb-client vulnerabilities disclosed?
0 vulnerabilities were recorded for @influxdata/influxdb-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 @influxdata/influxdb-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 @influxdata/influxdb-client for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @influxdata/influxdb-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.