Vulnerability Database · Maven · Package report

org.eclipse.jdt:ecj: vulnerability history, versions and safety

org.eclipse.jdt:ecj is a package in the Maven ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Maven 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 org.eclipse.jdt:ecj 3.46.100 i

Updated on 23 Oct 2026

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

Package health score 90/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 3.46.100 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1,037 packages i
  • Stars 239 i
  • Last release 1 month ago i
  • Licence EPL-2.0 i

Version list, release dates, licence and dependants published by Maven Central, 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 org.eclipse.jdt:ecj, 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.46.100 08 Sep 2026 none EPL-2.0 — Details →
3.46.0 05 Jun 2026 none EPL-2.0 — Details →
3.45.0 06 Mar 2026 none EPL-2.0 — Details →
3.44.0 05 Dec 2025 none EPL-2.0 — Details →
3.43.0 05 Sep 2025 none EPL-2.0 — Details →
3.42.0 07 Jun 2025 none EPL-2.0 — Details →
3.41.0 08 Mar 2025 none non-standard — Details →
3.40.0 01 Dec 2024 none non-standard — Details →
3.39.0 06 Sep 2024 none non-standard — Details →
3.38.0 07 Jun 2024 none non-standard — Details →
3.37.0 08 Mar 2024 none non-standard — Details →
3.36.0 03 Dec 2023 none non-standard — Details →
3.35.0 08 Sep 2023 none non-standard — Details →
3.34.0 09 Jun 2023 none non-standard — Details →
3.33.0 13 Mar 2023 none non-standard — Details →
3.32.0 06 Dec 2022 none non-standard — Details →
3.31.0 10 Sep 2022 none non-standard — Details →
3.30.0 14 Jun 2022 none non-standard — Details →
3.29.0 15 Mar 2022 none non-standard — Details →
3.28.0 06 Dec 2021 none non-standard — Details →
3.27.0 15 Sep 2021 none non-standard — Details →
3.26.0 14 Jun 2021 none non-standard — Details →
3.25.0 12 Mar 2021 none non-standard — Details →
3.24.0 13 Dec 2020 none non-standard — Details →
3.23.0 14 Sep 2020 none non-standard — Details →
3.22.0 15 Jun 2020 none non-standard — Details →
3.21.0 26 Mar 2020 none non-standard — Details →
3.20.0 17 Dec 2019 none non-standard — Details →
3.19.0 17 Sep 2019 none non-standard — Details →
3.18.0 17 Jun 2019 none non-standard — Details →
3.17.0 16 Mar 2019 none non-standard — Details →
3.16.0 19 Dec 2018 none non-standard — Details →
3.15.1 30 Oct 2018 none non-standard — Details →
3.15.0 25 Sep 2018 none non-standard — Details →
3.14.0 14 Jun 2018 none non-standard — Details →
3.13.102 12 Apr 2018 none non-standard — Details →
3.13.101 29 Mar 2018 none non-standard — Details →
3.13.100 20 Dec 2017 none non-standard — Details →
3.13.50 16 Nov 2017 none non-standard — Details →
3.13.0 17 Oct 2017 none non-standard — Details →
3.12.3 29 Mar 2017 none non-standard — Details →

All 41 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 org.eclipse.jdt:ecj

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 org.eclipse.jdt:ecj

Is org.eclipse.jdt:ecj safe to use?

Vulert has no vulnerabilities on record for org.eclipse.jdt:ecj in Maven 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 org.eclipse.jdt:ecj's Vulert package health score?

Vulert scores org.eclipse.jdt:ecj 90/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 org.eclipse.jdt:ecj affected?

No. 3.46.100, 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 org.eclipse.jdt:ecj should I use?

3.46.100 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 org.eclipse.jdt:ecj have?

0 vulnerabilities are recorded for org.eclipse.jdt:ecj in the Maven 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 org.eclipse.jdt:ecj vulnerabilities disclosed?

0 vulnerabilities were recorded for org.eclipse.jdt:ecj 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 org.eclipse.jdt:ecj 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 org.eclipse.jdt:ecj for upcoming vulnerabilities?

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