EOL.Wiki EOL.Wiki
← ← Back to all products

SonarQube Community

Active
Tools & Monitoring Latest Version: 26.2.0.119303 Latest Release: Feb 4, 2026

SonarQube Community Edition is a free code quality and security analysis tool for continuous inspection.

Versions

7

Latest Version

26.2.0.119303

Active Support

1

EOL

6

Lifecycle Timeline

Today
26
26
25
25
24
24
10
10
9
9
8
8
7
7
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
26Jan 6, 2026-No26.2.0.119303No
Active
25Jan 7, 2025-Jan 6, 202625.12.0.117093No
EOL
24Dec 2, 2024-Jan 7, 202524.12.0.100206No
EOL
10Mar 30, 2023-Dec 2, 202410.7.0.96327No
EOL
9Jul 5, 2021-Jan 20, 20259.9.8.100196No
EOL
8Oct 15, 2019-Feb 7, 20238.9.10.61524No
EOL
7Feb 2, 2018-May 4, 20217.9.6No
EOL

Frequently Asked Questions

Which versions of SonarQube Community have reached end of life?
The following SonarQube Community versions have reached end of life and no longer receive security updates: 25, 24, 10, 9, 8, 7. It is recommended to upgrade to a supported version.
Is it safe to continue using SonarQube Community 25?
SonarQube Community 25 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of SonarQube Community?
The latest version of SonarQube Community is 26.2.0.119303, released in the 26 release cycle.
How many versions of SonarQube Community are currently supported?
SonarQube Community currently has 1 actively supported version(s): 26.
When does SonarQube Community 26 reach end of life?
SonarQube Community 26 does not have a specific end-of-life date announced yet.
What should I do when SonarQube Community reaches end of life?
When a SonarQube Community version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.