See Snyk Advisor.

Asset (Snyk AppRisk)

A Snyk AppRisk asset is an identifiable entity that is part of an application, and relevant for security and developers.


Base image

The parent image used to construct a container image, usually defined in the FROM directive in a Dockerfile. Base images themselves can be constructed from other base images.


See Snyk Broker.

Build System

A system that takes the source code and builds the deployable application (such as a container).



Continuous integration (CI), continuous delivery (CD), and continuous deployment (CD) together comprise a Software Development Lifecycle (SDLC) model, guiding developers to automate the development and delivery of small, frequent changes. This ensures all team members have access to the latest codebase and can ensure the compatibility of committed code during development. See Snyk CI/CD for details of Snyk CI/CD integrations.

Class (Snyk AppRisk)

A way to assign business context to assets and categorize an asset based on the business criticality. Assets can be assigned Classes A, B, C, or D, where Class A (assets that are business critical, deal with sensitive data, are subject to compliance, and so on) is the most important, and Class D (test apps, sandbox environments, and so on) the least important. Assets are assigned Class C by default. A class can be used in policies as well as defined in a policy.


Command Line Interface. See Snyk CLI.

Cloud Native Application Security

Implementing security throughout the CI/CD pipeline, automating security embedding in microservices, and maximizing repetition to reduce the introduction of vulnerabilities. Snyk provides a comprehensive CNAS platform. See the article Cloud-native security guide for building secure applications.


Containers allow you to package applications and their dependencies together to be deployed as a single runnable unit. A container is an abstraction provided by the operating system kernel that allows a process to be isolated from other processes running on the system. See also Snyk Container.

Container engine

For users, an application that takes a container image and turns it into a running container. Container engines typically interface with container registries and run containers. Examples of container engines include Docker, CRI-O, and LXC.

Container image

One or more files that, when instantiated by a container engine or runtime, provide a running container. Images are the packaging and distribution format for containers.

Container registry

A server that provides a mechanism to store and retrieve container images.

Controls (Snyk AppRisk)

The security controls associated with the asset. Navigate to the Snyk AppRisk Controls section to see all available statuses for security controls.

Coverage (Snyk AppRisk)

An assessment of whether applicable assets are scanned and tested by security tools (like Snyk Open Source, for instance), as it relates to an application security program. A type of policy that allows you to specify what controls should be applied and, optionally, how often it needs to be run.


Common Vulnerabilities and Exposures. A widely-used identifier for a well-known vulnerability.


Common Vulnerability Scoring System. An industry standard to assess the severity of vulnerabilities, using a score of 0 (lowest) to 10 (highest). Snyk uses CVSS.


Common Weakness Enumeration. An online glossary that categorizes software and hardware weaknesses into different types, for example, CWE-20: Input Validation.



Dynamic Application Security Testing. An application that you can point at a site or service; it then typically profiles the site or service, then examines the output and behavior to uncover security vulnerabilities. See also SAST.


When your application uses another package, this other package becomes a dependency in your own software.

  • A direct dependency is a package you include in your own Project.

  • An indirect dependency (also known as a deep, chained, or transitive dependency), is a package that is used by one of your direct dependencies.

Dependency tree

Also known as Dependency path. A hierarchical graph showing the dependencies of a software application. This includes both direct and indirect dependencies and thus may be many levels deep.


A set of cultural philosophies, practices, and tools that combines software development and IT operations to shorten the systems development lifecycle.


The integration of security into emerging agile IT and DevOps development as seamlessly and as transparently as possible.


A text file format used to build container images using Docker. The Dockerfile contains all the commands needed to construct the final image, including specifying the parent base image.



Can refer to a cloud environment, a Project attribute, or an interface for working with Snyk, such as the Snyk CLI, Web UI, or an IDE.


A demonstration of how a vulnerability can be taken advantage of. When an exploit is widely published, it is commonly referred to as an exploit "in the wild". See View exploits.

Exploit Maturity

A measure of how practical an exploit for a vulnerability is, based on whether the exploit is in the wild, and how "helpful" the exploit is to attackers.


Fixable / Partially fixable

A measure of whether a vulnerability can be fixed by Sny by applying a patch, upgrade, or pin. See Vulnerability fix types.

