the problem was the methods were not being processed
the same as regular controller methods, causing them
to have a :scope node, creating a new scope when
the ControllerAliasProcessor did not expect it. This
caused the variables from the method to not be propagated
to the view.

for consistency

If a file in app/controllers does not contain a class, treat it like a
library.

Test with 1.9.3 on travis-ci

Include detected user input value in warnings and highlight in reports

to report the actual piece of code detected as user input for some
warnings

not a big change, it was already returning an array containing
the type and the matched value, but this simplifies/clarifies things.

Include all of lib in the gem

Update json output and add comparison feature for json