Low
Showing all detectors for the Shell language with low severity.
ShellCheck directives incorrectly placed within case statement branches.
Unrecognized shebang, Tool supports only 'sh/bash/dash/ksh'. Add a 'shell' directive.
Use ${#variable} for efficient string length calculation.
In POSIX shell, single quotes strictly terminate quoted segments without interpreting any characters within.
Use double quotes instead of single quotes for variable expansion in shell scripts.
Single-quoted strings treat backslash followed by a linefeed as a literal backslash and linefeed, with no special meaning.
Use either '&' or ';' to terminate commands, but not both.
Incorrect tick character usage.
Shell script uses non-portable character ranges instead of POSIX character classes for case conversion.
Shell script contains a comment without a preceding space, potentially causing syntax errors.
Shell script incorrectly uses square brackets around character ranges in tr command.
Presence of Unicode quotes instead of ASCII quotes.
Shell script performs integer division before multiplication, potentially losing precision in calculations.
ShellCheck unable to analyze sourced file due to access issues or configuration.
Shell script contains trailing spaces after a backslash used for line continuation, causing syntax errors.
Use correct comment syntax.
Shell script uses unbraced syntax for array expansion, potentially leading to incorrect interpretation.
Don't use' A && B || C' as a substitute for if-then-else constructs.
Avoid escaping parentheses inside square bracket expressions.
Shell script incorrectly uses tr command to replace words instead of individual characters.
Proper spacing before opening brackets in shell conditional statements.
Avoid unnecessary use of 'cat' for single file input.
For loop in shell script incorrectly uses $ on the iterator variable name.
In double quotes, $ is special but can be interpreted literally in specific contexts; use a backslash to escape it when intended as literal.
Incorrect escape sequences are ignored, use a literal backslash, single quote, or correct escape method.
The process only removes tabs, not spaces, but your editor might convert tabs to spaces automatically.
Shell prompt uses unescaped escape sequences, leading to display issues.
Shell script uses echo to print escape sequences, which doesn't work as intended.
Use backslash to escape $ within quotes instead of ending quotes.
Avoid unnecessary backslash escapes.
Shell script uses a non-constant source path, which can't be statically analyzed for potential issues.
Use '$HOME' instead of tilde in quotes.
Avoid unnecessary dollar signs in arithmetic expressions.
Piping to 'echo' command incorrectly.
Shell script incorrectly uses unescaped quotes within a string, causing syntax errors.
ShellCheck directives incorrectly placed after commands.
Shell script misuses asterisk in regex, potentially leading to unintended matches.
Remove unnecessary 'echo' when outputting command results.
Identifying scripts written in languages not supported by ShellCheck.
Variable appears unused in the script.
Use parameter expansion instead of 'sed' for simple string replacements.