You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 21, 2021. It is now read-only.
Using this tool for the very first time, I was curious why the output is so verbose.
Here is what I see:
Found 3 potentially unsafe SQL statements:
<LIST OF FILES WITH PROBLEMS>
Please ensure that all SQL queries you use are compile-time constants.
You should always use parameterized queries or prepared statements
instead of building queries from strings.
Do we gain anything from all the extra output or could we just output a list of problematic files?
I'd be happy to open a PR if y'all think we should trim down the output.
I think the informational lines would be more appropriate in the output of safesql -h what do you think?
The text was updated successfully, but these errors were encountered:
Using this tool for the very first time, I was curious why the output is so verbose.
Here is what I see:
Do we gain anything from all the extra output or could we just output a list of problematic files?
I'd be happy to open a PR if y'all think we should trim down the output.
I think the informational lines would be more appropriate in the output of
safesql -h
what do you think?The text was updated successfully, but these errors were encountered: