VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

rope: vulnerability history, versions and safety

rope is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 12 releases, from Apr 2018 to Jul 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 U1
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.

See all rope vulnerabilities

Vulert verdict on rope 1.15.0 i

Updated on 23 Oct 2026

Good news: 1.15.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 1.15.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 26 Jul 2018 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 104 packages i
  • Stars 2,244 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence LGPL-3.0-or-later 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 rope, 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
1.15.0 26 Sep 2026 none LGPL-3.0-or-later — Details →
1.14.0 12 Jul 2025 none LGPL-3.0-or-later — Details →
1.13.0 24 Mar 2024 none LGPL-3.0-or-later — Details →
1.12.0 18 Jan 2024 none LGPL-3.0-or-later — Details →
1.11.0 05 Nov 2023 none LGPL-3.0-or-later — Details →
1.10.0 28 Sep 2023 none LGPL-3.0-or-later — Details →
1.9.0 29 Jun 2023 none LGPL-3.0-or-later — Details →
1.8.0 05 May 2023 none LGPL-3.0-or-later — Details →
1.7.0 17 Jan 2023 none LGPL-3.0-or-later — Details →
1.6.0 15 Dec 2022 none LGPL-3.0-or-later — Details →
1.5.1 25 Nov 2022 none LGPL-3.0-or-later — Details →
1.5.0 22 Nov 2022 none LGPL-3.0-or-later — Details →
1.4.0 21 Oct 2022 none LGPL-3.0-or-later — Details →
1.3.0 29 Jul 2022 none LGPL-3.0-or-later — Details →
1.2.0 22 Jun 2022 none LGPL-3.0-or-later — Details →
1.1.1 25 May 2022 none LGPL-3.0-or-later — Details →
1.1.0 25 May 2022 none LGPL-3.0-or-later — Details →
1.0.0 07 Apr 2022 none LGPL-3.0-or-later — Details →
0.23.0 27 Feb 2022 none LGPL-3.0-or-later — Details →
0.22.0 22 Nov 2021 none LGPL-3.0-or-later — Details →
0.21.1 11 Nov 2021 none LGPL-3.0-or-later — Details →
0.21.0 18 Oct 2021 none LGPL-3.0-or-later — Details →
0.20.1 18 Sep 2021 none LGPL-3.0-or-later — Details →
0.20.0 18 Sep 2021 none LGPL-3.0-or-later — Details →
0.19.0 18 Apr 2021 none non-standard — Details →
0.18.0 07 Oct 2020 none non-standard — Details →
0.17.0 05 May 2020 none non-standard — Details →
0.16.0 11 Jan 2020 none non-standard — Details →
0.14.0 22 Mar 2019 none non-standard — Details →
0.12.0 11 Feb 2019 none non-standard — Details →
0.11.0 08 Aug 2018 none non-standard — Details →
0.10.7 23 Aug 2017 C1 U1 non-standard Yes Details →
0.10.6 22 Aug 2017 C1 U1 non-standard Yes Details →
0.10.5 23 Feb 2017 C1 U1 non-standard Yes Details →
0.10.4 22 Feb 2017 C1 U1 non-standard Yes Details →
0.10.3 29 Oct 2015 C1 U1 non-standard Yes Details →
0.10.2 22 May 2014 C1 U1 non-standard Yes Details →
0.10.1 22 May 2014 C1 U1 non-standard Yes Details →
0.10.0 22 May 2014 C1 U1 non-standard Yes Details →
0.9.4 16 May 2012 C1 U1 non-standard Yes Details →
0.9.3 04 Feb 2010 C1 U1 non-standard Yes Details →
0.9.2 19 Feb 2009 C1 U1 non-standard Yes Details →
0.2.0rc5 17 Jul 2006 C1 U1 — Yes Details →

All 43 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for rope

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2014-3539: Critical vulnerability in rope library 9.8 critical 0.11.0 26 Jul 2018
CVE-2014-3539: Remote Code Execution in rope N/A unrated 0.11.0 06 Apr 2018

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 rope

Is rope safe to use?

Vulert records 2 vulnerabilities for rope in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is rope's Vulert package health score?

Vulert scores rope 81/100, which reads as in good shape. 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 rope affected?

No. 1.15.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 rope should I use?

1.15.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 rope have?

2 vulnerabilities are recorded for rope in the PyPI ecosystem: 1 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new rope vulnerabilities disclosed?

0 vulnerabilities were recorded for rope in the last 12 months, and the oldest entry in this database dates to 06 Apr 2018. 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 rope 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 rope for upcoming vulnerabilities?

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