> For the complete documentation index, see [llms.txt](https://docs.xygeni.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xygeni.io/introduction-to-xygeni/key-concepts/risk-level.md).

# Risk Level

### Risk Level <a href="#risk_level" id="risk_level"></a>

The **Risk Level** (RL) is a quantitative metric that assesses the current **exposure** to software supply chain attacks. It evaluates the ***security posture*** of the DevOps system based on scans conducted by the Xygeni platform.

In the [Dashboard](/introduction-to-xygeni/xygeni-web-ui-overview.md#xygeni-web-ui), the **Risk Level** is displayed alongside its variation in relation to the current baseline of projects.

The Risk Level is quantified on a scale from 0 to 100, with 100 indicating the highest level of risk. This measure is determined by the issues identified within a project. If no issues are detected, the Risk Level is rated as 0.

The RL is qualified in three categories that make more evident how good or bad is the risk for the organization. Each category is encoded with a color following the "semaphore" scheme:

* **Low**: RL between 0 and 33, green color.
* **Moderate**: RL between 33 and 66, yellow color.
* **High**: RL between 66 and 100, blood-red color.


---

# 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.xygeni.io/introduction-to-xygeni/key-concepts/risk-level.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.