Snyk Projects

Snyk Project information appears in the Projects listing, which you can display from the menu on the Snyk dashboard. The filters you can add depend on the Group by option you choose from the pulldown on the right. To filter by Origin or source, use an Integrations filter.

Progress and error information on the state of your repository and container registry image imports are shown in the Import Log.

Snyk Projects concepts include the following:

• Target

• Origin

• Project

• Targetfile

• Type

Target

Projects are held in a Target. A Target represents an external resource Snyk has scanned: a code repository, a Kubernetes workload, or another scannable resource external to Snyk.

Snyk creates a Target when you request to import a Project or scan using the CLI. If the import fails or finds nothing, the Target will be empty.

When you select Group by target, Snyk Targets appear in the Projects listing. You can also find Targets using the endpoints Get targets by org ID and List all Projects for an Org with the given Org ID.

Click the dots at the far right of each Target on the list to see the available actions, including deleting a target.

Each Snyk Project is associated with a parent Target. One Target may include many Projects. The structure of the Target depends on the Origin.

The grouping option controls whether the filtering attributes are applied at the Target or at the Project level. Group by none (ungrouped) lets you apply tags and filtering attributes at the Project level to the individual Projects.

Snyk provides both pagination to improve the page loading time for Projects page requests and filtering, which is particularly helpful if you have hundreds of thousands of Projects to scan.

Use Sort by (pull down on the far right) to sort the Projects listing by severity, by how recently the Projects were imported, or in alphabetical order.

Origin or source

The Origin defines the Target ecosystem, such as CLI, GitHub, or Kubernetes. Origins are a property of Targets (see preceding section) and appear in the Projects listing as an icon next to the Target name.

Possible Origin values are:

• acr

• api

• artifactory-cr

• aws-config

• aws-lambda

• azure-functions

• azure-repos

• bitbucket-cloud

• bitbucket-server

• cli

• cloud-foundry

• digitalocean-cr

• docker-hub

• ecr

• gcr

• github

• github-cr

• github-enterprise

• gitlab

• gitlab-cr

• google-artifact-cr

• harbor-cr

• heroku

• ibm-cloud

• kubernetes

• nexus-cr

• pivotal

• quay-cr

• terraform-cloud

Project

A Snyk Project defines the items, such as manifest files, that Snyk scans for a given Target, with configuration information defining how to run that scan.

Projects appear in the Projects listing. You can also find Projects using the endpoint List all Projects for an Org with the given Org ID.

Use Group by none (ungrouped) for better Project visibility and to apply filtering attributes at the Project level.

Targetfile

The Targetfile is the specific item to scan in a Target, such as a pom.xml file in a GitHub repo.

Type

The Type is the scanning method to use for a particular Project, such as Static Application Security Testing (SAST) for scanning using Snyk Code, or Maven for a Maven project using Snyk Open Source. This is part of the configuration for scanning.

Project actions on the Project listing page

Delete, activate, or deactivate

To perform an action at bulk on your Projects, first select the Projects and then choose to Delete, Activate, or Deactivate the Projects.

Click Delete to remove Projects from the Projects listing page and the Target-level aggregates.

Click Deactivate to remove webhooks and prevent tests from occurring. Deactivating a Project will:

• Stop showing the Project results in reporting.

• Keep showing the findings of the last scan in the Projects listing page, including the Target-level aggregates on the Group by Target view.

Test frequency settings

You can set the frequency of testing for each Project.

For each entry, you can select the frequency of testing for that Project (never, daily, or weekly) as applicable to the type of Project, Open Source, Code analysis, Container, or IaC: