safe_value? is essentially a filter to mark values
as safe that otherwise would be reported by unsafe_sql?

but still a little ways to go

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