> 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/importing-external-issues/about-external-issues.md).

# About external issues

Issues generated by third-party analyzers can be imported into SonarQube Community Build.

Many languages have dedicated analyzers (also known as linters) that are commonly used to spot problems in code. SonarQube can integrate the results from many of these external analyzers. This lets you see this information alongside the other SonarQube metrics and allows the external results to be taken into account when calculating quality gate status.

If your analyzer doesn't integrate with SonarQube Community Build, you can import the external issues either in the generic SonarQube format or in the SARIF format.

## List of supported analyzers

The table below lists the third-party analyzers that integrate with SonarQube Community Build.

<table><thead><tr><th width="197">Language</th><th>External analyzers</th></tr></thead><tbody><tr><td>Cloudformation</td><td>AWS CloudFormation Linter</td></tr><tr><td>C#/VB.NET</td><td>Roslyn (inc. Roslyn analyzers provided by Microsoft)</td></tr><tr><td>CSS</td><td>StyleLint.io</td></tr><tr><td>Docker</td><td>Hadolint</td></tr><tr><td>Go</td><td>GoVet, GoLint, GoMetaLinter, golanci-lint, gosec</td></tr><tr><td>Java</td><td>SpotBugs, FindSecBugs, FindBugs, PMD, Checkstyle</td></tr><tr><td>JavaScript/TypeScript</td><td>ESLint</td></tr><tr><td>Kotlin</td><td>AndroidLint, Detekt, Ktlint</td></tr><tr><td>PHP</td><td>Psalm, PHPStan</td></tr><tr><td>Python</td><td>Pylint, Bandit, Flake8, Mypy, Ruff</td></tr><tr><td>Ruby</td><td>Rubocop</td></tr><tr><td>Scala</td><td>Scalastyle, Scapegoat</td></tr><tr><td>Terraform</td><td>TFLint</td></tr></tbody></table>

## Limitations

The external issues will be taken into account by SonarQube in the analysis report and users will be able to resolve an external issue the same way as an internal issue.

But external issues have an important limitation. The activation of the rules that raise these issues cannot be managed within SonarQube. External rules are not visible on the Rules page or reflected in any quality profile.

{% hint style="info" %}
Managing an external issue within SonarQube has no impact on its state in the external tool. For example, when you mark an issue as false positive in SonarQube, it is not reflected in the external tool.
{% endhint %}

## Related pages

[External analyzer reports](/sonarqube-community-build/analyzing-source-code/importing-external-issues/external-analyzer-reports.md)\
[Generic issue import format](/sonarqube-community-build/analyzing-source-code/importing-external-issues/generic-issue-import-format.md)\
[SARIF reports](/sonarqube-community-build/analyzing-source-code/importing-external-issues/importing-issues-from-sarif-reports.md)\
[Integration with external analyzers at instance level](/sonarqube-community-build/instance-administration/analysis-functions/integration-with-external-analyzers.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/importing-external-issues/about-external-issues.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.