Fix PR

A pull request with an automatic fix for discovered vulnerabilities that Snyk can offer the user. See Automated fix PRs.



A distributed version control system for tracking changes in source code during software development.



Infrastructure as Code. See Snyk Infrastructure as Code.


Interactive Application Security Testing. This approach tests for vulnerabilities while running the application. See DAST and SAST.


Integrated Development Environment. An application that has facilities for software development, typically with a source code editor, build automation tools, and a debugger.


The stored instance of a container that holds a set of software needed to run an application.

Image layer

Container images typically consist of several different file system layers, which are combined together at runtime into a single file system.


Third-party products, applications, and platforms that Snyk works with, for example, SCM systems such as GitHub. See Integrate with Snyk.


A license problem, vulnerability, or misconfiguration identified and listed by Snyk. See Find and manage priority issues.



A specific type of package.

License policy

A set of criteria for evaluating open-source license issues. License policies enable you to set the severity level and define legal instructions for each license. See License policies.



A file containing metadata about other files in a package.


The snyk monitor command tests a Project and uploads the results to Snyk. See the CLI help for Monitor.



Open Container Initiative. An independent body set up to facilitate collaboration on standards for containers, to ensure they are interoperable between vendor solutions.


An Organization in Snyk is a way to collect and organize your Projects. Members of Organizations have access to these Projects. See Manage Groups and Organizations.

Origin or source

The identifier for the ecosystem that a Target exists in. Snyk can scan Projects from multiple integrations, including CLI, API, GitHub, Kubernetes, and others. See Snyk Projects.



A group of files and additional metadata about those files, used by package managers.

Package manager

A set of tools that automate and manage packages of bundled files, and are usually specific to a language. For example, npm.

Package registry

A software package hosting service that allows customers to host packages and code in one place.


A fix type: define and "pin" a specific version of an indirect dependency, to avoid a direct dependency pulling in a vulnerable version.


See license policy, security policy, and .snyk policy.

Policy (Snyk AppRisk)

A way to automate actions in certain conditions, like classifying and tagging assets with business context. You can also use a policy to configure actions like sending a message or setting the coverage gap control using a Policy builder UI.


Pull Request. Allows a user to exchange changes made to source code and collaborate with others on the same branch.

PR Checks

Use Snyk PR Checks to prevent new security issues from entering your codebase by automatically scanning code changes in real-time as soon as you submit a pull request (PR) in your source code manager (SCM). See Run PR Checks.

Priority Score

Snyk scores issues, including vulnerabilities and licenses for Open Source, to help prioritize the treatment of each one. Scores are based on multiple factors including the CVSS score and range from 0 (low) to 1000 (high). See Priority Score.


An external item scanned by Snyk with configuration to define how to run that scan. Projects appear on the Projects menu on the Snyk dashboard. See also Target. For details, see Snyk Projects.



Whether an application contains code that will hit a vulnerable code path during execution. See Reachable vulnerabilities.


See Container registry or Package registry.


A storage area that contains all elements necessary for the distribution of an application.


A cloud infrastructure entity such as an AWS S3 bucket, Identity and Access Management (IAM) role, or Virtual Private Cloud (VPC) flow log.

Risk score

A value assigned to an issue, ranging from 0 to 1,000, representing the risk imposed on your environment.


A security policy that checks cloud infrastructure and infrastructure as code (IaC) for misconfigurations that can lead to security problems, or a security rule used by Snyk Code when scanning your source code for vulnerabilities. For more information, see Snyk Code security rules and IaC custom rules.



Static Analysis Results Interchange Format. A standard, JSON-based format for the output of static analysis tools.


Static Application Security Testing. A method to secure software by reviewing the source code of your proprietary software and identifying sources of vulnerabilities. See also DAST.


Software Bill Of Materials. A list of components in a piece of software.


Software Composition Analysis. A technology that is used to identify open-source and third-party components in use in an application, including their known security vulnerabilities, and typically adversarial license restrictions. See also Static Code Analysis.


Source Code Management. Also known as a code repository (repo) or version control system. The method used by developers to store their source code and track changes to code. SCM helps resolve conflicts when merging updates from multiple contributors. GitHub is an example of a common SCM system. See Git repositories (SCMs).


