# VibeSec Prevented Risks Report

The VibeSec Prevented Risks report provides a detailed view of security risks that were prevented during development through VibeSec guidance.

This report helps you understand which vulnerabilities were avoided, where they occurred, and which developers and applications were involved.

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

## Prevented Risks

This table lists all security risks that were proactively prevented by VibeSec.

Each entry represents a case where insecure code was identified and corrected during development before becoming a vulnerability.

| Column           | Description                                                                                     |
| ---------------- | ----------------------------------------------------------------------------------------------- |
| **User**         | The developer whose code was secured                                                            |
| **Risk**         | The type of vulnerability that was prevented (for example, Path Traversal, SSRF, SQL Injection) |
| **App**          | Application or repository where the risk was identified                                         |
| **Timestamp**    | When the prevention occurred                                                                    |
| **File**         | The file in which the risk was detected                                                         |
| **Line of Code** | The location in the file where the risk was prevented                                           |


---

# Agent Instructions: 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:

```
GET https://docs.ox.security/generate-reports/built-in-reports/vibesec-prevented-risks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.