Release 1.0.0 Β· rife2/bld-spotbugs

Summary Improved Flexibility for multi-value inputs Performance, parsing, and testing Errors handling Logging and documentation Fixed ignoreFailures method name inconsistencies What's Changed ...

GitHub
Release 0.9.0 Β· rife2/bld-spotbugs

Summary Initial release

GitHub
There is something I'd like to correct and it is that I use System.exit(1); in some places to exit from #FidoCadJ. #SpotBugs is not very happy about it, but I haven't found an alternative to fix this issue. #Java
I am using #SpotBugs, too. Some of the issues found are insightful, others leave me a little perplexed.

I've wrapped up SpotBugs/FindSecBugs in a bow 🎁 in a GitHub Action, so you can use it in GitHub Code Scanning - free for open source projects, and also available for paid users of GitHub Advanced Security.

SpotBugs and FindSecBugs work with JVM languages - Scala, Java, and Clojure, mainly.

https://github.com/marketplace/actions/spotbugs-with-findsecbugs

Point it at the results of the build, and go.

#GitHub #SAST #Scala #JVM #Clojure #Java #CodeSecurity #SpotBugs #FindSecBugs #DevSecOps #SDLC

SpotBugs with FindSecBugs - GitHub Marketplace

Run SpotBugs with FindSecBugs on your build results, and upload the results to GitHub Code Scanning

GitHub

Are there any good equivalents to #Errorprone or #SpotBugs for #SQL queries? Bonus points if I can write my own linter rules additionally to the core rules. #Database #Linter

https://sqlfluff.com/ doesn't quite cut it.

SQLFluff

πŸ“œ The SQL Linter for humans