High
Showing all detectors for the Shell language with high severity.
The end token EOF was not found in the here document.
Avoid premature termination of single-quoted strings by properly escaping apostrophes or switching to double quotes.
Shell script incorrectly uses sudo with I/O redirection, which doesn't work as intended.
Direct use of variables in printf format string instead of using format specifiers.
Unescaped '&' in command terminates it prematurely.
Remove unexpected characters after closing test bracket.
Document isn't properly terminated because the terminator is not on a separate line by itself.
Bourne shells are very sensitive to whitespace, and missing spaces can change script behavior.
Unquoted 'eval' can lead to arbitrary code execution if variable contains malicious input.
Use globs instead of 'ls' for file iteration.
The construct <<( is invalid; to redirect from process substitution, use < <(cmd) instead.
Use arrays or functions for complex command arguments instead of strings.
Parser error due to invalid script structure.
Unintended execution of command output due to unnecessary backtick command substitution.
Use of multiple parameters in shebang line, causing script execution failure on most operating systems.
Identifying and addressing syntax errors in shell scripts.
Using single quotes instead of double quotes in trap commands to prevent premature expansion of variables and commands.