> ## 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.

# Supply Chain results may be incomplete

> Find out why a scan shows the Supply Chain results may be incomplete alert, and fix each dependency error it lists.

A scan's details on the **Projects** page show the **Supply Chain results may be incomplete** alert. The alert lists one or more dependency errors.

## Cause

Semgrep Supply Chain couldn't resolve or read some of the project's dependencies during the scan. Semgrep can't generate findings for those dependencies. The alert lists each type of error once, even if it happened in several places.

## Fix

Find each error in the alert, and follow the steps for it:

| Error | What to do |
| :- | :- |
| **Unsupported manifest or lockfile** | Semgrep doesn't support one or more of the project's manifest files or lockfiles. Check the package managers that Semgrep supports in [Supply Chain requirements and feature support](https://docs.semgrep.dev/semgrep-supply-chain/requirements-and-feature-support.md). |
| **Missing requirement** | A tool that dependency resolution needs is missing. For a CI scan, find the missing requirement in the scan logs, add it to your CI environment, and rerun the scan. For a Managed Scan, contact [Semgrep Support](https://docs.semgrep.dev/support.md). |
| **Dependency resolution failed** | Check the scan logs for details. |
| **Dependency parsing failed** | Semgrep resolved the dependencies but couldn't read the output. Contact [Semgrep Support](https://docs.semgrep.dev/support.md). |
| **Lockfile parsing failed** | Semgrep couldn't parse the dependency output. Contact [Semgrep Support](https://docs.semgrep.dev/support.md). |
| **Manifest or lockfile parsing failed** | Check that the project's lockfiles and manifest files are valid, then rerun the scan. |
| **Registry access failed** or **Private registry access failed** | Semgrep couldn't download dependencies from a registry. If the alert names private registries, check their credentials in **Settings > Integrations**. For more information, see [Connect a private registry to Semgrep](https://docs.semgrep.dev/kb/semgrep-supply-chain/connect-a-private-registry.md). Otherwise, check the scan logs for details. |
| **Public or other registry access failed** | Semgrep couldn't download dependencies from other registries. Check the scan logs for details. |
| **Incomplete dependency resolution** | Semgrep couldn't resolve all dependencies. Check the scan logs for details. |
| **Unknown dependency error** | Add a lockfile to the project, or turn on [Dynamic Dependency Resolution](https://docs.semgrep.dev/semgrep-supply-chain/set-up-and-configure.md#dynamic-dependency-resolution-beta). |

If an error persists after you follow these steps, contact [Semgrep Support](https://docs.semgrep.dev/support.md).
