Skip to content

[TEC-547] Export AI findings to csv #2549

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
abhijna merged 2 commits into from
Apr 9, 2026
Merged

[TEC-547] Export AI findings to csv #2549

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b3ac344
export to csv edits
abhijna Apr 8, 2026
d632017
Update src/components/procedure/_export-findings-csv.md
abhijna Apr 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions docs/deployment/ai-powered-detection.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,19 +49,20 @@ To scan a non-default branch:

## View findings

Findings generated by AI-powered detection scans are part of Semgrep Code and are listed on the **[Code](https://semgrep.dev/orgs/-/findings)** page. You can use the filters icon to filter for **AI-powered scan findings**.
Findings generated by AI-powered detection scans are part of [Semgrep Code findings](/semgrep-code/findings) and are listed on the **[Code](https://semgrep.dev/orgs/-/findings)** page. You can use the filters icon to filter for **AI-powered scan findings**.

The findings card indicates whether a finding was deterected by an AI-powered scan or a Rule-based scan.
The findings card indicates whether a finding was detected by an AI-powered scan or a Rule-based scan.


## Add additional context to AI-Powered detection scans

By uploading project-specific context such as design documents, threat models, or instructional markdown, you can provide additional information for Semgrep to use during AI-powered scans. This enables Semgrep to show higher-impact findings and reduce false positives based on how your application is designed and used.
## Add additional context to AI-powered detection scans

:::info
Only **Admins** can upload context documents to Semgrep Projects.
Only **Admins** can upload context documents to Semgrep projects.
:::

By uploading project-specific context such as design documents, threat models, or instructional markdown, you can provide additional information for Semgrep to use during AI-powered scans. This enables Semgrep to show higher-impact findings and reduce false positives based on how your application is designed and used.


To upload a project-specific context document:

1. Log in to Semgrep AppSec Platform.
Expand Down
5 changes: 3 additions & 2 deletions src/components/procedure/_export-findings-csv.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,11 @@ Export findings by navigating to the product page and clicking the **<i class="f
| ------- | ------ |
| Id | The unique ID number of the finding. |
| Rule name | The name of the rule. |
| Product | The Semgrep product. Possible values are **Code**, **Supply Chain**, or **Secrets**. |
| Product | The Semgrep product. Possible values are **Code**, **Code (AI)** **Supply Chain**, or **Secrets**. |
| Severity | The finding's severity. Possible values are **Critical**, **High**, **Medium**, or **Low**. |
| Status | The finding's triage status. |
| Assistant component | A descriptor, such as `API`, `Payments processing`, `Infrastructure`, that Multimodal tags the finding with, based on the code's context. |
| Confidence | Filter by the likelihood of the rule to detect true positives. The higher the confidence, the more true positives the rule may detect. |
| Multimodal component | A descriptor, such as `API`, `Payments processing`, `Infrastructure`, that Multimodal tags the finding with, based on the code's context. |
| Repository name | The name of the repository where Semgrep found the finding. |
| Repository URL | The repository URL. |
| Line of code URL | The URL to the specific line of code where the finding match began. A finding may be several lines long. |
Expand Down
Loading