> 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/xygeni-products/compliance.md).
# SSCS Compliance
The **Compliance page** provides a comprehensive view of all your project(s) compliance with [Supported compliance standards](/xygeni-products/compliance/compliance-scanner/supported-compliance-standards.md).
{% hint style="info" %}
You can reach the **Compliance page** either by selecting **Compliance** in the Navigation Bar or selecting the **Compliance** tab of the Supply Chain page.
{% endhint %}
### Project Group View
If you have selected ***All projects*** or a subset of projects, you will see this general view.
You can see the compliance level of all the supported standards for the selected projects group. These charts will provide you with a high level view of the general coverage of checkpoints per standard.
Furthermore, you can see a list with all the projects together with its respective compliance level for every standard.
{% hint style="info" %}
Clicking on the icon a project will take you to the [Single Project view](#single-project-view).
{% endhint %}
### Single Project View
Opening the Compliance page for a selected single project will display as the below image.
This page will show statistics for every standard that the selected project has been assessed:
* Overall view of passed/failed checkpoints
* Checkpoints by result
* A list of all the checkpoints together with its pass status
Clicking on icon of any checkpoint will open a slide with the details
---
# 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/xygeni-products/compliance.md?ask=&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.
