> ## Documentation Index
> Fetch the complete documentation index at: https://docs.semgrep.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Semgrep Supply Chain FAQ

> Answers to common questions about Supply Chain setup, CVE coverage, rescans, reachability, triage, malicious dependencies, licenses, and SBOMs.

This page answers common questions about Semgrep Supply Chain. Each answer links to the page with the full details.

## Getting started

> [accordion] Do I need a lockfile to scan my project?
>
> Supply Chain reads the dependencies in a project's manifest files or lockfiles. For projects without a lockfile, or with an incomplete one, Dynamic Dependency Resolution (beta) can resolve dependencies for Maven and Gradle, pip `setup.py` projects, and NuGet. Dynamic Dependency Resolution doesn't work on Windows.
>
> If you scan a manifest file, Supply Chain reports vulnerabilities for dependencies with exact (pinned) versions. Starting with Semgrep CLI version 1.184.0, Supply Chain also reports vulnerabilities for dependencies in a Python `requirements.txt` file that declare a version range or no version. These findings are labeled [**Needs review**](https://docs.semgrep.dev/semgrep-supply-chain/findings#reachability) because Semgrep can't determine the installed version.
>
> For more information, see [Dynamic Dependency Resolution (beta)](https://docs.semgrep.dev/semgrep-supply-chain/set-up-and-configure.md#dynamic-dependency-resolution-beta).

> [accordion] Which languages and package managers does Supply Chain support?
>
> Supply Chain supports specific package managers and manifest file or lockfile names for each language. Reachability analysis is available for generally available (GA) languages.
>
> For the full list, see [Supply Chain requirements and feature support](https://docs.semgrep.dev/semgrep-supply-chain/requirements-and-feature-support.md) and [Supported languages](https://docs.semgrep.dev/supported-languages).

> [accordion] Can Supply Chain scan a monorepo?
>
> Yes. Supply Chain groups findings by directory, based on the nearest manifest file or lockfile. Code files are associated with the dependencies in the manifest file or lockfile in the same directory or a parent directory.
>
> For more information, see [Scan a monorepo's dependencies](https://docs.semgrep.dev/semgrep-supply-chain/set-up-and-configure.md#scan-a-monorepos-dependencies).

> [accordion] Do I need to connect my private registry?
>
> Connect a private registry if you want to open Autofix pull requests or merge requests, generate Upgrade Guidance, or run Semgrep Managed Scans on projects that use Maven registries.
>
> For more information, see [Connect a private registry to Semgrep](https://docs.semgrep.dev/kb/semgrep-supply-chain/connect-a-private-registry.md).

## Coverage for new vulnerabilities

> [accordion] How quickly does Semgrep add coverage for a new CVE?
>
> Semgrep ingests new CVEs and security advisories from its sources multiple times per day, and generates rules for new advisories or updates existing rules. Your projects get the new rules the next time Supply Chain scans them.
>
> For more information, see [New CVEs and rule updates](https://docs.semgrep.dev/semgrep-supply-chain/overview.md#new-cves-and-rule-updates).

> [accordion] Does Semgrep cover unreviewed GitHub Security Advisories?
>
> Not by default. Semgrep generates rules from [reviewed GitHub Security Advisories](https://github.com/advisories?query=type%3Areviewed), not unreviewed ones. For major incidents, or when customers request it, Semgrep's Security Research team can publish its own advisories, even before third-party databases are updated.
>
> For more information, see [New CVEs and rule updates](https://docs.semgrep.dev/semgrep-supply-chain/overview.md#new-cves-and-rule-updates).

> [accordion] Does Semgrep cover known exploited vulnerabilities (KEVs)?
>
> Yes. Semgrep processes vulnerabilities in the [CISA Known Exploited Vulnerabilities Catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog) the same way it processes other types of vulnerabilities.
>
> For more information, see [New CVEs and rule updates](https://docs.semgrep.dev/semgrep-supply-chain/overview.md#new-cves-and-rule-updates).

> [accordion] How quickly does Semgrep respond to a malware incident?
>
> For major security incidents, Semgrep's Security Research team delivers rules that check for malicious package versions to all customer accounts. Semgrep notifies you when it declares a threat if you've set up threat notifications.
>
> For response times and what to do while you wait, see [Verify that your next scan includes rules for the incident](https://docs.semgrep.dev/semgrep-supply-chain/incident-response.md#2-verify-that-your-next-scan-includes-rules-for-the-incident).

> [accordion] What happens if an incident affects packages that Supply Chain doesn't support?
>
> Supply Chain can only report findings for dependencies in the ecosystems and package managers it supports. When an incident affects software outside those ecosystems, Semgrep's Security Research team can add coverage for affected packages that Supply Chain does support, and can publish Semgrep Code rules to help you find affected code that Supply Chain can't detect. Coverage for these incidents can grow as Semgrep learns about more affected packages.
>
> For the ecosystems that Supply Chain supports, see [Supply Chain requirements and feature support](https://docs.semgrep.dev/semgrep-supply-chain/requirements-and-feature-support.md).

## Findings and scans

> [accordion] When do findings for a new vulnerability appear in my projects?
>
> Semgrep uses the latest rules each time it scans a project, so findings for a new vulnerability appear after the next Supply Chain scan of each affected project. How soon that happens depends on how often you scan. To pick up rule updates quickly, scan your projects on a schedule as well as on pull requests or merge requests.
>
> For more information, see [Scan frequency](https://docs.semgrep.dev/semgrep-supply-chain/set-up-and-configure.md#scan-frequency).

> [accordion] Does Semgrep rescan my projects automatically when it adds a new rule?
>
> Not for routine rule updates. Semgrep rescans projects automatically only when it declares a Supply Chain threat that comes with rules, and only if your organization has configured the **Early notification for Supply Chain threats** policy and the project is eligible. All other projects get the new rules at their next scan, whether that's a scheduled scan, a scan triggered by a pull request or merge request, or a scan that you start yourself.
>
> For which projects are eligible and how to start scans yourself, see [Initiate scans on potentially affected projects with Semgrep rules](https://docs.semgrep.dev/semgrep-supply-chain/incident-response.md#3-initiate-scans-on-potentially-affected-projects-with-semgrep-rules).

> [accordion] Why did a finding I already triaged come back as a new finding?
>
> When Semgrep updates a rule, findings from the updated rule are new findings, even if the previous version of the rule produced a finding at the same place. Triage actions on findings from the earlier rule version don't carry over, and you get notifications for the new finding through the channels you've set up.
>
> For more information, see [Rule updates](https://docs.semgrep.dev/semgrep-supply-chain/set-up-and-configure.md#rule-updates).

> [accordion] Why isn't Supply Chain showing findings for my project?
>
> Common causes include an unsupported language or package manager, a manifest file or lockfile with a nonstandard name or location, and a manifest file without pinned versions. Python `requirements.txt` files are an exception: dependencies with version ranges still produce findings that need review.
>
> For a full checklist, see [Why aren't Supply Chain findings showing?](https://docs.semgrep.dev/kb/semgrep-supply-chain/why-no-findings.md)

> [accordion] How do I find out when Semgrep declares a new threat?
>
> Configure the **Early notification for Supply Chain threats** policy. Semgrep posts to a Slack channel or webhook when it declares a threat, and tells you whether any of your projects are affected based on their most recent dependency data. This policy is also required for automatic rescans of eligible projects.
>
> For more information, see [Supply Chain threat notifications and response](https://docs.semgrep.dev/semgrep-supply-chain/incident-notifications.md).

## Reachability

> [accordion] What's the difference between reachable, unreachable, and no reachability analysis?
>
> * **Reachable**: your code matches the vulnerable code pattern. A finding is **always reachable** when upgrading the dependency is the only fix, and **conditionally reachable** when it's exploitable only under conditions that Semgrep can't check, such as a specific operating system. Conditionally reachable findings require manual review.
> * **Unreachable**: you don't use the vulnerable package, or you don't use its vulnerable code.
> * **No reachability analysis**: you use a vulnerable version of the dependency, but Supply Chain doesn't have a reachability rule for the vulnerability.
>
> For more information, see [Types of Supply Chain findings](https://docs.semgrep.dev/semgrep-supply-chain/overview.md#types-of-supply-chain-findings).

> [accordion] Why don't all findings have reachability analysis?
>
> Semgrep writes reachability rules for all critical and high severity CVEs in GA languages. For other vulnerabilities, and for languages without reachability rules, Supply Chain checks the dependency's version against the versions with known vulnerabilities and reports **no reachability analysis**.
>
> For more information, see [Types of Supply Chain findings](https://docs.semgrep.dev/semgrep-supply-chain/overview.md#types-of-supply-chain-findings).

> [accordion] Does Supply Chain scan transitive dependencies?
>
> Yes, for all supported languages. Supply Chain doesn't run reachability analysis on transitive dependencies, so it doesn't check whether your dependencies use a vulnerable transitive dependency. However, if a dependency is vulnerable just by being included in a codebase, Supply Chain reports a reachable finding even when it's a transitive dependency.
>
> For more information, see [Transitive dependencies and reachability analysis](https://docs.semgrep.dev/semgrep-supply-chain/overview.md#transitive-dependencies-and-reachability-analysis).

## Triage and fix

> [accordion] How do I stop specific files, dependencies, or rules from generating findings?
>
> * To ignore a code file, manifest file, or lockfile, add its path to a `.semgrepignore` file. Ignoring a code file stops its reachable findings. Ignoring a manifest file or lockfile stops findings from its dependencies.
> * To skip a specific rule, pass its rule ID to `semgrep ci --exclude-rule`.
>
> For more information, see [Ignore manifest files, lockfiles, and dependencies](https://docs.semgrep.dev/semgrep-supply-chain/ignoring-deps.md) and [How to exclude a Semgrep Supply Chain rule from a scan](https://docs.semgrep.dev/kb/semgrep-supply-chain/exclude-rule.md).

> [accordion] What's the difference between Upgrade Guidance and Autofix?
>
> Upgrade Guidance (beta) analyzes a finding to determine whether you can upgrade the vulnerable dependency to a fixed version without breaking your code. It's available for JavaScript and Python projects on GitHub Cloud or GitLab Cloud, and requires Semgrep Multimodal.
>
> Autofix opens a pull request or merge request that upgrades the vulnerable dependency to a fixed version. Autofix doesn't require Upgrade Guidance, but when Upgrade Guidance analysis is complete, Semgrep can include it in the pull request or merge request description.
>
> For more information, see [Upgrade Guidance (beta)](https://docs.semgrep.dev/semgrep-supply-chain/upgrade-guidance.md) and [Supply Chain Autofix](https://docs.semgrep.dev/semgrep-supply-chain/autofix.md).

## Malicious dependencies

> [accordion] Which ecosystems can Semgrep detect malicious dependencies in?
>
> Semgrep can detect malicious dependencies for NuGet, Go modules, npm, Composer, PyPI, RubyGems, and Cargo.
>
> For more information, see [Detect and remove malicious dependencies](https://docs.semgrep.dev/semgrep-supply-chain/malicious-dependencies.md).

## Licenses and reporting

> [accordion] Can Semgrep block dependencies based on their license?
>
> Yes. You can set each license to **Allow**, **Comment**, or **Block**. All licenses are set to **Allow** by default. **Comment** and **Block** apply only when a pull request or merge request adds a dependency or changes a dependency's version in a way that introduces a new license. **Block** also makes the diff-aware scan exit with code 1.
>
> For more information, see [Types of license policies](https://docs.semgrep.dev/semgrep-supply-chain/license-compliance.md#types-of-license-policies).

> [accordion] Which SBOM formats does Semgrep support?
>
> Semgrep generates software bills of materials (SBOMs) in JSON or XML for CycloneDX versions 1.4 through 1.7. An SBOM uses the vulnerability information from the project's default branch and the dependency information from the project's latest full scan.
>
> For more information, see [Supported standards and formats](https://docs.semgrep.dev/semgrep-supply-chain/sbom.md#supported-standards-and-formats).

> [accordion] How do I export Supply Chain findings?
>
> Semgrep AppSec Platform exports the 10,000 most recent findings to a CSV file. Filters on the **Findings** page don't apply to the export. To export more than 10,000 findings, use the Semgrep API.
>
> For more information, see [Export findings](https://docs.semgrep.dev/semgrep-supply-chain/findings#export-findings).

## Comparisons

> [accordion] How does Supply Chain compare with Dependabot?
>
> For languages where Supply Chain doesn't offer reachability rules, Supply Chain performs comparably to GitHub's Dependabot: it checks dependency versions against known vulnerable versions. For GA languages, Supply Chain also runs reachability analysis to show whether your code uses the vulnerable code.
>
> For more information, see [Types of Supply Chain findings](https://docs.semgrep.dev/semgrep-supply-chain/overview.md#types-of-supply-chain-findings).

> [accordion] How does Semgrep compare with other tools?
>
> For comparisons with other tools, see [Compare Semgrep to Snyk](https://docs.semgrep.dev/faq/comparisons/snyk.md) and [Compare Semgrep to Endor Labs](https://docs.semgrep.dev/faq/comparisons/endor-labs.md).
