Why did my project fail to import?
Failed to process manifest FILE_NAME
The manifest file is missing, has been moved or renamed. If this is intentional, please deactivate or delete this project in settings.
NPM & Yarn
Failed to parse package.json or package-lock.json as valid JSON
Failed to parse package.json or yarn.lock as valid JSON
Failed to process RubyGems lockfile contents
If you are manually adding a project to Snyk by using the `Add custom file location` you need to ensure the folder path and file name are in the correct case that matches your repo. For example if you have on BBS myproject/MyRepo and inside this a subfolder like GoofFolder which contains goof code with manifest files etc, adding manually gooffolder/package.json will fail, adding manually GoofFolder/package.json will work.
Satisfying version not found for cousin dependencies
When importing a .Net project, Snyk is creating the dependency tree according to the.*proj file. According to the NuGet logic, it is not allowed to use the same package with different versions in the same project. For example, let's assume that Package A and Package B are direct dependencies of the same project and both use Package C, meaning Package C is a transitive dependency. When resolving the version of Package C, it must be resolved into 1 version and to satisfy the requirements of Package A and Package B. Failing to do that will result in the error "Satisfying version not found for cousin dependencies error".
To troubleshoot the issue, please try to build the project. If it was built successfully, please reach out to email@example.com and we will look into it. If it wasn't, please make sure that all of the dependencies you are using in your project are not conflicting.
Satisfying version not found
When importing a .Net project, Snyk is creating the dependency tree according to the packages.config or .*proj files. In order to be able to resolve the version of all dependencies, they should be compatible with the target framework of the project. In case one or more of the dependencies are not compatible, we will return the "Satisfying version not found" error.
To troubleshoot the issue, please try to build the project. If it was built successfully, please reach out to firstname.lastname@example.org and we will look into it. If it wasn't, please make sure that all of the dependencies you are using in your project are compatible with the target framework of the project.
Target framework not present in <project_FileName>
In order to be able to build a dependency tree, Snyk needs to be able to determine what is the target framework of the project. Currently, we require the target framework to be part of the .*proj file. Support for using props file will be coming soon.
Infrastructure as Code (Kubernetes / Helm)
Failed to download Helm chart file
This error is probably caused by a failure to download the
Chart.yaml file from your git repository. This might mean Snyk does not have the correct permissions to access the file or that it has been deleted.
If you are using a Snyk broker, make sure you follow the relevant configuration instructions.
Failed to find a proper values file
Snyk needs the
values.yaml file to render the template. This file needs to be in the same folder as the
Failed to receive the content of the templates folder Failed to get the file: <FileName> in order to template the chart
Please make sure that there is a
templates folder in the same directory as the
Chart.yaml file. This folder should contain templates and helper files (
*.tpl) that we access as part of the import flow. For more details about the expected format of Helm Charts, please see the Scan and fix security issues in your Helm Charts.
If you are using a Snyk broker, make sure you follow the relevant configuration instructions
Failed to run Helm template using the chart
You can check whether your chart is valid by testing locally by running
helm template, which should pass without errors.
Note that we don’t yet support Helm charts which use an internal Helm repository to fetch dependencies or that require additional values files to render the Chart.
Infrastructure as Code (Terraform)
Unsupported Terraform file format
You will get this error if the imported repository contains HCL version 1 files. Snyk only supports HCL version 2, used from Terraform version 0.12+. Use the
terraform validate command to check your configuration file version.