github.com/ggml-org/llama.cpp

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

When a COPY command has more than two arguments, the last one should end with a slash.

Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

Dynamic code execution via eval()/new Function() — arbitrary-code-execution risk if any operand is attacker-influenced. Avoid; parse explicitly. (Apache-2.0.)

subprocess invoked through the shell (shell=True) or with a command string that is interpolated/concatenated/.split() instead of a fixed argv list — command injection risk. Pass a literal argv list and shell=False. (First-party socbox; Apache-2.0.)

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

'apt-get' install should use '--no-install-recommends' to minimize image size.

You should use 'yum clean all' after using a 'yum install' command to clean package cached data and reduce image size.

Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.

Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.

Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.

Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.

Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.

Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.

Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.

Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.

Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.

Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.

Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.

urllib3 is a user-friendly HTTP client library for Python. Starting in version 1.0 and prior to 2.6.0, the Streaming API improperly handles highly compressed data. urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chu…

urllib3 is an HTTP client library for Python. urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once. urllib3 can perform decoding or decompression b…

urllib3 is an HTTP client library for Python. From 1.23 to before 2.7.0, cross-origin redirects followed from the low-level API via ProxyManager.connection_from_url().urlopen(..., assert_same_host=False) still forward these sensitive headers. This vulnerability is fixed in 2.7.0.

urllib3 is a user-friendly HTTP client library for Python. Starting in version 1.24 and prior to 2.6.0, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage a…