• Semgrep Supply Chain
• Semgrep AppSec Platform

Triage and remediate dependency findings

Perform triage and remediation on your open source dependencies through the Supply Chain page. This page displays relevant scan data through three tabs:

Vulnerabilities

This tab enables you to:

• View reachable vulnerabilities in your repositories through links to specific lines of code.
• Filter vulnerabilities by severity, reachability, status, transitivity, and other attributes.
• Understand how to remediate vulnerabilities by providing versions to upgrade to.
• Track the process of resolving vulnerabilities by adding links to Jira issues and pull requests.

Advisories

This tab displays the latest Common Vulnerabilities and Exposures (CVEs) that are covered by Semgrep Supply Chain rules. Use this tab to see the CVEs that Semgrep Supply Chain can detect.

Dependencies

This tab displays information about all of your dependencies across all onboarded repositories.

License configuration

This tab allows you to explicitly allow or disallow (block) a package's use in your repository based on its license.

Figure 1. Semgrep Supply Chain Vulnerabilities page.

Assess and triage dependency findings and usages

Prerequisite

At least one repository that scans for dependencies through Semgrep Supply Chain. See Scan third-party dependencies.

To view the latest Semgrep Supply Chain findings, click Supply Chain. You can view findings individually or grouped by the rule that identified the finding. A specific finding in the code is called a usage. Vulnerability entries are sorted as cards by severity from critical to low, then from oldest to newest.

Figure 2. A single vulnerability entry in Semgrep Supply Chain.

You can also view the findings individually by clicking on the drop-down box on the header and clicking No grouping.

Default Supply Chain > Vulnerabilities tab view

tip

• If you do not see any findings, or there are zero findings after a scan has concluded, check the Projects page to view the findings count, if any, and to set a primary branch, if it is not already set.
• The total count of findings in the Projects page is based on the latest scanned branch, not the primary branch, so it may differ.

A single finding may appear in several branches. These appearances are called instances of a finding. Several instances of the same finding may differ in which line of code (LOC) they are on or in their triage state. For example, on production the finding may be on line 20, but the same finding was moved further to line 26 in feature-branch-a.

Semgrep automatically recognizes that they are fundamentally the same finding and deduplicates these instances so that you do not get an inflated count of findings per ref that the finding is present in.

By default, the Supply Chain page displays findings from the primary branches of all repositories (projects), arranged by most recent scan. You are viewing the primary branch's instance of that finding, so you may see variations in LOC or triage state when comparing the finding across branches.

When filtering by primary branch and triage status, the filters are applied based on the triage status of the finding on the primary branch. This means that on some feature branches, the instance may already be Fixed, but on the primary branch, the finding is still Open. The finding status on the primary branch is updated when the PR or MR is merged and Semgrep has scanned the code.

Assessment actions

To assess your findings, Semgrep Supply Chain provides the following methods:

Assessment action	Method
View specific pattern matches in your codebase.	Click the link provided in the vulnerability entry to see where the issue appears in the source code.
View specific CVE entries in cve.org.	Click the vulnerability's CVE badge.
View safe versions to upgrade your dependencies.	Visible on the vulnerability entry.
Filter vulnerabilities.	Click any of the filters available. Refer to the following table for filtering information.

Filters

Use filters to narrow down your results. The following criteria are available for filtering:

Filter	Description
Projects and branches	Filter by repositories connected to your Semgrep account and by findings in different Git branches.
Tags	Filter for findings based on the tags associated with the project.
Status	Filter the triage state of a finding: Open: Findings for which there have been no triage or remediation action. Reviewing: Findings that require more investigation to determine what the next steps should be. Fixing: Findings for which you have decided to fix. Commonly used to indicate that these findings are tracked in Jira or assigned to developers for further work. Ignored: Vulnerabilities that have been triaged as Ignored by the user. Fixed: Vulnerabilities that are no longer detected after a scan. This typically means that the dependency containing the vulnerability has been updated. Semgrep Supply Chain automatically checks if the dependency has been updated and sets the vulnerability's status as Fixed.
Severity	Filter by the severity of a finding. Filters are based on the severity of a vulnerability. Semgrep Supply Chain rules use severity values set by the GitHub Advisory Database.
Transitivity	Filter by the transitivity of the finding. Direct: Your project depends directly on the dependency. Transitive: Your project's dependency depends on a vulnerable dependency. Undetermined: Semgrep had no transitivity information for the dependency as it relates to your project.
EPSS probability	Exploit prediction scoring system (EPSS) probability. Represents the likelihood that the vulnerability will be exploited in the wild in the next 30 days. Values range from 0% to 100% where the higher the score, the greater the probability the vulnerability is exploited. Semgrep groups probabilities as follows: High: 50 - 100% Medium: 10 - <50% Low: <10%
Reachability	Filter by exposure, or whether the finding is reachable or not. Reachable: A finding is reachable if there's a code pattern in the codebase that matches the vulnerability definition Always reachable: A finding is always reachable if it's something Semgrep recommends fixing, regardless of what's in the code. Conditionally reachable: A finding is conditionally reachable if Semgrep finds a way to reach it when scanning your code when certain conditions are met. No Reachability Analysis: A finding that isn't scanned by Semgrep for reachability. Unreachable: A finding is unreachable if you don't use the vulnerable piece of code of the imported library or package.
Dependencies	Filter for findings based on the name of the dependency involved.
Rules	Filter based on the rule that generated the finding.

Remediate true positives

Remediate (or resolve) true positives in Semgrep Supply Chain through the following methods:

• Update the dependency to a safe version that does not contain the vulnerability.
• Remove the dependency and refactor all usages in the codebase.

Remove the dependency and refactoring code

Another method to remediate vulnerabilities is to remove the dependency entirely and refactor code. Upon merging any dependency removals, Semgrep Supply Chain scans the PR or MR, detects the changes in your lockfile, and updates the status to Fixed.

Ignore findings

The Vulnerabilities tab allows you to identify the reachable, true positives so that you can fix or resolve the related issues. However, you can choose to ignore any false positives, acceptable risks, or deprioritized findings due to some factor. To do this:

1. Select one or more findings.
2. Click Triage.
3. Select Ignore and click Continue.
4. Select an Ignore reason, provide a optional comment, and click Ignore.

View Semgrep Supply Chain's total CVE coverage

The Advisories tab displays all the CVEs that Semgrep Supply Chain can detect. Click the individual entry to see the code pattern that the Advisory detects. The Advisories tab displays both lockfile-only and reachability rules.

info

Semgrep ingests CVE information and security advisories from sources such as Reviewed GitHub Security Advisories to ensure effective rule coverage. Semgrep processes new information at least once per day to:

• Generate rules for new security advisories;
• Update rules based on changes to existing security advisories.

---

Not finding what you need in this doc? Ask questions in our Community Slack group, or see Support for other ways to get help.