Vulnerability Database · PyPI · Package report

plotly: vulnerability history, versions and safety

plotly is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the PyPI 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 plotly 7.1.0 i

Updated on 23 Oct 2026

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

Package health score 91/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 7.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 8,478 packages i
  • Stars 18,851 i
  • OpenSSF scorecard 6/10 i
  • Last release 1 month ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, 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 plotly, 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
7.1.0 15 Sep 2026 none MIT — Details →
7.0.0 25 Aug 2026 none MIT — Details →
7.0.0rc0 29 Jul 2026 none MIT — Details →
6.9.0 09 Jul 2026 none MIT — Details →
6.8.0 03 Jun 2026 none MIT — Details →
6.7.0 09 Apr 2026 none MIT — Details →
6.6.0 02 Mar 2026 none non-standard — Details →
6.5.2 14 Jan 2026 none non-standard — Details →
6.5.1 07 Jan 2026 none non-standard — Details →
6.5.0 17 Nov 2025 none non-standard — Details →
6.4.0 04 Nov 2025 none non-standard — Details →
6.3.1 02 Oct 2025 none non-standard — Details →
6.3.0 12 Aug 2025 none non-standard — Details →
6.2.0 26 Jun 2025 none non-standard — Details →
6.1.2 27 May 2025 none non-standard — Details →
6.1.1 20 May 2025 none non-standard — Details →
6.1.0 15 May 2025 none non-standard — Details →
6.1.0rc0 02 May 2025 none non-standard — Details →
6.1.0b0 31 Mar 2025 none non-standard — Details →
6.0.1 17 Mar 2025 none non-standard — Details →
6.0.0 28 Jan 2025 none MIT — Details →
6.0.0rc0 27 Nov 2024 none MIT — Details →
5.24.1 12 Sep 2024 none MIT — Details →
5.24.0 29 Aug 2024 none MIT — Details →
5.23.0 23 Jul 2024 none MIT — Details →
5.22.0 01 May 2024 none MIT — Details →
5.21.0 17 Apr 2024 none MIT — Details →
5.20.0 13 Mar 2024 none MIT — Details →
5.19.0 15 Feb 2024 none MIT — Details →
5.18.0 25 Oct 2023 none MIT — Details →
5.17.0 15 Sep 2023 none MIT — Details →
5.16.1 16 Aug 2023 none MIT — Details →
5.16.0 11 Aug 2023 none MIT — Details →
5.15.0 08 Jun 2023 none MIT — Details →
5.14.1 05 Apr 2023 none MIT — Details →
5.14.0 29 Mar 2023 none MIT — Details →
5.13.1 24 Feb 2023 none MIT — Details →
5.13.0 23 Jan 2023 none MIT — Details →
5.12.0 13 Jan 2023 none MIT — Details →
5.11.0 27 Oct 2022 none MIT — Details →
5.10.0 11 Aug 2022 none MIT — Details →
5.9.0 24 Jun 2022 none MIT — Details →
5.8.2 10 Jun 2022 none MIT — Details →
5.8.1 08 Jun 2022 none MIT — Details →
5.8.0 11 May 2022 none MIT — Details →
5.7.0 05 Apr 2022 none MIT — Details →
5.6.0 09 Feb 2022 none MIT — Details →
5.5.0 21 Dec 2021 none MIT — Details →
5.4.0 15 Nov 2021 none MIT — Details →
5.3.1 01 Sep 2021 none MIT — Details →
5.3.0 30 Aug 2021 none MIT — Details →
5.2.2 23 Aug 2021 none MIT — Details →
5.2.1 14 Aug 2021 none MIT — Details →
5.2.0 13 Aug 2021 none MIT — Details →
5.1.0 28 Jun 2021 none MIT — Details →
5.0.0 21 Jun 2021 none MIT — Details →
5.0.0rc2 07 Jun 2021 none MIT — Details →
5.0.0rc1 31 May 2021 none MIT — Details →
4.14.3 12 Jan 2021 none MIT — Details →
4.14.2 11 Jan 2021 none MIT — Details →
4.14.1 09 Dec 2020 none MIT — Details →
4.14.0 07 Dec 2020 none MIT — Details →
4.13.0 23 Nov 2020 none MIT — Details →
4.12.0 23 Oct 2020 none MIT — Details →
4.11.0 01 Oct 2020 none MIT — Details →
4.10.0 10 Sep 2020 none MIT — Details →
4.9.0 16 Jul 2020 none MIT — Details →
4.9.0rc1 15 Jul 2020 none MIT — Details →
4.8.2 26 Jun 2020 none MIT — Details →
4.8.1 29 May 2020 none MIT — Details →
4.8.0 26 May 2020 none MIT — Details →
4.7.1 08 May 2020 none MIT — Details →
4.7.0 06 May 2020 none MIT — Details →
4.6.0 01 Apr 2020 none MIT — Details →
4.5.4 11 Mar 2020 none MIT — Details →
4.5.3 06 Mar 2020 none MIT — Details →
4.5.2 25 Feb 2020 none MIT — Details →
4.5.1 19 Feb 2020 none MIT — Details →
4.5.0 22 Jan 2020 none MIT — Details →
4.5.0rc1 22 Jan 2020 none MIT — Details →
4.4.1 10 Dec 2019 none MIT — Details →
4.4.0 10 Dec 2019 none MIT — Details →
4.3.0 12 Nov 2019 none MIT — Details →
4.2.1 18 Oct 2019 none MIT — Details →
4.2.0 16 Oct 2019 none MIT — Details →
4.1.1 03 Sep 2019 none MIT — Details →
4.1.0 07 Aug 2019 none MIT — Details →
4.1.0rc3 06 Aug 2019 none MIT — Details →
4.1.0rc2 06 Aug 2019 none MIT — Details →
4.1.0rc1 04 Aug 2019 none MIT — Details →
4.0.0 16 Jul 2019 none MIT — Details →
4.0.0rc1 09 Jul 2019 none MIT — Details →
4.0.0a10 08 Jul 2019 none MIT — Details →
4.0.0a9 04 Jul 2019 none MIT — Details →
4.0.0a8 01 Jul 2019 none MIT — Details →
4.0.0a7 01 Jul 2019 none MIT — Details →
4.0.0a6 01 Jul 2019 none MIT — Details →
4.0.0a5 01 Jul 2019 none MIT — Details →
4.0.0a4 20 Jun 2019 none MIT — Details →
4.0.0a3 18 Jun 2019 none MIT — Details →
4.0.0a2 15 Jun 2019 none — — Details →
4.0.0a1 15 Jun 2019 none — — Details →
3.10.0 31 May 2019 none — — Details →
3.10.0rc1 29 May 2019 none — — Details →
3.9.0 06 May 2019 none — — Details →
3.9.0rc1 06 May 2019 none — — Details →
3.8.1 19 Apr 2019 none — — Details →
3.8.0 15 Apr 2019 none — — Details →
3.8.0rc1 12 Apr 2019 none — — Details →
3.7.1 19 Mar 2019 none — — Details →
3.7.0 08 Mar 2019 none — — Details →
3.7.0rc1 07 Mar 2019 none — — Details →
3.6.1 08 Feb 2019 none — — Details →
3.6.0 01 Feb 2019 none — — Details →
3.6.0rc1 26 Jan 2019 none — — Details →
3.5.0 04 Jan 2019 none — — Details →
3.5.0rc1 03 Jan 2019 none — — Details →
3.4.2 23 Nov 2018 none — — Details →
3.4.1 09 Nov 2018 none — — Details →
3.4.1rc1 07 Nov 2018 none — — Details →

The newest 120 of 320 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 plotly

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 plotly

Is plotly safe to use?

Vulert has no vulnerabilities on record for plotly in PyPI 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 plotly's Vulert package health score?

Vulert scores plotly 91/100, which reads as healthy. 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 plotly affected?

No. 7.1.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 plotly should I use?

7.1.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 plotly have?

0 vulnerabilities are recorded for plotly in the PyPI 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 plotly vulnerabilities disclosed?

0 vulnerabilities were recorded for plotly 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 plotly 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 plotly for upcoming vulnerabilities?

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