> 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-ci-and-cd-tools/github.md).

# GitHub

GitHub is a tool that allows developers to create, store, manage and share their code.

## Usage of Github in Delivery Shield

* Delivery Shield can run security analysis to identify the GitHub security posture using frameworks such as OpenSSF Scorecard.
* It also collects metadata such as repository name, branch, list of commits, approvers etc., to perform supply chain security-related analysis and populate it on the DBOM for audit purposes.
* It can run security scans such as SAST, Secret Scan and license scan on GitHub repositories.

## To Integrate Delivery Shield:

1. Navigate to \*\*Setup \*\*> **Integrations**.
2. In the **Source** panel, click **Github**.
3. The Github integration page is displayed. Click **+New Account**.
4. In the popup that appears, enter the values for the following:
5. Enter the \*\*Account Name, API URL, Authentication Type \*\*and **Token** values of your Github account.
6. 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. > **\[info]** You can select up to 5 teams for the integration to be displayed.

* A sample is given below for reference:![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXeuMZQzZsZQuulVdW9B9OuffNPoEXqbcpcAkYtKVyb7YiTQxbVIt1L4Gh-zshqX2J9MFKIat8x4oWFIGxdg3j1XVagyUNhUAlD_52soyMyd1cy53p6XiYi0LsTjIBfHcybRWl61?key=D9EXoOdGF7oYOBvYaW2GnRWJ)
* In the example above,
* 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**.
* 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:**
  * 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.

3. Click **Save**. The tool is integrated in the source stage.
4. To delete the integration, click the **Delete** button.
5. You can edit the entered Github values by clicking the **Edit** option as shown below:
6. Enter the new values and click **Update**.

The new values get updated.