PAGES
← all tools
◆ SAST / SCA / Code Security

SonarQube

changelog-20261003-9e5fd489 commercial

Sonarqube is a enforce consistent quality gates across every pull request and pipeline, from IDE to CI/CD, with automated code review for bugs and security issues.

Summary

SonarQube is a commercial code review and code verification platform that detects quality and security issues before deployment. It is run as a service and targets application developers. Its documentation positions it alongside code-scanning tools. SonarQube was first launched in 2008, and seven releases have been tracked in our records.

Sonarqube is a enforce consistent quality gates across every pull request and pipeline, from IDE to CI/CD, with automated code review for bugs and security issues.

How SonarQube helps

Which vulnerabilities and quality issues are already sitting in my codebase before I ship it?

scans the source against its rule set for the language in use and lists bugs, vulnerabilities, and maintainability issues by file, so they surface before deployment rather than after

Which of the flagged issues in my main branch are actually worth fixing first?

an agent works through the existing backlog of issues on the branch and proposes fix suggestions ranked for review, instead of leaving every issue at equal priority

Are there broken access control or business logic flaws hiding in my application that pattern rules would miss?

a dedicated security agent explores the codebase for issues like missing authorization checks, privilege escalation, session fixation, and skipped workflow steps, then confirms each candidate against the running code before reporting it

Is a newly flagged security issue real or a false alarm before I spend time on it?

each candidate finding is checked for exploitability by a separate validation pass before it is ever surfaced as an issue, which is what keeps reported precision in the 80-90% range

Can my build scripts and pipeline definitions be scanned the same way as my application code?

applies dedicated rule sets to Groovy, PowerShell, Gosu, DataWeave and R sources, covering things like hardcoded credentials, injection risks, and unsafe command execution alongside the usual bug and maintainability checks

Will scanning slow down as my repository grows past a few million lines?

runs an incremental multi-phase pipeline that re-analyzes only what changed, cutting re-scan time on large repositories by roughly half compared to a full rescan

all 20 features, with the evidence for each →

Languages

Not documented

Features

20 capabilities across 2 capability groups

Built from SonarQube's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • SonarQube covers 2 of the 8 vulnerability assessment methods capabilities we track.

What SonarQube offers you

  • Self-hosted deployment3
  • Agent-based deployment2
  • Python scripting support2
  • CI/CD pipeline integration1
  • Command-line interface1
  • JavaScript scripting support1
  • Kubernetes-native deployment1
  • MCP server1
  • Scripting language support1
Static application security testing 6 features Vulnerability assessment methods since 2026
Hunter Agent shipped An on-demand background agent that uses your own Anthropic key to trace data and identity flows across a full codebase, detecting broken access control, IDOR, privilege escalation, session fixation, and authentication flaws that pattern-based scanners miss, and surfaces confirmed findings directly into the SonarQube issue list. 6 releases · 2 other sources · first seen Sep 2026

Shared capability: Static application security testing

Also counts toward: Agent-based deployment, Self-hosted deployment

release

  • Adds support for the hunter-agent tag and category tags such as hunter-broken-access-control to filter Hunter Agent findings on the Issues page alongside the Fixable by Agent filter.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Oct 2026 · source · release history
  • Adds OpenAI GPT Cyber Models to SonarQube Hunter Agent via the OpenAI Daybreak Defense Network, enabling deeper agentic security reasoning across codebases.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Oct 2026 · source · release history
  • Makes GPT-6.1 Sol available inside Hunter Agent, delivering 67% complete-finding coverage and up to 43% faster scans on large codebases. announced · Oct 2026 · source · release history
  • Adds SonarQube Hunter Agent, an on-demand background agent that uses your own Anthropic key to uncover broken access control, business logic, and authentication flaws that pattern-based scanners miss, surfacing confirmed findings directly as SonarQube issues. changelog · Oct 2026 · source · release history
  • Adds SonarQube Hunter Agent, an on-demand background agent that uncovers broken access control, business logic, and authentication flaws using your own Anthropic key, surfacing confirmed findings directly as SonarQube issues rather than in a separate tool or portal. SonarQube Server 2026.5 LTA: Ship AI code inside your perimeter with confidence · seen Sep 2026 · source · release history
  • Adds SonarQube Hunter Agent self-hosted deployment, using your own Anthropic key to trace data and identity flows across a full codebase and detect IDOR, privilege escalation, and session fixation, delivering confirmed findings with severity into the existing SonarQube issue list. announced · Sep 2026 · source · release history

