Source Code Integration: Settings

Source Code Integration: Settings

Overview

The settings screen for the Source Code Integration (“SCI”) provides detailed information about the SCI scan and outlines the steps to integrate Relyance AI with your source code repositories. This settings page is divided into 2 main cards:

1. Source Code Analyzer Status

This card enables Relyance administrators to view detailed information about the source code scan(s). The metrics and information displayed (such as repo name, number of files scanned, etc.) create visibility into the code repositories Relyance is integrated with.

If no code repositories have been integrated with Relyance, the card displays “Not Completed”.

If code repositories have been integrated with Relyance, then this card will display a list of code repositories that are sorted by the most recently scanned. On clicking a specific code repository name, the following information is displayed:

1. Repository: The name and URL of the repository.
2. Last Scan Time: The last repository scan time (specific date and the relative time from the current date).
3. Lines of Code:
   • The number of lines of code that were scanned during the most recent scan of the repository.
   • A chart showing historical data for the lines of code scanned in previous runs. Hover over the chart to get more information about previous SCI runs.
4. Files Scanned:
   • The number of files that were scanned during the most recent scan of the repository
   • A chart showing historical data for the number of files scanned in previous runs. Hover over the chart to get more information about previous SCI runs.
5. Products: A list of products related to the repository as defined in the YAML file.
6. Services: A list of services related to the repository as defined in the YAML file.
7. Directories Scanned: A list of the directories that were scanned by Relyance in the repository as defined in the YAML file.

The history of scans goes back three months only.

2. Setup Relyance Compliance Inspector

This card outlines high-level instructions to set up the Relyance Compliance Inspector.

Step 1: The “Download Sample” button allows the user to download a sample “relyance.yaml” file that needs to be placed in the root of the code repository.

Step 2: Displays the tenant-specific one-line docker pull command that can be integrated into a CI pipeline to run the Relyance scan.

For more information about the technical configuration of the Source Code Inspector, please refer to this article.