Vulnerability Database · Maven · Package report

org.sonarsource.scanner.api:sonar-scanner-api: vulnerability history, versions and safety

Q: How do I monitor org.sonarsource.scanner.api:sonar-scanner-api for upcoming vulnerabilities?

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

org.sonarsource.scanner.api:sonar-scanner-api 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 org.sonarsource.scanner.api:sonar-scanner-api vulnerabilities

Vulert verdict on org.sonarsource.scanner.api:sonar-scanner-api 2.16.3.1081 i

Updated on 23 Oct 2026

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

Package health score 61/100

Security Minor issues
Maintenance Slowing
Popularity Niche
Community Quiet

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

Current release 2.16.3.1081 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 18 packages i
Stars 118 i
OpenSSF scorecard 4/10 i
Last release 46 months ago i
Licence LGPL-3.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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for org.sonarsource.scanner.api:sonar-scanner-api, 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
2.16.3.1081	22 Dec 2022	none	LGPL-3.0	—	Details →
2.16.2.588	09 Nov 2021	none	LGPL-3.0	—	Details →
2.16.1.361	29 Apr 2021	none	LGPL-3.0	—	Details →
2.16.0.226	14 Jan 2021	none	LGPL-3.0	—	Details →
2.15.0.2182	17 Feb 2020	none	LGPL-3.0	—	Details →
2.14.0.2002	30 Sep 2019	none	LGPL-3.0	—	Details →
2.13.0.1871	04 Jul 2019	none	LGPL-3.0	—	Details →
2.12.0.1661	07 Jan 2019	none	LGPL-3.0	—	Details →
2.11.0.1537	21 Sep 2018	none	LGPL-3.0	—	Details →
2.10.0.1189	20 Nov 2017	none	LGPL-3.0	—	Details →
2.9.0.887	13 Mar 2017	none	LGPL-3.0	—	Details →
2.8	19 Sep 2016	none	LGPL-3.0	—	Details →
2.7	24 Aug 2016	none	LGPL-3.0	—	Details →
2.6	14 Apr 2016	none	LGPL-3.0	—	Details →

All 14 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 org.sonarsource.scanner.api:sonar-scanner-api

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.sonarsource.scanner.api:sonar-scanner-api

Is org.sonarsource.scanner.api:sonar-scanner-api safe to use?

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

Vulert scores org.sonarsource.scanner.api:sonar-scanner-api 61/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 org.sonarsource.scanner.api:sonar-scanner-api affected?

No. 2.16.3.1081, 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.sonarsource.scanner.api:sonar-scanner-api should I use?

2.16.3.1081 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.sonarsource.scanner.api:sonar-scanner-api have?

0 vulnerabilities are recorded for org.sonarsource.scanner.api:sonar-scanner-api 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.sonarsource.scanner.api:sonar-scanner-api vulnerabilities disclosed?

0 vulnerabilities were recorded for org.sonarsource.scanner.api:sonar-scanner-api 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.sonarsource.scanner.api:sonar-scanner-api 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.sonarsource.scanner.api:sonar-scanner-api for upcoming vulnerabilities?

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