To perform an in-depth cybersecurity risk assessment, start by accessing the Source Code Management (SCM) system. Then, conduct a thorough code review, analyze third-party packages, and examine build files, among other steps. Throughout this process, take care to avoid any unintended interaction with the original customer’s code.

Please follow these steps to provide us access to a forked repository:

1. Make sure that the relevant repository is on Private visibility.

2. On the right panel of the original repository name, click “Fork” to create an independent snapshot of this repository, and then click on the “Create fork” button.

3. On the forked repository, click on Settings.

5. Copy the email address [email protected] to the search field and choose “Invite to {RepositoryName}”.

6. Verify that the role is checked on “Read” privileges and click “Add [email protected] to this repository”.

7. On the same page, under the Base Role section, click on the “Manage” button to edit the created member privileges.

8. Allow the option of forking private repositories and save the changes. It will not apply this option on all the repositories by default.

9. Go back to the forked repository and access the Settings tab. In the General section, locate the new feature called ‘Allow forking’ and check the box. This lets us create a separate snapshot of the repository we just gained access to.”

10. We will receive a notification regarding the invitation to this repository. Once accepted, we will have collaborator access to the repository.

11. If the “Allow forking of private repositories” option was disabled, disabled it again.