bash-review

To check bash scripts for security vulnerabilities, you can use automated analysis to detect critical flaws like command injection and unsafe eval, alongside warnings for improper quoting and error handling. This process ensures scripts are robust before deployment.

Finding bashisms and portability issues in shell scripts involves analyzing the code to flag syntax that may cause failures on different systems. This portability analysis identifies non-compliant constructs that hinder cross-platform execution.

To lint bash scripts for proper error handling, the analysis verifies the presence of essential directives like `set -e`, `set -u`, and `set -o pipefail`. This catches missing safeguards and highlights warnings for unhandled errors.

Yes, you can review all .sh files in your repository at once. The analysis operates on specified files, recent changes, or all .sh files in the directory, applying shellcheck and manual analysis to identify best practice violations.

Shellcheck detects many common pitfalls in bash scripting, but combining it with manual analysis provides deeper security auditing. This dual approach identifies critical vulnerabilities, portability concerns, and best practice suggestions that automated linting might miss.