consider adding check style hooks to github actions to scan for metasploits and common passwords included into your source code. last thing you want is soe derp adding some sql into the end of all your users passwords.. do'h
Hey,
Yes, you’re getting here into the realm of static code analysis.
I did mention ways of simple code scan to identify leaked strings, but I consider STA to be a field of its own that requires commercial solutions.
I wasn’t aware of the style check on GitHub and would look it up.
Thanks!
consider adding check style hooks to github actions to scan for metasploits and common passwords included into your source code. last thing you want is soe derp adding some sql into the end of all your users passwords.. do'h
Hey,
Yes, you’re getting here into the realm of static code analysis.
I did mention ways of simple code scan to identify leaked strings, but I consider STA to be a field of its own that requires commercial solutions.
I wasn’t aware of the style check on GitHub and would look it up.
Thanks!
the new github actions are fantastic for that.