github.com/jesseduffield/lazygit

Command injection: exec.Command/exec.CommandContext is invoked with a shell (sh/bash -c) plus an interpolated string, or with argv[0] AND its args spread from the same parsed slice ($A[0], $A[1:]...) — i.e. a command string split into an argv and executed, which lets input choose…

Command injection: exec.Command/exec.CommandContext is invoked with a shell (sh/bash -c) plus an interpolated string, or with argv[0] AND its args spread from the same parsed slice ($A[0], $A[1:]...) — i.e. a command string split into an argv and executed, which lets input choose…

Command injection: exec.Command/exec.CommandContext is invoked with a shell (sh/bash -c) plus an interpolated string, or with argv[0] AND its args spread from the same parsed slice (args[0], args[1:]...) — i.e. a command string split into an argv and executed, which lets input ch…

Command injection: exec.Command/exec.CommandContext is invoked with a shell (sh/bash -c) plus an interpolated string, or with argv[0] AND its args spread from the same parsed slice (args[0], args[1:]...) — i.e. a command string split into an argv and executed, which lets input ch…

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.

For clarity and reliability, you should always use absolute paths for your WORKDIR.

Base64 High Entropy String on 8278b30ef12fdf2ca2aaa363ea2f2504f0543357

Ensure that a user for the container has been created on /Dockerfile.

Ensure that HEALTHCHECK instructions have been added to container images on /Dockerfile.

Ensure top-level permissions are not set to write-all on on(Continuous Integration)

Ensure top-level permissions are not set to write-all on on(Release)

Ensure top-level permissions are not set to write-all on on(Generate Sponsors README)

Ensure top-level permissions are not set to write-all on on(Check Required Labels)

The build output cannot be affected by user parameters other than the build entry point and the top-level source location. GitHub Actions workflow_dispatch inputs MUST be empty. on on(Release)

MD5/SHA1/DES are broken for security use. Use sha256+, and AES over DES. (Apache-2.0.)

Possible hardcoded secret assigned to a credential-like variable. Move it to a secret store / env var. (First-party socbox rule; Apache-2.0.)

Possible hardcoded secret assigned to a credential-like variable. Move it to a secret store / env var. (First-party socbox rule; Apache-2.0.)

Possible hardcoded secret assigned to a credential-like variable. Move it to a secret store / env var. (First-party socbox rule; Apache-2.0.)