> 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-server/quality-standards-administration/managing-quality-profiles/built-in-quality-profiles.md).
# Built-in quality profiles
SonarQube Server 2026.5 ships three built-in quality profiles per language (Sonar way core, extended, and comprehensive), each with a different level of strictness.
SonarQube Server provides three built-in quality profiles for each supported language: **Sonar way core**, **Sonar way extended**, and **Sonar way comprehensive**. Each profile applies a different level of strictness. Pick the one that matches your team’s experience with SonarQube and how much friction you want in your workflow.
**Sonar way core** is the default quality profile for every language. See [Changing default quality profile](/sonarqube-server/quality-standards-administration/managing-quality-profiles/changing-default-quality-profile.md) to change it.
## Sonar way core
Sonar way core activates:
* All security rules (vulnerabilities in Standard Experience).
* Medium and higher severity recommended reliability rules (Major and higher severity bugs in Standard Experience).
* Blocker severity recommended maintainability rules (Blocker severity code smells in Standard Experience).
This profile covers the most impactful rules recommended by Sonar. It helps your team focus on the issues that matter most, and it’s a good baseline for most projects.
Sonar way core also aligns with the following standards: OWASP Top 10, OWASP Mobile Top 10, CWE Top 25, OWASP ASVS, NIST SSDF, PCI DSS, DISA STIG, CASA, the EU Cyber Resilience Act (CRA), the Digital Operational Resilience Act (DORA), GDPR, and SOC 2.
## Sonar way extended
Sonar way extended activates:
* All security rules (vulnerabilities in Standard Experience).
* Low and higher severity recommended reliability rules (Minor and higher severity bugs in Standard Experience).
* High and higher severity recommended maintainability rules (Critical and higher severity code smells in Standard Experience).
This profile builds on Sonar way core, adding more strictness in reliability and maintainability. The rule count still stays balanced, so your team keeps a good development experience. It aligns with the same standards as Sonar way core.
## Sonar way comprehensive
Sonar way comprehensive activates:
* All security rules (vulnerabilities in Standard Experience).
* All recommended reliability rules (bugs in Standard Experience).
* All recommended maintainability rules (code smells in Standard Experience).
This is Sonar’s comprehensive ruleset. It’s recommended for teams already experienced with SonarQube, or if you’re evaluating SonarQube and want to experience its complete value. It aligns with the same standards as Sonar way core.
{% hint style="info" %}
Sonar way comprehensive replaces the quality profile formerly named **Sonar way**.
When you update to SonarQube Server 2026.5 from an earlier version, your projects keep the quality profiles they used in the previous version. The default profile of each language also stays the same.
{% endhint %}
## Other built-in profiles
Sonar way core, extended, and comprehensive aren’t the only built-in profiles. SonarQube also provides the *Sonar agentic AI* quality profile for agent centric development, and the **Sonar MISRA compliance** quality profiles for C and C++ safety-critical code. See [Quality profiles for agentic AI](/sonarqube-server/quality-standards-administration/ai-code-assurance/quality-profiles-for-agentic-ai.md) and [Understanding quality profiles](/sonarqube-server/quality-standards-administration/managing-quality-profiles/understanding-quality-profiles.md) for more information.
## Related pages
* [Understanding quality profiles](/sonarqube-server/quality-standards-administration/managing-quality-profiles/understanding-quality-profiles.md)
* [Changing default quality profile](/sonarqube-server/quality-standards-administration/managing-quality-profiles/changing-default-quality-profile.md)
* [Creating a quality profile](/sonarqube-server/quality-standards-administration/managing-quality-profiles/creating-a-quality-profile.md)
* [Quality profiles for agentic AI](/sonarqube-server/quality-standards-administration/ai-code-assurance/quality-profiles-for-agentic-ai.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-server/quality-standards-administration/managing-quality-profiles/built-in-quality-profiles.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.