Software Development Lifecycle. A process followed by a development team, describing how to develop and maintain software.

Security policy

A set of criteria for evaluating open-source vulnerabilities. Security policies enable you to set custom rules to automatically prioritize or de-prioritize specific vulnerabilities. See Security policies.


A severity level is applied to a vulnerability or a license issue, to indicate the risk for that item in an application. See Severity levels.


An individual report within the test history of a Project. Includes a tree of dependencies and a list of vulnerabilities that was accurate at the time the test was conducted.

.snyk policy

A policy file that Snyk uses to define certain analysis behaviors and to specify patches for the CLI and CI/CD plugins. See The .snyk file.


A platform providing Cloud Native Application Security (CNAS) solutions, allowing developers to own and build security for the whole application, from code and open source to containers and cloud infrastructure. Snyk is also the company providing the Snyk platform. See Getting started.

Snyk Advisor

A free web application that allows you to compare software packages across open-source ecosystems. It provides insights into the overall health of a particular package by combining community and security data into a single unified view. See Snyk Advisor.

Snyk API

A Snyk tool that enables developers to integrate programmatically with Snyk. See Snyk API.

Snyk Apps

Snyk Apps are the modern and preferred way to build integrations with Snyk, exposing fine-grained scopes for accessing resources over the Snyk APIs, powered by OAuth 2.0 for a developer-friendly experience. See Snyk Apps.

Snyk Broker

A client/server system that serves as an agent or proxy, allowing Snyk to scan private customer environments: Jira, code repositories, or container registries. Snyk Broker relays messages and allows users to filter which messages are allowed through, for example, allowing users to expose only some GitHub APIs to Snyk. See Snyk Broker.

Snyk CLI

A Snyk platform tool that enables developers to find and fix known vulnerabilities in dependencies, using a command line interface. See Snyk CLI.

Snyk Code

A Snyk product. A SAST product enabling developers to find and fix vulnerabilities in your proprietary application code. See Snyk Code.

Snyk Container

A Snyk product. Enables developers to find and fix vulnerabilities in container images and Kubernetes applications. See Snyk Container.

Snyk Infrastructure as Code

A Snyk product. Enables developers to find and fix vulnerabilities in Kubernetes, Helm, and Terraform configuration files. See Snyk Infrastructure as Code.

Snyk Open Source

A Snyk product. Enables developers to find and fix open-source vulnerabilities. See Snyk Open Source.

Snyk plugin

A library used by the Snyk CLI to scan a certain language or build system.

Snyk Security Intelligence

A component powering the Snk cloud-native application security platform. Incorporates the Snyk Intel Vulnerability DB: the Snyk database of vulnerabilities, providing detailed information and fix advice for known vulnerabilities. See Vulnerability DB.

Snyk Web UI

The browser-based environment that provides users access to Snyk functions. See Explore the Snyk Web UI.

Snyk shows a Trending banner on issues that are being actively discussed on Twitter. See Vulnerabilities with Social Trends.


See Origin.


Software Package Data Exchange. A file format used to document information on the software licenses under which a piece of computer software is distributed. See SPDX.

Static Code Analysis

A method of debugging by examining source code before a program is run. See also SCA, Software Composition Analysis.



Representation of an external resource Snyk has scanned. All Snyk Projects are associated with a parent Target. One Target may relate to many Projects. The structure of the Target depends on the origin.

Tags (Snyk AppRisk)

A way to categorize assets. Helps you recognize or handle assets differently according to mutual properties. Assets can be filtered by their tags in the inventory or when creating policy rules. A tag can be automatically assigned to an asset, or the asset can be tagged by a policy you created. GitHub and GitLab topics are treated as asset tags and you can use them for creating policies.


Upgradable / Patchable

A fix type: a problem can be fixed by upgrading a version of a package or by applying a patch.



A security vulnerability that was identified by Snyk. See Manage vulnerabilities.



A way for an app to provide other applications with real-time information. Snyk uses webhooks to check changes in code. See Snyk Webhooks.

Last updated

More information

Snyk privacy policy

© 2023 Snyk Limited | All product and company names and logos are trademarks of their respective owners.