Vulnerability Database · Maven · Package report

net.sf.jopt-simple:jopt-simple: vulnerability history, versions and safety

Q: How do I monitor net.sf.jopt-simple:jopt-simple for upcoming vulnerabilities?

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

net.sf.jopt-simple:jopt-simple is a package in the Maven ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the Maven ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all net.sf.jopt-simple:jopt-simple vulnerabilities

Vulert verdict on net.sf.jopt-simple:jopt-simple 6.0-alpha-3 i

Updated on 23 Oct 2026

Good news: 6.0-alpha-3, the version you would install today, has no known vulnerabilities.

Package health score 55/100

Security Minor issues
Maintenance Unmaintained
Popularity Niche
Community Quiet

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

Current release 6.0-alpha-3 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 42 packages i
Stars 366 i
OpenSSF scorecard 4/10 i
Last release 97 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for net.sf.jopt-simple:jopt-simple, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
6.0-alpha-3	11 Sep 2018	none	non-standard	—	Details →
6.0-alpha-2	23 Jul 2017	none	non-standard	—	Details →
5.0.4	13 Jul 2017	none	non-standard	—	Details →
6.0-alpha-1	06 Dec 2016	none	non-standard	—	Details →
5.0.3	25 Sep 2016	none	non-standard	—	Details →
5.0.2	08 Jun 2016	none	non-standard	—	Details →
5.0.1	07 Apr 2016	none	non-standard	—	Details →
5.0	11 Mar 2016	none	non-standard	—	Details →
5.0-beta-1	22 Jan 2016	none	non-standard	—	Details →
4.9	27 Jun 2015	none	non-standard	—	Details →
4.9-beta-1	04 Feb 2015	none	non-standard	—	Details →
4.8	29 Oct 2014	none	non-standard	—	Details →
4.8-beta-1	15 Oct 2014	none	non-standard	—	Details →
4.7	17 Aug 2014	none	non-standard	—	Details →
4.7-beta-1	31 Jul 2014	none	non-standard	—	Details →
4.6	06 Jan 2014	none	non-standard	—	Details →
4.5	01 Jun 2013	none	non-standard	—	Details →
4.4	08 Jan 2013	none	non-standard	—	Details →
4.4-beta-3	11 Dec 2012	none	non-standard	—	Details →
4.4-beta-2	20 Nov 2012	none	non-standard	—	Details →
4.4-beta-1	20 Nov 2012	none	non-standard	—	Details →
4.3	26 Nov 2011	none	non-standard	—	Details →
4.2	05 Nov 2011	none	non-standard	—	Details →
4.1	20 Oct 2011	none	non-standard	—	Details →
4.0	16 Oct 2011	none	non-standard	—	Details →
4.0-beta1	20 Aug 2011	none	non-standard	—	Details →
3.3	21 May 2011	none	non-standard	—	Details →
3.2	08 Dec 2009	none	non-standard	—	Details →
3.2-rc1	05 Oct 2009	none	non-standard	—	Details →
3.1	26 Apr 2009	none	non-standard	—	Details →
3.1-rc1	07 Apr 2009	none	non-standard	—	Details →
3.1-beta2	30 Mar 2009	none	non-standard	—	Details →
3.1-beta1	24 Mar 2009	none	non-standard	—	Details →
3.0.1	06 Mar 2009	none	non-standard	—	Details →
3.0	13 Jan 2009	none	non-standard	—	Details →
3.0-rc2	06 Jan 2009	none	non-standard	—	Details →
3.0-rc1	27 Dec 2008	none	non-standard	—	Details →
3.0-beta1	16 Dec 2008	none	non-standard	—	Details →
2.4.1	15 Jul 2008	none	non-standard	—	Details →
2.4	09 Jun 2008	none	non-standard	—	Details →
2.4-rc2	30 May 2008	none	non-standard	—	Details →
2.4-rc1	22 May 2008	none	non-standard	—	Details →
2.4-beta2	15 May 2008	none	non-standard	—	Details →
2.4-beta1	17 Apr 2008	none	non-standard	—	Details →
2.3.6	27 Mar 2008	none	non-standard	—	Details →

All 45 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for net.sf.jopt-simple:jopt-simple

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 net.sf.jopt-simple:jopt-simple

Is net.sf.jopt-simple:jopt-simple safe to use?

Vulert has no vulnerabilities on record for net.sf.jopt-simple:jopt-simple 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 net.sf.jopt-simple:jopt-simple's Vulert package health score?

Vulert scores net.sf.jopt-simple:jopt-simple 55/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 net.sf.jopt-simple:jopt-simple affected?

No. 6.0-alpha-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 net.sf.jopt-simple:jopt-simple should I use?

6.0-alpha-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 net.sf.jopt-simple:jopt-simple have?

0 vulnerabilities are recorded for net.sf.jopt-simple:jopt-simple 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 net.sf.jopt-simple:jopt-simple vulnerabilities disclosed?

0 vulnerabilities were recorded for net.sf.jopt-simple:jopt-simple 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 net.sf.jopt-simple:jopt-simple 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 net.sf.jopt-simple:jopt-simple for upcoming vulnerabilities?

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