# VibeSec Prevented Risks

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="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-63f91fc9aa8cff4da713a297979e050df0b5ce37%2FVibeSec%20Prevented%20Risks.png?alt=media" 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                                           |