Andrew

Move rule violation text from hardcoding over to GitHub wiki pages, using short identifiers to indicate the basic error type. This allows for more rapid and clear text descriptions, and...

Traditionally, shebang lines were limited to 16, 32, 127, 255, 1024, etc. bytes. For portability with very old systems, the user could specify a flag like `maxShebangLength 16` to scan...

Many of the basic funk rules can apply to non-shell scripts, like Python and Ruby scripts. We can turn some of these on generally for alternative non-POSIXy shell script languages,...

Strip leading `/bin/env` (SCO, Unicos, RHEL) just like `/usr/bin/env`. https://web.archive.org/web/20170215070707/http://www.in-ulm.de/~mascheck/various/shebang/#details (The archives advise against using env at all for portability, but I dare you to pratice shebangs across GNU Linux...

For the programmer's sanity, offer a boolean flag controlling whether we warn on the presence of non-ASCII bytes in source code files. Rule should default to enabled. For non-English programmers,...

To make installing it that much easier

For use with [jsfmt](https://github.com/rdio/jsfmt) and other JavaScript linters that have gaps identifying JavaScript files in large, multi-programming-language, recursive directory projects. * [ ] Add a field `JavaScripty` to results, similar...

Prevent subtle portability errors, such as "ksh" scripts that invoke `set -euo pipefail` on Debian, which break when run on OpenBSD, where the default ksh expansion is not a ksh93...

Golly, get pure Go AST's for bash, POSIX sh, ksh, zsh in here, so we can reliably implement ShellCheck-like warnings such as #68 and #70.

When the `-kin` flag is present, recommend replacing the findings with dedicated machine code, such as fully statically linked binaries. To minimize dependencies.