> 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-dashboard.md).

# VibeSec Dashboard

The VibeSec Dashboard is the single pane of glass for VibeSec usage and behavioral data across your organization. You can review developer engagement, see which AI BOM elements are in use, and track how often OX prevented risks during code generation.

<figure><img src="/files/jpIEj2d0tdRWMjTOOc4m" alt="" width="563"><figcaption></figcaption></figure>

The main parts of the VibeSec Dashboard are the [Key metrics](https://claude.ai/chat/7ac18b08-8e4e-4345-afa4-2141e356a670#key-metrics) tiles, the [Activity trends](https://claude.ai/chat/7ac18b08-8e4e-4345-afa4-2141e356a670#activity-trends), the [AI BOM Elements Detected](https://claude.ai/chat/7ac18b08-8e4e-4345-afa4-2141e356a670#ai-bom-elements-detected) widget, the [User Statistics](https://claude.ai/chat/7ac18b08-8e4e-4345-afa4-2141e356a670#user-statistics) table, and the [Top 10 Risks Prevented by Vulnerability](https://claude.ai/chat/7ac18b08-8e4e-4345-afa4-2141e356a670#top-10-risks-prevented-by-vulnerability) chart.

### Key metrics

The tiles at the top of the dashboard summarize VibeSec activity for the selected date range.

| Metric              | Description                                                                                                                                                                           |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Active Users**    | Number of developers who actively used VibeSec in the selected date range. A user is counted as active when their AI agent communicates with the OX backend while VibeSec is enabled. |
| **Prompts Secured** | Number of prompts in which VibeSec provided security guidance during code generation.                                                                                                 |
| **Risks Prevented** | Number of security risks prevented by VibeSec in the selected date range.                                                                                                             |
| **Secured Apps**    | Number of applications in which VibeSec actively prevented risks.                                                                                                                     |

### Activity trends

The activity trend charts show how VibeSec usage and protection have changed over the last 90 days.

| Chart                        | Description                                                                                                                    |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **Active Users (Weekly)**    | Number of active VibeSec users per week.                                                                                       |
| **Risks Prevented (Weekly)** | Number of risks prevented per week, including a Policy Blocks series that shows how often OX policies blocked an agent action. |
| **Prompts Secured by Tool**  | Number of secured prompts grouped by AI coding tool (for example, Claude Code, Cursor, Copilot).                               |

### AI BOM Elements Detected

The AI BOM Elements Detected widget shows the volume of AI BOM elements discovered each week. The stacked bar format lets you compare totals over time and see the contribution of each element type at a glance.

| Element type            | Description                                               |
| ----------------------- | --------------------------------------------------------- |
| **MCP servers**         | MCP servers that agents in your environment connect to.   |
| **External SaaS tools** | Third-party SaaS components that agents call out to.      |
| **Models**              | AI models that power agent reasoning and code generation. |
| **Skills**              | Skills available to agents in your environment.           |

### User Statistics

The User Statistics table lists recent VibeSec activity for each developer. Reviewing this table helps you identify the most active users, spot accounts that aren't yet onboarded, and confirm which AI coding tools each developer uses.

| Column              | Description                                                                  |
| ------------------- | ---------------------------------------------------------------------------- |
| **User**            | Developer's email or ID.                                                     |
| **Prompts Secured** | Number of prompts in which VibeSec provided security guidance for this user. |
| **Risks Prevented** | Number of risks prevented for this user.                                     |
| **Tools**           | AI coding tools the user worked with.                                        |
| **Last Used**       | Most recent VibeSec interaction for this user.                               |

### Top 10 Risks Prevented by Vulnerability

The Top 10 Risks Prevented by Vulnerability chart shows the most common vulnerability types VibeSec prevented over the last 90 days, for example XSS, path traversal, SSRF, and SQL injection.

Reviewing this chart helps you understand which risk categories VibeSec catches most often in your environment and where to focus secure-coding training.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ox.security/vibesec/vibesec-dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
