Go linter that validates all accesses to slices and arrays are bound-checked.
Go linter which warns of any slice or array accesses which are not enclosed in an if-statement that validates capacity or length. These warnings are meant to help notify developers which accesses aren't bound-checked to help prevent out-of-bound runtime errors.
The idea for this comes from rule G602 which I contributed to gosec. That rule only validates slices whose capacities are determined by calls to make() where the capacity/length is a constant literal, or by reslicing slices made with make(). This linter is simpler than that rule, as it flags all slice and array accesses which are made without first checking capacity or length. I made goboundcheck for developers who want to have strict validation on all slices and arrays. If you want a less noisey and less strict bound-checker, check out gosec.
git clone https://github.com/morgenm/goboundcheck
makeThis will output the executable file goboundcheck on Linux or Mac, and goboundcheck.exe on Windows
The syntax of goboundcheck is similar to other Go linters, due to being built off of golang.org/x/tools/go/analysis.
To recursively scan code starting in the current directory:
goboundcheck ./...You can also scan specific files:
goboundcheck code1.go code2.ggoTo see other flags and options:
goboundcheck --help