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

# VibeSec Evaluation

You can use the VibeSec evaluation guides to experience how VibeSec protects AI-assisted development and provides visibility and control over AI activity in your organization.

The evaluations use controlled scenarios that demonstrate VibeSec capabilities without introducing actual security risks. Follow each guide to perform the scenario in your AI coding environment and review how VibeSec responds.

The evaluation guides cover the following areas:

* [**Code security guidance:**](/vibesec/vibesec-evaluation/evaluate-vibesec-code-security-guidance.md) Evaluate how VibeSec provides security guidance while developers use AI coding assistants to generate code.
* [**AI BOM visibility and governance:**](/vibesec/vibesec-evaluation/evaluate-vibesec-mcp-ai-bom-governance.md) Evaluate how VibeSec identifies MCP (Model Context Protocol) servers used by AI coding assistants and enables you to control access to MCP servers and their tools.
* [**Malicious dependency protection:** ](/vibesec/vibesec-evaluation/evaluate-vibesec-malicious-dependency-protection.md)Evaluate how VibeSec prevents AI coding assistants from installing dependencies identified as malicious.

Each evaluation guide provides the instructions and expected results for its scenario.


---

# 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.ox.security/vibesec/vibesec-evaluation.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.