FindBugs
Codacy
SonarQube
Pmd
CodeClimate
JSHint
Semmle
Source Insight
Splint
Coverity Scan
Cppcheck
Shellcheck
Checkmarx
Flawfinder
SonarQube
PVS-Studio
Based on our record, Splint should be more popular than FindBugs. It has been mentiond 10 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
FindBugs: Detects potential issues in Java code that could lead to bugs. - Source: dev.to / almost 2 years ago
The tools generally depend on the programming language. You might be looking for something like a "linter" or static analyzer (i.e. FindBugs for Java). Source: almost 5 years ago
These tools perform analysis on the application's source code without executing/running the code on a platform. In other words, a bot goes line by line of source code to find any bug defined by preconfigured policies/rules. It could be compared to manual code review, but the review is done by a bot. Mostly, code quality, coding standard aspects are targeted to be scanned. The biggest name in static code analysis... - Source: dev.to / about 5 years ago
FindBugs looks for bugs in Java Code, and this means over 400 different bugs. - Source: dev.to / over 5 years ago
> My gut feeling is You're probably right, I was saying it just can be transferred, with a large "just". > the fact that neither GCC nor Clang appear to have discussed reusing concepts from their optimizer passes to recreate the borrow checker or borrow checker-like functionality There is however a commitment from GCC, that every UB the compiler exploits must be reported by -fanalyzer, otherwise it's a compiler... - Source: Hacker News / 12 months ago
Whenever I see people talk about the portability or compatibility advantages of C, I'm reminded of how "even C isn't compatible with C", because you typically aren't talking about up-to-date GCC or LLVM on these niche platforms... you're talking about some weird or archaic vendor-provided compiler... Possibly with syntax extensions that static analyzers like splint will choke on. (Splint can't even understand near... Source: over 3 years ago
Huh. I think I actually needed to use the equivalent position for certain splint annotations in my C retro-hobby project. Source: over 3 years ago
I often like to say that Rust's bindings are a way to trick people into writing the compile-time safety annotations that they didn't want to write for things like splint. (Seriously. Look into how much splint is capable of checking with the correct annotations.). Source: over 3 years ago
Linters like Splint [0] can do that for C. I’m not saying that Rust’s built-in approach isn’t better, but please be careful about what exactly you claim. [0] http://splint.org/. - Source: Hacker News / almost 4 years ago
Codacy - Automatically reviews code style, security, duplication, complexity, and coverage on every change while tracking code quality throughout your sprints.
Coverity Scan - Find and fix defects in your Java, C/C++ or C# open source project for free
SonarQube - SonarQube, a core component of the Sonar solution, is an open source, self-managed tool that systematically helps developers and organizations deliver Clean Code.
Cppcheck - Cppcheck is an analysis tool for C/C++ code. It detects the types of bugs that the compilers normally fail to detect. The goal is no false positives. CppCheckDownload cppcheck for free.
Pmd - PMD scans Java source code and looks for potential problems like:
Shellcheck - ShellCheck finds bugs in your shell scripts