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

# Policy checks

View policy evaluation results across repositories and dependencies.

Policy checks show whether repositories and dependencies trigger your configured automation policies. Use them to identify policy issues and review the rules behind each result.

### Review repository policy checks

Select a repository's policy-check result to open its details. The panel groups triggered rules by outcome:

* **Failing** — Rules that fail the policy check.
* **Warning** — Rules that generate a warning.
* **Other actions** — Rules configured with another action, such as a notification.

Each group shows the affected conditions, such as vulnerabilities, licenses, or dependencies. Select **Inspect repository rules** to review the rules configured for the repository.

Use **See affected dependencies** to open the dependencies that triggered a rule. Select **Refresh data** to update the policy-check results. The panel also shows when the data was last refreshed.

### All Repositories table

The **Policy Checks** column provides an overview of policy compliance for each repository. Use it to identify repositories that need further review.

### Repository dependencies table

Open a repository to view its dependencies. The **Policy Checks** column shows the policy evaluation result for each dependency.

### Dependency details

Open a dependency to view its details. The **Policy Checks** tab is available alongside the **Security** tab.

The **Triggering Rules** section lists the policy rules triggered by the selected dependency. Review these rules alongside dependency insights, including **Popularity**, **Contributors**, and **Security Scores**.


---

# 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.debricked.com/product/policy-checks.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.