docs

  • Sonar Vortex documentation sonar-vortex_light_16x9.svg sonar-vortex_dark_16x9.svg Hunter Agent documentation sonarqube-hunter-agent_light_16x9.svg sonarqube-hunter-agent_dark_16x9.svg Agent Centric Development Cycle (AC/DC) documentation SonarQube MCP Server documentation If you need additional information that is not… seen Oct 2026 · source

example

  • Filter the Issues page to only Hunter Agent authorization findings ready for automated remediation, then dispatch them for fixing. In SonarQube Cloud, open your project Issues page, select the main branch, enable the 'Fixable by Agent' filter, then add the tag `hunter-broken-access-control` (or `hunter-agent` for all Hunter… announced · Oct 2026 · source
Language coverage expansion shipped Extends analysis to Java 25, Python web frameworks (FastAPI, Flask, Django), Jenkins Groovy, PowerShell, Gosu, Ruby, Apex, MuleSoft DataWeave, and R. 2 releases · first seen Sep 2026

Shared capability: Static application security testing

Also counts toward: Python scripting support, Scripting language support

release

  • Expands language coverage to include Java 25, Python web frameworks (FastAPI, Flask, Django), Jenkins Groovy, PowerShell, Gosu, Ruby, and Apex. announced · Sep 2026 · source · release history
  • Adds native support for MuleSoft DataWeave and R as new analysis languages. announced · Sep 2026 · source · release history
Quality gate for agent-generated code shipped A purpose-built quality gate that enforces stricter security, reliability, and supply-chain standards on AI-generated code while remaining permissive on coding style. 1 release · 1 other source · first seen Sep 2026

Shared capability: Static application security testing

release

  • Adds a new quality gate purpose-built for agent-generated code that enforces stricter security, reliability, and supply-chain standards while staying permissive on coding style. announced · Sep 2026 · source · release history

docs

  • - [Built-in quality profiles](https://docs.sonarsource.com/sonarqube-cloud/standards/managing-quality-profiles/built-in-quality-profiles.md): SonarQube Cloud ships three built-in quality profiles per language (Sonar way core, extended, and comprehensive), each with a different level of strictness. seen Sep 2026 · source
C/C++ cross-translation-unit symbolic execution shipped Extends C/C++ symbolic execution across file boundaries so analysis results are consistent when logic is spread across multiple translation units. 1 release · first seen Sep 2026

Shared capability: Static application security testing

release

  • Adds cross-translation-unit awareness to C/C++ symbolic execution, making analysis consistent across file boundaries. announced · Sep 2026 · source · release history
C/C++ taint analysis shipped Detects command-injection and path-traversal vulnerabilities in C and C++ code through taint analysis. 1 release · first seen Sep 2026

Shared capability: Static application security testing

release

  • Adds new taint analysis for C and C++ covering command-injection and path-traversal detection. announced · Sep 2026 · source · release history
Incremental taint analysis shipped Cuts pull-request scan times on large Java and C# projects by up to 90% by running taint analysis only on changed code paths. 1 release · first seen Sep 2026

Shared capability: Static application security testing

release

  • Adds incremental taint analysis cutting pull request scan times on large Java and C# projects by up to 90%. announced · Sep 2026 · source · release history
Container image vulnerability scanning 1 feature Vulnerability assessment methods since 2026
Container image scanning shipped A CLI scanner that analyzes container images for known OS-layer vulnerabilities and malicious packages, generates an SBOM sent to SonarQube Cloud for analysis, supports vendor-advisory-backed vulnerability tracking across major Linux distributions, enables CI pipeline gating on image risk severity, surfaces results in a dedicated organization sidebar, and re-checks previously analyzed images against newly published vulnerabilities without requiring a re-scan. 6 releases · 1 other source · first seen Oct 2026

Shared capability: Container image vulnerability scanning

Also counts toward: CI/CD pipeline integration, Command-line interface

release

  • Adds a Container images section in the SonarQube Cloud organization sidebar, listing every analyzed image with its tag, risk count, most severe risk, and last-analyzed timestamp alongside code and dependency risks. announced · Oct 2026 · source · release history
  • Supports vulnerability tracking backed by vendor security advisories for images based on Red Hat Enterprise Linux, Debian 11+, Rocky Linux, AlmaLinux, Ubuntu, and Alpine. announced · Oct 2026 · source · release history
  • Available at no additional cost for SonarQube Cloud organizations on Team and Enterprise plans with SonarQube Advanced Security. announced · Oct 2026 · source · release history
  • Introduces sonar-container-scanner <IMAGE> --organization <ORGANIZATION_KEY> --token <TOKEN> CLI to scan container images for known OS-layer vulnerabilities and malicious packages, generating an SBOM sent to SonarQube Cloud for analysis.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Oct 2026 · source · release history
  • Supports automatic re-checking of previously analyzed images against newly published vulnerabilities without requiring a re-scan, based on organization re-analysis settings. announced · Oct 2026 · source · release history
  • Adds --fail-on flag to sonar-container-scanner to set a minimum severity threshold (default: high) at which the scanner exits with a failing code, enabling CI pipeline gates on container image risk. announced · Oct 2026 · source · release history

example

  • Gate a CI build on container image risk — build the image and fail the pipeline if any high-severity or above vulnerabilities are found in OS-layer packages. docker build -t my-app:${BUILD_TAG} . sonar-container-scanner my-app:${BUILD_TAG} --organization <ORGANIZATION_KEY> --token <TOKEN> --fail-on high announced · Oct 2026 · source
Other / not yet classified 13 features Features we have not matched to a capability yet. A suggested match is marked.
Remediation Agent shipped suggested A self-hosted, containerized agent that automatically generates verified code fixes for SonarQube issues, submits pull requests via GitHub, GitLab, or Azure DevOps, and supports bring-your-own-LLM endpoints including AWS Bedrock, Azure AI Foundry, Anthropic, OpenAI, and custom gateways — all without code leaving operator-controlled infrastructure. 14 releases · 3 other sources · first seen Sep 2026

Suggested capability: Static application security testing. This is our guess, not confirmed.

Also counts toward: Agent-based deployment, JavaScript scripting support, Kubernetes-native deployment, Python scripting support, Self-hosted deployment

release 14 total

  • Each Hunter Agent finding sent to the Remediation Agent generates its own individual pull request (or merge request on GitHub), separate from the grouped-by-rule-key behavior used for rule-based issues. announced · Oct 2026 · source · release history
  • Enables CI follow-up for Hunter Agent fix pull requests via GitHub Actions: when CI fails, the agent reads build logs, pushes a corrective commit, and retries up to three times before leaving the PR open. announced · Oct 2026 · source · release history
  • Brings Remediation Agent support for Hunter Agent findings to SonarQube Server 2026.5, with both agents running on self-deployed infrastructure. announced · Oct 2026 · source · release history
  • Adds SonarQube Remediation Agent, a containerized engine deployable inside Kubernetes or Docker that connects to a cloud LLM endpoint using your own key, integrates with GitHub, GitLab, or Azure DevOps, and delivers SonarQube-verified automated code fixes without requiring public internet exposure. changelog · Oct 2026 · source · release history
  • Adds the Remediation Agent to SonarQube Server Enterprise and Data Center editions, enabling automated fix generation, sandbox verification, and pull request submission without code leaving self-hosted infrastructure.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Oct 2026 · source · release history
  • Adds an Agent activity page showing every remediation job (running and finished) with status, duration, source, and the pull requests opened. announced · Oct 2026 · source · release history

example

  • Schedule weekly automated remediation at the project level to keep technical debt low without manual triage, capping PR volume to avoid overwhelming reviewers. In the SonarQube Server project settings under the Remediation Agent section, set the schedule to weekly and configure the maximum number of pull requests per run, then save. announced · Oct 2026 · source
  • Enable the Remediation Agent on a self-hosted SonarQube Server instance connected to Azure AI Foundry for regulated environments that cannot use external AI endpoints. In the SonarQube Server administration UI, go to AI Capabilities, connect your DevOps platform (GitHub, GitLab, or Azure DevOps) with the required permissions, select Azure AI Foundry as your model… announced · Oct 2026 · source
  • Trigger on-demand remediation before an audit by filtering the Issues page to agent-fixable items in a single project and assigning them to the agent for immediate PR generation. On the SonarQube Server Issues page, filter by issues the Remediation Agent can fix, select the target issues, and assign them to the agent to generate and submit pull requests grouped by rule and… announced · Oct 2026 · source
Sonar Vortex shipped A semantic code-navigation engine deployable inside your own infrastructure that injects project context, coding guidelines, architecture awareness, and dependency health into AI coding agents before and during code generation, verifying changes inside the agent loop to prevent new issues and reduce token consumption. 3 releases · 7 other sources · first seen Sep 2026

Also counts toward: Self-hosted deployment

release

  • Adds Sonar Vortex, a semantic Code Navigation engine that guides AI agents to write code aligned with project standards and prevents new issues from being introduced, reducing token consumption.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ changelog · Oct 2026 · source · release history
  • Adds Sonar Vortex, a semantic Code Navigation engine that guides AI coding agents to write code aligned with project standards and prevents introduction of new issues, reducing token consumption during code generation.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ SonarQube Server 2026.5 LTA: Ship AI code inside your perimeter with confidence · seen Sep 2026 · source · release history
  • Adds Sonar Vortex self-hosted deployment for SonarQube Server Enterprise and Data Center editions, injecting project context and constraints into coding agents and verifying changes inside the agent loop before commit. announced · Sep 2026 · source · release history

docs 7 total

  • Sonar Vortex documentation sonar-vortex_light_16x9.svg sonar-vortex_dark_16x9.svg Hunter Agent documentation sonarqube-hunter-agent_light_16x9.svg sonarqube-hunter-agent_dark_16x9.svg Agent Centric Development Cycle (AC/DC) documentation SonarQube MCP Server documentation If you need additional information that is not… seen Oct 2026 · source
  • Sonar's Agent Centric Development Cycle helps you ensure code generated by agents is verified in SonarQube Cloud and SonarQube Server and fixed before it reaches your repository. * On SonarQube Server, Sonar Vortex, the Remediation Agent, and Hunter Agent require activation through the Sonar License user portal. seen Oct 2026 · source
  • Sonar Vortex documentation sonar-vortex_light_16x9.svg sonar-vortex_dark_16x9.svg Hunter Agent documentation sonarqube-hunter-agent_light_16x9.svg sonarqube-hunter-agent_dark_16x9.svg Agent Centric Development Cycle (AC/DC) documentation SonarQube MCP Server documentation Perform an HTTP GET request on the following… seen Oct 2026 · source
  • - [About the Agent Centric Development Cycle](https://docs.sonarsource.com/agent-centric-development-cycle/readme.md): Sonar's Agent Centric Development Cycle helps you ensure code generated by agents is verified in SonarQube Cloud and SonarQube Server and fixed before it reaches your repository. docs update · Oct 2026 · source
  • Sonar Vortex documentation sonar-vortex_light_16x9.svg sonar-vortex_dark_16x9.svg Hunter Agent documentation sonarqube-hunter-agent_light_16x9.svg sonarqube-hunter-agent_dark_16x9.svg Agent Centric Development Cycle (AC/DC) documentation SonarQube MCP Server documentation seen Oct 2026 · source
  • September 29, 2026 SonarQube Server 2026.5 LTA: Ship AI code inside your perimeter with confidence Sonar Vortex makes your agent produce better code, faster, for fewer tokens. Vortex guides your agent to write code aligned with your standards, and prevents it from introducing new issues. changelog · Oct 2026 · source
Dependency reachability analysis shipped suggested Identifies which known-vulnerable dependency code paths are actually called by application code in Java and C#, distinguishing reachable vulnerabilities from unreachable ones. 5 releases · 2 other sources · first seen Sep 2026

Suggested capability: Vulnerability prioritization. This is our guess, not confirmed.

release

  • Surfaces reachability status in the Dependency Risks tab with a Reachability filter and a Reachable badge on individual risk cards.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Oct 2026 · source · release history
  • Reachability analysis is calculated during full analysis runs (CI or automatic analysis) for Java, C#, and Python; no extra configuration is required. announced · Oct 2026 · source · release history
  • Adds reachability status to the Detailed Risk view alongside CVSS, EPSS, and KEV data under the What's the Risk? tab. announced · Oct 2026 · source · release history
  • Includes reachability status in downloadable dependency risk reports in JSON and CSV formats (Enterprise plan only). announced · Oct 2026 · source · release history
  • Adds direct reachability analysis for Java and C# identifying which dependency vulnerabilities the application code actually calls. announced · Sep 2026 · source · release history

example

  • After your next CI full analysis, filter your dependency backlog to only confirmed-reachable vulnerabilities so your team works the highest-priority items first. In SonarQube, go to your project > Dependency Risks tab, then click the Reachability filter and select 'Reachable' to see only vulnerabilities your code actively calls. announced · Oct 2026 · source
  • Download a dependency risk report scoped to reachable vulnerabilities for compliance attestation or offline triage (Enterprise plan). In SonarQube, go to your project > Dependency Risks tab, filter by Reachability = 'Reachable', then download the report in JSON or CSV format. announced · Oct 2026 · source
Portfolio and project dashboards shipped Provides customizable portfolio and project dashboards with a new overview landing page for organization-wide reporting, including a coverage dashboard showing connected DevOps platforms, imported repositories, and unanalyzed projects. 5 releases · 1 other source · first seen Sep 2026

release

  • Adds an Import all repositories button on the Analyze projects page for SonarQube Cloud organizations bound to Azure DevOps or Bitbucket, enabling a single-action bulk import of every repository in the organization.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Oct 2026 · source · release history
  • Provides a real-time progress indicator on the Analyze projects page while a bulk import is running, replacing the previous opaque all-or-nothing wait. announced · Oct 2026 · source · release history
  • Generates a downloadable summary report after bulk import completes, listing which repositories were imported, skipped, or failed for an auditable record. announced · Oct 2026 · source · release history
  • Adds customizable portfolio and project dashboards with a new overview landing page for organization-wide reporting. announced · Sep 2026 · source · release history
  • Adds a project coverage dashboard showing which DevOps platforms are connected, which repositories are imported, and which projects have not yet been analyzed. announced · Sep 2026 · source · release history

example

  • Onboard every repository in an Azure DevOps or Bitbucket organization into SonarQube Cloud at once, instead of importing in batches of up to 25. In SonarQube Cloud, go to Analyze projects, then click 'Import all repositories' for your Azure DevOps or Bitbucket organization. announced · Oct 2026 · source
MISRA C/C++ compliance reporting shipped suggested Generates audit-ready, tamper-evident MISRA C/C++ attestation artifacts automatically, with automated MISRA C:2012 coverage reaching 38.4%. 2 releases · first seen Sep 2026

Suggested capability: Static application security testing. This is our guess, not confirmed.

release

  • Adds a new MISRA C/C++ Compliance Report generating audit-ready, tamper-evident attestation artifacts automatically. announced · Sep 2026 · source · release history
  • Raises MISRA C automated coverage to 38.4% for MISRA C:2012. announced · Sep 2026 · source · release history
Architecture drift detection shipped Automatically detects architectural drift and surfaces violations directly in the developer issue list. 1 release · first seen Sep 2026

release

  • Adds architecture management that automatically catches architectural drift and surfaces it in the existing developer issue list. announced · Sep 2026 · source · release history
LLM governance via Azure API Management shipped Integrates Azure API Management as a gateway for LLM calls so Azure OpenAI customers can authenticate without static API keys. 1 release · first seen Sep 2026

release

  • Adds Azure API Management support for LLM governance so Azure OpenAI customers authenticate without static API keys.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Sep 2026 · source · release history
Quality gate adherence dashboard shipped Provides a dashboard that flags releases that shipped to production despite a failing quality gate, making bypass events visible. 1 release · first seen Sep 2026

release

  • Adds a quality gate adherence dashboard flagging risky releases that shipped despite a failing gate. announced · Sep 2026 · source · release history
Rust analysis shipped Adds first-class Rust analysis beyond Clippy, including centralized quality profiles, quality-gate enforcement, Cognitive Complexity and Cyclomatic Complexity metrics, code-coverage correlation from LCOV or Cobertura, duplication detection, and coverage of popular Rust crates. 1 release · first seen Sep 2026

release

  • Adds Rust analysis beyond Clippy, layering centralized quality profiles, quality-gate enforcement, Cognitive Complexity and Cyclomatic Complexity metrics, code-coverage correlation from LCOV or Cobertura, duplication detection, and coverage of popular Rust crates. announced · Sep 2026 · source · release history
Secret masking and redaction shipped Automatically masks and redacts detected secrets in scan results by default to reduce accidental exposure. 1 release · first seen Sep 2026

release

  • Detected secrets are now masked and redacted by default to reduce potential exposure. announced · Sep 2026 · source · release history
SonarQube MCP Server endpoint shipped Exposes an embedded MCP Server endpoint so agentic tools such as Cursor, Claude Code, and GitHub Copilot can read project issues and quality-gate status, governed by a token-based kill-switch. 1 release · first seen Sep 2026

Also counts toward: MCP server

release

  • Adds an embedded SonarQube MCP Server endpoint letting Cursor, Claude Code, GitHub Copilot and other agentic tools reach project issues and quality gates, governed by a token-based kill-switch. announced · Sep 2026 · source · release history
Unified vulnerability model shipped Migrates security hotspots into a single vulnerability model that preserves the full history of previously tracked hotspot issues. 1 release · first seen Sep 2026

release

  • Migrates security hotspots into a unified vulnerability model preserving full history. announced · Sep 2026 · source · release history
WCAG Accessibility and CRA compliance reporting shipped Generates reports proving WCAG accessibility and Cyber Resilience Act conformance at the project, application, and portfolio level. 1 release · first seen Sep 2026

release

  • Adds new WCAG Accessibility and CRA Compliance Reports proving conformance at the project, application, and portfolio level. announced · Sep 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Command line

3 commands for SonarQube, each with where it came from. This tool has no source analysis yet, so there is no option reference and no captured run beside them.

Source

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface

Five scores for SonarQube, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail SonarQube puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Website history

sonarsource.com, every change

SonarSource's home page and 31 more pages as they looked each month from September 2021 to October 2026: 41 renders, 6 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Coverage

Missing something? Tell us

What SonarQube connects to, runs on and detects, read from its release notes and docs. So far: 1 new vulnerability check, 1 new supported platform.

Show

2 changes, tracked since Oct 22, 2026.

  • Oct 222026

    new Container image OS-layer vulnerability scanning for PHP2Shell

    With CVE-2026-109618, CVE-2026-109619

    Check your container images for known vulnerabilities and malicious packages. This includes PHP2Shell (CVE-2026-109618 and CVE-2026-109619) in images that install PHP from a Linux distribution package.

    Source ↗

  • Oct 222026

    new Container image scanning support for Red Hat Enterprise Linux, Debian 11+, Rocky Linux, AlmaLinux, Ubuntu, Alpine

    Vulnerability tracking for images based on Red Hat Enterprise Linux, Debian 11 and higher, Rocky Linux, AlmaLinux, Ubuntu and Alpine.

    Source ↗

How we count

Read from 2 of 30 release notes and docs updates we hold for SonarQube. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through SonarQube's life, so an old integration can show a recent first-seen date.

Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.

Releases

Show
Coverage in all entries

30 entries

  1. October 20268
  2. September 202618
  3. August 20264
    Show
    Coverage in all entries

    30 entries

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →