> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/checks/component/comp_0004.md).

# Non platform supported components

<table><thead><tr><th width="138">Check ID</th><th>COMP_0004</th></tr></thead><tbody><tr><td>Category</td><td>Maintainability</td></tr><tr><td>Summary</td><td>The Mendix Marketplace contains a library of components that can be added to your Mendix app. Some of these components are supported by Mendix ('platform supported'), others are supported by independent software vendors (ISVs), and others are community supported. Care should be used when using non-platform supported components as bugs or security vulnerabilities with these components can be difficult to resolve.</td></tr><tr><td>Options</td><td>The maximum number of non-platform supported components an app may have.</td></tr><tr><td>Pass</td><td>The number of non-platform supported components in use by your app is less than the number configured in this check.</td></tr><tr><td>Fail</td><td>The number of non-platform supported components in use by your app is more than the number configured in this check.</td></tr></tbody></table>


---

# 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.bluestorm.io/checks/component/comp_0004.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.
