RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.gitlab.com/user/application_security/comparison_dependency_and_container_scanning/ below:

Dependency Scanning compared to Container Scanning

Help us learn about your current experience with the documentation.

Dependency Scanning compared to Container Scanning

GitLab offers both Dependency Scanning and Container Scanning to ensure coverage for all of these dependency types. To cover as much of your risk area as possible, we encourage you to use all of our security scanning tools:

Dependency Scanning analyzes your project and tells you which software dependencies, including upstream dependencies, have been included in your project, and what known risks the dependencies contain.
Container Scanning analyzes your containers and tells you about known risks in the operating system’s (OS) packages.

The following table summarizes which types of dependencies each scanning tool can detect:

Feature Dependency Scanning Container Scanning Identify the manifest, lock file, or static file that introduced the dependency check-circle dotted-circle Development dependencies check-circle dotted-circle Dependencies in a lock file committed to your repository check-circle check-circle ¹ Binaries built by Go dotted-circle check-circle ² Dynamically-linked language-specific dependencies installed by the Operating System dotted-circle check-circle Operating system dependencies dotted-circle check-circle Language-specific dependencies installed on the operating system (not built by your project) dotted-circle check-circle

Lock file must be present in the image to be detected.
Report language-specific findings must be enabled, and binaries must be present in the image to be detected.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4