VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.eclipse.collections:eclipse-collections: vulnerability history, versions and safety

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

See all org.eclipse.collections:eclipse-collections vulnerabilities

Vulert verdict on org.eclipse.collections:eclipse-collections 13.0.0 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Moderate

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

  • Current release 13.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 753 packages i
  • Stars 2,659 i
  • OpenSSF scorecard 4/10 i
  • Last release 15 months ago i
  • Licence non-standard 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.collections:eclipse-collections, 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
13.0.0 23 Jun 2025 none non-standard — Details →
13.0.0.M1 21 Jun 2025 none non-standard — Details →
12.0.0 20 Jun 2025 none non-standard — Details →
12.0.0.M21 18 Jun 2025 none non-standard — Details →
12.0.0.M20.JDK11 15 Jun 2025 none non-standard — Details →
12.0.0.M20.JDK17 15 Jun 2025 none non-standard — Details →
12.0.0.M3 28 Aug 2023 none non-standard — Details →
12.0.0.M2 17 Jul 2023 none non-standard — Details →
12.0.0.M1 08 Feb 2023 none non-standard — Details →
11.1.0 05 Jul 2022 none non-standard — Details →
11.1.0.M2 28 Jun 2022 none non-standard — Details →
11.1.0.M1 21 Jun 2022 none non-standard — Details →
11.0.0 23 Nov 2021 none non-standard — Details →
11.0.0.M6 04 Nov 2021 none non-standard — Details →
11.0.0.M5 29 Oct 2021 none non-standard — Details →
11.0.0.M3 14 Jul 2021 none non-standard — Details →
11.0.0.M2 18 Mar 2021 none non-standard — Details →
11.0.0.M1 02 Nov 2020 none non-standard — Details →
10.4.0 20 Aug 2020 none non-standard — Details →
10.3.0 07 Aug 2020 none non-standard — Details →
10.3.0.M5 30 Jul 2020 none non-standard — Details →
10.3.0.M4 16 Jul 2020 none non-standard — Details →
10.3.0.M3 15 Jul 2020 none non-standard — Details →
10.3.0.M2 15 Jul 2020 none non-standard — Details →
10.3.0.M1 03 Jul 2020 none non-standard — Details →
10.2.0 11 Feb 2020 none non-standard — Details →
10.2.0.M1 29 Jan 2020 none non-standard — Details →
10.1.0 04 Dec 2019 none non-standard — Details →
10.1.0.M2 23 Nov 2019 none non-standard — Details →
10.0.0 12 Jul 2019 none non-standard — Details →
10.0.0.M3 03 May 2019 none non-standard — Details →
10.0.0.M2 18 Sep 2018 none non-standard — Details →
9.2.0 18 May 2018 none non-standard — Details →
8.2.1 17 May 2018 none non-standard — Details →
7.1.2 17 May 2018 none non-standard — Details →
7.0.3 17 May 2018 none non-standard — Details →
8.0.2 17 May 2018 none non-standard — Details →
9.2.0.M1 04 Mar 2018 none non-standard — Details →
9.1.0 31 Dec 2017 none non-standard — Details →
9.1.0.M2 11 Dec 2017 none non-standard — Details →
9.1.0.M1 06 Dec 2017 none non-standard — Details →
9.0.0 20 Sep 2017 none non-standard — Details →
9.0.0.M5 11 Sep 2017 none non-standard — Details →
9.0.0.M3 24 Aug 2017 none non-standard — Details →
9.0.0.M2 19 Aug 2017 none non-standard — Details →
9.0.0.M1 10 Aug 2017 none non-standard — Details →
8.2.0 22 Jun 2017 none non-standard — Details →
8.0.1 17 Mar 2017 none non-standard — Details →
7.1.1 17 Mar 2017 none non-standard — Details →
8.1.0 16 Mar 2017 none non-standard — Details →
8.1.0-RC 02 Mar 2017 none non-standard — Details →
8.0.0 08 Sep 2016 none non-standard — Details →
8.0.0-M1 06 Jul 2016 none non-standard — Details →
7.1.0 08 Apr 2016 none non-standard — Details →
7.0.2 23 Feb 2016 none non-standard — Details →
7.0.1 05 Feb 2016 none non-standard — Details →
7.0.0 24 Dec 2015 none non-standard — Details →

All 57 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.collections:eclipse-collections

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.collections:eclipse-collections

Is org.eclipse.collections:eclipse-collections safe to use?

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

Vulert scores org.eclipse.collections:eclipse-collections 76/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 org.eclipse.collections:eclipse-collections affected?

No. 13.0.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 org.eclipse.collections:eclipse-collections should I use?

13.0.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 org.eclipse.collections:eclipse-collections have?

0 vulnerabilities are recorded for org.eclipse.collections:eclipse-collections 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.collections:eclipse-collections vulnerabilities disclosed?

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

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