> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-community-build/analyzing-source-code/languages/overview.md).
# Supported languages
SonarQube Community Build provides analysis of different languages depending on the edition you’re running.
SonarQube Community Build is an automated code review and static code analysis solution for several languages to satisfy your unique needs.
{% hint style="info" %}
To get started quickly, you can follow the in-product tutorial. When you create a project in SonarQube Community Build, it walks you through analyzing your project's main language and running your first analysis.
{% endhint %}
The table below lists the supported languages. For the supported versions and language-specific properties, refer to each language page directly. See *Related pages* below.
Infrastructure as Code (IaC) analysis is supported for the following languages listed in the table below: Ansible, Azure Resource Manager, CloudFormation, Docker, Kubernetes, Terraform.
| Language | SonarQube Community Build | SonarQube Cloud | SonarQube Server 2026.5 |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ABAP | | 
Enterprise Plan
|  |
| Ansible | |  |  |
| Apex | |
Enterprise Plan
|
From Enterprise
|
| Azure Pipelines | |  |  |
| Azure Resource Manager |  |  |  |
| C | |  |  |
| C++ | |  |  |
| CloudFormation |  |  |  |
| COBOL | |
Enterprise Plan
|
From Enterprise
|
| C# |  |  |  |
| CSS |  |  |  |
| Dart | |  |  |
| Docker |  |  |  |
| Flex |  |  |  |
| GitHub Actions | |  |  |
| Go |  |  |  |
| Gosu | |
Enterprise Plan
|
From Enterprise
|
| Groovy | |  |  |
| HTML |  |  |  |
| Java |  |  |  |
| JavaScript |  |  |  |
| JCL | |
Enterprise Plan
|
From Enterprise
|
| JSON | |  |  |
| Kotlin |  |  |  |
| Kubernetes/Helm |  |  |  |
| Mulesoft Dataweave | |
Enterprise Plan
|
From Enterprise
|
| Objective-C | |  |  |
| PHP |  |  |  |
| PL/I | |
Enterprise Plan
|
From Enterprise
|
| PL/SQL | |  |  |
| Powershell | |  |  |
| Python |  |  |  |
| R | |  |  |
| RPG | |
Enterprise Plan
|
From Enterprise
|
| Ruby |  |  |  |
| Rust |  |  |  |
| Scala |  |  |  |
| Secrets |  |  |  |
| Shell | |  |  |
| Swift | |  |  |
| Terraform |  |  |  |
| TypeScript |  |  |  |
| TSQL | |  |  |
| VB.NET |  |  |  |
| VB6 | |  |
From Enterprise
|
| XML |  |  |  |
| YAML | |  |  |
## Related pages
* [Azure Resource Manager](/sonarqube-community-build/analyzing-source-code/languages/azure-resource-manager.md)
* [CloudFormation](/sonarqube-community-build/analyzing-source-code/languages/cloudformation.md)
* [C#](/sonarqube-community-build/analyzing-source-code/languages/csharp.md)
* [Docker](/sonarqube-community-build/analyzing-source-code/languages/docker.md)
* [Flex](/sonarqube-community-build/analyzing-source-code/languages/flex.md)
* [Go](/sonarqube-community-build/analyzing-source-code/languages/go.md)
* [HTML](/sonarqube-community-build/analyzing-source-code/languages/html.md)
* [Java](/sonarqube-community-build/analyzing-source-code/languages/java.md)
* [JavaScript/TypeScript/CSS](/sonarqube-community-build/analyzing-source-code/languages/javascript-typescript-css.md)
* [Kotlin](/sonarqube-community-build/analyzing-source-code/languages/kotlin.md)
* [Kubernetes/Helm](/sonarqube-community-build/analyzing-source-code/languages/kubernetes.md)
* [PHP](/sonarqube-community-build/analyzing-source-code/languages/php-analysis.md)
* [Python](/sonarqube-community-build/analyzing-source-code/languages/python.md)
* [Ruby](/sonarqube-community-build/analyzing-source-code/languages/ruby.md)
* [Rust](/sonarqube-community-build/analyzing-source-code/languages/rust.md)
* [Scala](/sonarqube-community-build/analyzing-source-code/languages/scala.md)
* [Secrets](/sonarqube-community-build/analyzing-source-code/languages/secrets.md)
* [Terraform](/sonarqube-community-build/analyzing-source-code/languages/terraform.md)
* [VB.NET](/sonarqube-community-build/analyzing-source-code/languages/vb-dotnet.md)
* [XML](/sonarqube-community-build/analyzing-source-code/languages/xml.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sonarsource.com/sonarqube-community-build/analyzing-source-code/languages/overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.