Define project import strategy
Snyk identifies all testable assets as projects. A project can be a json file, a docker file, a terraform file, or other files that Snyk will scan for issues.
There are two basic ways to import projects to Snyk to begin monitoring them for issues.
Whichever method you use, the projects are imported to a specific organization. The org provides reporting at an aggregate level.
We recommend importing a small number of projects at first as you begin gaining visibility into your issues.
Once you work out your process, you can determine a plan for importing additional projects. When defining your plan, consider the speed at which you want to adopt Snyk, as well as the repository structure and the number of projects that you want to import.
For more advanced import strategy, refer to Tech Services Snyk API import.
Last modified 2mo ago
Copy link