> 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/applications/projects.md).

# Projects

{% hint style="warning" %}

* To scan the applications, either of the following options can be used -
  * [Using Maven](/product-guides/integral-zone/iz-suite/iz-scan/ci-cd-integration/using-maven.md)
  * [Using IZ Scan CLI](/product-guides/integral-zone/iz-suite/iz-scan/ci-cd-integration/using-iz-scan-cli.md)
    {% endhint %}

To view all the Applications -

1. Navigate to **`IZ Scan`** and choose an application type from its platform submenu, for example **`Anypoint Platform`** -> **`Mule Projects`** or **`APIs`**, or **`Others`** -> **`Java Apps`**. See [Languages](/product-guides/integral-zone/iz-suite/iz-scan/languages.md) for every application type. The main row includes -
   1. **`Application Name`** - Name of the application
   2. **`Updated`** - The last date and time the application was scanned\
       

      <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fludid3XlkO5Lnl1dlHCZ%2Fimage.png?alt=media&amp;token=53791970-70db-44c3-beba-7dbd16604b9a" alt=""><figcaption></figcaption></figure>
2. Click on the **`Plus`** icon to view all the branches or pull requests associated with the application.
3. Summary details include -
   1. **`Type`** - Branch or Pull Request
   2. **`Name`** - name of the Branch or Pull Request
   3. **`Total Issues`** - Indicates the total number of issues identified when the application was scanned
   4. **`Quality Gate`** - Status of the Quality Gate
   5. **`Last Scan`** - Time since the last scan was performed
4. Actions include -
   1. **`View Dashboard`** - Summary report of all the issues. [View Dashboard](/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/application-dashboard.md)
   2. **`View Issues`** - Detailed report of the issues with file names and line numbers. [View Issues](/product-guides/integral-zone/iz-suite/iz-eye/application-issues.md)

### See Also

* [Mule Projects](/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/applications/mule-applications.md)
* [Application Issues](/product-guides/integral-zone/iz-suite/iz-eye/application-issues.md)
* [Application Dashboard](/product-guides/integral-zone/iz-suite/iz-eye/dashboard.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/applications/projects.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.