> 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/changelog/version-5.11-april-11-2025-1-1.md).

# Version 5.11 - April 11, 2025

Version 5.11 introduces key upgrades to enhance developer experience, improve static analysis, and more effectively enforce security controls across builds. This release focuses on usability improvements, better enforcement of secure development policies, and expanded language support in SAST.

### 🧩 Unified Screen Design

We’ve updated all product screens to improve readability and consistency across the platform.

* Key fields like **explanation** and **location** are now always visible
* Homogeneous layouts across risk types make navigation more intuitive
* Original filtering and sorting options remain fully supported

This visual redesign helps teams scan, triage, and act on issues faster—reducing friction and enabling more efficient reviews across large projects.

<figure><img src="https://4096647782-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUTz59rJLkJBjiRWAMknU%2Fuploads%2Fz4AZ0xwwuCMW9qcunTfl%2Fimage.png?alt=media&amp;token=59abe4f6-bfe1-43ff-96e1-129082e8c3e5" alt=""><figcaption></figcaption></figure>

### 🛡️ Guardrail Rule Enhancements

Guardrails now offer more control to enforce build-time security policies with greater precision.

* Create detailed **Go/No-Go rules** for specific scenarios and thresholds
* Update the **baseline directly from the CLI**. No UI interaction is needed

These changes make it easier to integrate Guardrails into automated pipelines and align security enforcement with internal compliance requirements.

<figure><img src="https://4096647782-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUTz59rJLkJBjiRWAMknU%2Fuploads%2FnrqpMIlGxXMPDyxrNYkb%2Fimage.png?alt=media&amp;token=1a32440d-60fe-46f8-9192-dd168bc570a5" alt=""><figcaption></figcaption></figure>

### 🧪 SAST Detection & Performance Improvements

We’ve expanded and optimized our static analysis rules to strengthen detection and reduce overhead.

* New and extended detection rules for **PHP**
* Refined logic and detectors across other supported languages
* **Performance boosts** that reduce scan times for large codebases

These enhancements help teams catch more relevant issues with less delay, improving overall security coverage without slowing development.

<figure><img src="https://4096647782-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUTz59rJLkJBjiRWAMknU%2Fuploads%2FEHHNNh6RKU4UHILb4CgJ%2Fimage.png?alt=media&amp;token=04de36d5-c1eb-47fa-b22d-48842571d7b9" alt=""><figcaption></figcaption></figure>


---

# 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/changelog/version-5.11-april-11-2025-1-1.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.