> 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/2025.1/user-guide/viewing-reports/regulatory-reports.md).

# Regulatory reports

In SonarQube Server 2025.1, regulatory reports provide important information about your project, such as quality gate status, ratings, and the distribution of issues for new and overall code.

Starting in [Enterprise Edition](https://www.sonarsource.com/plans-and-pricing/enterprise/), you can download a regulatory report for any permanent branch of a project. A permanent branch is one that has been set to **Keep when inactive,** see [Maintaining project branches](/sonarqube-server/2025.1/project-administration/maintaining-the-branches-of-your-project.md) for details.

The report is a zip file containing a snapshot of the selected branch. It is comprised of a selection of .txt, .csv, and .pdf files containing:

* An overview of the selected branch of the project.
* Configuration items relevant to the project’s quality (quality profile, quality gate, and analysis exclusions).
* Lists of findings for both new and overall code on the selected branch.\
  Only operational risks - reliability and security issues (bugs and vulnerabilities) and hotspots - are logged in the list of findings. Maintainability issues (code smells) are excluded from the list.

Depending on the configuration of your SonarQube Server instance, the regulatory report is generated with metrics either from [Standard Experience](/sonarqube-server/2025.1/instance-administration/analysis-functions/instance-mode/standard-experience.md) or [MQR mode](/sonarqube-server/2025.1/instance-administration/analysis-functions/instance-mode/mqr-mode.md). Some .csv files may contain metrics from both modes and they are marked accordingly.

To download the regulatory report of a project:

1. Retrieve your project. See [Retrieving projects](/sonarqube-server/2025.1/user-guide/viewing-projects/retrieving-projects.md) for more details.
2. In the top right corner of the project page, select **Project Information**.
3. In the **Regulatory Report** section, select the desired branch and click **Download**. The report will be dynamically generated and downloaded, which may take a few minutes depending on the project size.

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Security reports](/sonarqube-server/2025.1/user-guide/viewing-reports/security-reports.md)
* [PDF reports](/sonarqube-server/2025.1/user-guide/viewing-reports/pdf-reports.md)
* [Portfolios](/sonarqube-server/2025.1/user-guide/viewing-reports/portfolios.md)
* [Other issues](/sonarqube-server/2025.1/server-update-and-maintenance/troubleshooting/other-issues.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/2025.1/user-guide/viewing-reports/regulatory-reports.md?ask=<question>&goal=<user_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.