View the GitHub Application Vulnerability Integration import run status and imported repository data

Use the Vulnerability Integration Runs related list to verify the success of your integration runs, locate any issues, and inform your remediation decisions.

Before you begin

Role required: sn_vul.app_sec_manager

Procedure

1. Navigate to All > GitHub Vulnerability Integration > Integrations.
2. Select an integration.
3. Select the Vulnerability Integration Runs related list.
4. Verify that all imports have succeeded.
   The most common causes for a failed run include:

   • Network interruption.
   • An issue in the data transfer resulting in corrupted data during the transform.
   Some other common errors and solutions are included in the following list.

   Symptom: 401 from GitHub

   Likely cause: Token expired or insufficient scope.

   Fix: Re-issue token with §3.1 scopes, update sn_vul_github_config.token.

   Symptom: Some repos missing in Enterprise mode

   Likely cause: Token not granted to that org under Enterprise/Personal access tokens.

   Fix: Approve the PAT for the missing org(s).

   Symptom: 403 / rate-limit

   Likely cause: Burst pulls exceeded GitHub primary rate limit.

   Fix: Stagger schedules across sub-integrations; reduce ds_group_number parallelism by deactivating individual sources 2–4 if needed.

   Symptom: Generic-secret findings missing

   Likely cause: manage_generic_secrets_in_snow = false.

   Fix: Set to true and wait for next Secret Scanning run.

   Symptom: scan_type=secret instead of generic_secret for old data

   Likely cause: One-shot data fix 7763a5069f… not yet run.

   Fix: Set its run_type back to periodically once; it will re-run and self-disable.

   If you encounter any of these conditions, select Execute Now, and rerun the integration.

5. To view imported repositories, navigate back to the integrations list and select the GitHub Repos Integration record.
6. Select the Vulnerability Integration Runs related list and open a record.
   The number of repositories you imported with an integration run is displayed in the Imported items column.

   Any tags and topics you have configured for a repository in your GitHub account from the Settings menu are imported. Any imported Custom properties are located on the menu under your Repository.

   Tags, topics, and custom properties are imported into your instance only if they are configured in your GitHub account.

   If imported, this GitHub information is displayed in your instance on the Source additional info column on the Discovered Applications [sn_vul_app_release] table and the Source additional info. section on a discovered application record. Custom properties are displayed as key-value pairs, and tags and topics are displayed in arrays.