For integration, you need the paid SourceCraft Security add-on. The cost is based on the SourceCraft pricing policy.
Repositories are created in the same Yandex Cloud organization where the GitLab instance is located. This organization may be different from the personal organization created automatically during your sign-up to SourceCraft. Make sure the add-on is enabled exactly for the organization the instance is in.
By enabling the integration, you confirm sending the source code to SourceCraft. All repositories of the GitLab instance are mirrored, regardless of their visibility settings. In SourceCraft, mirrored repositories are created as private.
Enabling integration
Enable the SourceCraft Security add-on to for your organization
Navigate to the Organizations list and select the Yandex Cloud organization containing the GitLab instance.
On the organization's page, under Security, open the Overview section.
Make sure the SourceCraft Security add-on is enabled. If a prompt to enable the Security add-on appears instead of scan results, enable it for the selected organization.
If a trial period is available, click Start free trial and follow the instructions in the UI. If you do not have permission to connect the add-on, contact your organization's administrator.
Enable integration in the GitLab instance settings
Management console
In the management console, select the folder containing your GitLab instance.
Select your instance and click Edit in the top-right corner of the page.
Under SourceCraft integration, enable Enable SourceCraft integration.
Click Save.
Wait for the instance update to complete: its status will switch from Updating to Running, and in the Overview section, the SourceCraft integration field will show Enabled.
Tip
You can also enable integration when creating the GitLab instance. First, connect the SourceCraft Security add-on to the organization where the instance will be created.
Wait for the repositories to be mirrored
SourceCraft UI
Open the organization for which you have enabled the SourceCraft Security add-on.
Navigate to the organization's repository list and wait for the mirrored repositories of the GitLab instance to appear.
Their names are derived from the path of the source repository, e.g., test-group/test-subgroup/example-repo is transformed into test-group-test-subgroup-example-repo. Learn more about address transformation.
Note
Scans are triggered when commits are pushed to the default branch of the GitLab source repository. Wait for the code to synchronize and the checks to complete, then view the results in SourceCraft.
Disabling integration
Management console
In the management console, select the folder containing your GitLab instance.
Select the organization where the GitLab instance is located. Its vulnerability control center displays results for all repositories of this organization that are accessible to you.
SourceCraft UI
To open the security dashboard for an organization:
On the Home tab, navigate to Repositories and select a repository.
Under  Security on the repository page, go to  Overview.
The Secret scanning alerts, Dependency scanning alerts, and Code analysis alerts dashboards provide the following statistics:
Alert status.
Resolved alerts breakdown.
Alerts by severity level (Dependency scanning alerts and Code analysis alerts dashboards).
To download SARIF (Static Analysis Results Interchange Format) or SBOM (Software Bill of Materials) files in SPDX format for audit or integration with external systems, click Download SARIF or Download SBOM on the dashboard.
The security dashboard also shows the last scan time.