> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-scan/language-identifier-settings.md).

# Language Identifier Settings

{% hint style="warning" %}

* This feature is available only in IZ Server versions later than 1.4.2.
  {% endhint %}

Language Identifier Settings allow you to control how the static code analysis engine determines the type of a project, such as Mule, API, Python, and others, based on its structure and contents.

These settings provide flexibility by ensuring more accurate classification and analysis. By customizing how projects are identified, teams can improve scan precision, apply the correct quality profiles, and ensure that language-specific rules and validations are consistently enforced across different types of codebases.

1. Navigate to **`Settings`** -> **`Global Settings`**.
2. Search for **`Language Identifier Settings`** and click on edit.
3. Settings can be configured / updated for each of the supported languages.

#### Detection Scripts <a href="#detection-scripts" id="detection-scripts"></a>

The setting holds one entry per language. The entry's key is the language id (for example **`mule`**, **`python`**, **`java`**, **`pyspark`**, **`cfn`**) and its value is a Groovy script that inspects the project folder and decides whether the project is that language and which files to scan. The same scripts are used by repository scans, IZ Eye, the IZ Scan CLI and the VS Code Extension.

A project is analysed by every language whose script matches it, so one repository can produce results for more than one language, for example Python and PySpark.

### See Also

* [Configure IZ Scan Plugin](/product-guides/integral-zone/iz-suite/iz-scan/anypoint-studio/configuration/iz-suite-configuration.md)
* [Source Code Analysis - On The Fly Results](/product-guides/integral-zone/iz-suite/iz-scan/anypoint-studio/source-code-analysis/anypoint-studio-analysis.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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-scan/language-identifier-settings.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.