> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/integrations/integrating-security-scanning-tools/opengrep.md).

# Opengrep

Opengrep is an open-source static analysis tool used for identifying and fixing security issues in source code. It is designed to be fast, developer-friendly, and can be integrated into the development workflow. Opengrep uses a pattern-based approach to detect and fix security vulnerabilities, coding errors, and other issues in codebases.

### Usage of Opengrep in Delivery Shield

* Delivery Shield integrates with Opengrep to perform static analysis on source code, identifying security vulnerabilities, code quality issues, and policy violations early in the development cycle.
* Findings from Opengrep scans are ingested and factored into the application's overall security score, alongside results from other SAST tools.

### To Integrate Opengrep:

1. Navigate to **Setup** > **Integrations**.
2. In the **Source** panel, click **Opengrep**.

<figure><img src="/files/7HoQPKjRjFc9jwXJaGX0" alt=""><figcaption></figcaption></figure>

3. The Opengrep integration page is displayed. Click **+New Account**.&#x20;
4. In the popup that appears, enter the details for the following fields:

<figure><img src="/files/2LlDJ3x6GZyA8My3zrsd" alt=""><figcaption></figcaption></figure>

5. Enter the Account Name.
6. Enable SAST Scan.&#x20;
7. Select the **Teams** and the corresponding **Environments** from the dropdown for which you want the integration to be available. The integration will be available for the selected teams and environment only.&#x20;

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>You can select up to 5 teams for the integration to be displayed. </p></div>

   * An example is given below for reference:

   <figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeuMZQzZsZQuulVdW9B9OuffNPoEXqbcpcAkYtKVyb7YiTQxbVIt1L4Gh-zshqX2J9MFKIat8x4oWFIGxdg3j1XVagyUNhUAlD_52soyMyd1cy53p6XiYi0LsTjIBfHcybRWl61?key=D9EXoOdGF7oYOBvYaW2GnRWJ" alt=""><figcaption></figcaption></figure>

   * In the example above,&#x20;
     * if **Team 1**, **Team 2**, and **Team 3** are selected, only applications associated with these teams can access the integration. Any applications belonging to other teams, such as **Team 4**, will not have access to this account.
     * Even if the user who created this account is also an admin for **Team 4**, the integration account remains restricted and is not available for **Team 4**.&#x20;
     * Access to the account is strictly limited to the specified **Teams** and **Environments** selected during account creation.
   * **For Organization Admins:**
     * When an **Organization Admin** creates an account without selecting specific **Teams** and **Environments**, the account will be universally applicable, granting access to **all teams** and **all environments** by default.
   * **For Team Admins with Multiple Teams:**<br>
     * If a **Team Admin** who manages multiple teams creates an account without specifying particular **Teams** and **Environments**, the account will only be accessible to the teams for which the logged-in user holds admin privileges.
8. Click **Save**. The tool is integrated in the source stage.&#x20;
9. To delete the integration, click the **Delete** button.&#x20;
10. You can edit the entered values by clicking the **Edit** option as shown below:
11. Do the necessary changes and click **Update**.&#x20;

The new values get updated.&#x20;

\
\
\ <br>