Merge branch 'fix_negative_array_indexing' of github.com:presidentbeef/brakeman into fix_negative_array_indexing

so checks that use has_immediate_user_input? will
report it as high confidence.

like `params[:x] || nil` which should be considered
immediate user input.

Don't bail out on processing a class if an error is raised when
determining the parent class name.

it just leads to confusing errors in reports like
"wrong number of arguments (0 for 1)"

especially empty arrays

message changed

Although in the future has_immediate_model? should
probably return a Match object

accidentally removed in cc4f4997

This error sometimes comes up when processsing a render
in a template, because the "name" of the template to render
is interpolated into a regex. If the "name" is actually a
method call or other code, then the regex comes out strange.

Improve file access check with better confidence levels

also support for --report-direct option

Thanks to @daveworth

to avoid losing information

which should give some speed improvements

Run tests before pushing...still learning that lesson, I guess.