VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

ete3: vulnerability history, versions and safety

ete3 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.

See all ete3 vulnerabilities

Vulert verdict on ete3 3.1.3 i

Updated on 23 Oct 2026

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

Package health score 65/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

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

  • Current release 3.1.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 283 packages i
  • Stars 884 i
  • OpenSSF scorecard 3/10 i
  • Last release 41 months ago i
  • Licence GPL-3.0 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 ete3, 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
3.1.3 02 May 2023 none GPL-3.0 — Details →
3.1.2 30 Aug 2020 none GPL-3.0 — Details →
3.1.1 03 Nov 2017 none GPL-3.0 — Details →
3.0.0b35 18 Mar 2016 none GPL-3.0 — Details →
3.0.0b34 18 Mar 2016 none GPL-3.0 — Details →
3.0.0b33 11 Mar 2016 none GPL-3.0 — Details →
3.0.0b32 12 Feb 2016 none GPL-3.0 — Details →
3.0.0b31 12 Feb 2016 none GPL-3.0 — Details →
3.0.0b30 11 Feb 2016 none GPL-3.0 — Details →
3.0.0b29 20 Jan 2016 none GPL-3.0 — Details →
3.0.0b27 18 Jan 2016 none GPL-3.0 — Details →
3.0.0b26 18 Jan 2016 none GPL-3.0 — Details →
3.0.0b24 18 Jan 2016 none GPL-3.0 — Details →
3.0.0b23 18 Jan 2016 none GPL-3.0 — Details →
3.0.0b22 18 Jan 2016 none GPL-3.0 — Details →
3.0.0b21 16 Jan 2016 none GPL-3.0 — Details →
3.0.0b20 16 Jan 2016 none GPL-3.0 — Details →
3.0.0b18 13 Jan 2016 none GPL-3.0 — Details →
3.0.0b17 21 Dec 2015 none GPL-3.0 — Details →
3.0.0b16 19 Dec 2015 none GPL-3.0 — Details →
3.0.0b15 17 Dec 2015 none GPL-3.0 — Details →
3.0.0b14 07 Dec 2015 none GPL-3.0 — Details →
3.0.0b13 07 Dec 2015 none GPL-3.0 — Details →
3.0.0b12 29 Nov 2015 none GPL-3.0 — Details →
3.0.0b11 28 Nov 2015 none GPL-3.0 — Details →
3.0.0b10 28 Nov 2015 none GPL-3.0 — Details →
3.0.0b9 28 Nov 2015 none GPL-3.0 — Details →
3.0.0b8 28 Nov 2015 none GPL-3.0 — Details →
3.0.0b7 24 Nov 2015 none GPL-3.0 — Details →

All 29 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 ete3

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 ete3

Is ete3 safe to use?

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

Vulert scores ete3 65/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 ete3 affected?

No. 3.1.3, 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 ete3 should I use?

3.1.3 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 ete3 have?

0 vulnerabilities are recorded for ete3 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 ete3 vulnerabilities disclosed?

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

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