Skip to main content

​
Scanning your repository

Prerequisite You registered in CorgeaPrerequisite You have completed a scan
Depending on the size of the results in the scan, it may take sometime for results to show up. For a couple of hundred findings, it should take 10 mins. Go to scanning to learn more.
1

Select an Issue

  • Navigate to the projects page.
  • Choose a project.
  • Click on a Scan.
  • Find an issue row with the Fix Available or On Demand status.
  • Click the issue row to open the issue details sidebar.
A scan finding with Auto-Fix set to Fix Available
A scan finding with Auto-Fix set to On Demand
A scan finding with Auto-Fix set to On Hold
2

Review the fix

Review the suggested fix in the issue details sidebar before applying it.If the issue is marked On Demand, Corgea starts generating the fix in the background when you open the issue. This usually takes a minute or two. The fix appears automatically when it is ready.
The Suggested Fix tab while Corgea generates a fix
API clients can start the same background generation with GET /api/v1/issue/{id}. generate_fix defaults to true. While generation is pending, auto_fix_suggestion.status is generating — fetch the issue again until it finishes. Pass wait_for_the_fix=true to wait up to 120 seconds for the result in the same request. See the API reference.Corgea generates fixes using AI and runs quality checks before making them available. We still strongly recommend reviewing the suggested change for correctness and fit in your codebase before applying it.
3

Apply the fix

If the fix seems appropriate, there are two ways to apply fixes:
  • Option 1: Corgea Web Application In the issue details sidebar, click on the Create Pull Request button.
    To issue a pull-request from Corgea, you need to setup the appropriate integration with GitHub or Azure DevOps.
    For findings from CLI or IDE scans, pull request creation requires an active source control integration for the repository and the scanned branch to exist on the remote. If Corgea reports that the branch is missing, push it and reload the issue page.
    Issue page warning that the scanned branch is not on GitHub, so a pull request cannot be created until you push the branch and reload
    Corgea automatically generates a pull request with issue and fix context. Wait for PR creation to complete, then click View Pull Request.
    Alternatively, use Download Fix and select one of the available options:
    • Download Git Patch
    • Download Fixed File
  • Option 2: Corgea IDE Extensions Corgea supports applying fixes locally using our IDE extensions. Corgea supports Visual Studio Code, Visual Studio 2022, and JetBrains IDEs.
    In Visual Studio Code, click a vulnerability in the sidebar to open issue details, review the suggested fix, then click Apply Fix and save the updated files. In a JetBrains IDE, click a finding in the Corgea tool window to open its details, review the suggested fix, then click Apply Fix and save the updated files.
4

Optionally: Vote on the fix

If the fix is good or bad, please leave a vote, and ideally a comment. We review your feedback and use it to make Corgea better, so we greatly appreciate them.
Click Give Feedback to open the feedback modal. In the modal, you can select a thumbs up or thumbs down, add an optional comment, and click Submit.

​
Troubleshooting

For issues marked On Demand, open the issue details sidebar to generate the fix. If generation fails, or if a previously available fix needs to be regenerated, click Try Again.
The Suggested Fix tab when generation fails, with a Try Again button
For issues still marked as processing, it might take several minutes to hours for a fix to be generated based on the backlog of other fixes that you sent.
Please leave a vote using the thumbs up and down icons, and ideally a comment. We review your feedback and use it to make Corgea better, so we greatly appreciate them.