
Cppcheck
Clang Static Analyzer
Coverity Scan
lgtm.com
SonarQube
VisualCodeGrepper
Flawfinder
Parasoft C/C++test
SpotBugs
Dependency-Check
Appknox
Coverity Scan
Checkmarx
HCL AppScan
Veracode
AttackFlow
Cppcheck
SpotBugsCppcheck is recommended for C/C++ developers and development teams, particularly those responsible for maintaining large codebases or projects where code quality and reliability are paramount. It is also beneficial for educational purposes, where students and new developers can learn about potential pitfalls in C/C++ programming.
Based on our record, Cppcheck should be more popular than SpotBugs. 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.
I dedicated Sunday morning to going over the documentation of the linters we use in the project. The goal was to understand all options and use them in the best way for our project. Seeing their manuals side by side was nice because even very similar things are solved differently. Cppcheck is the most configurable and best documented; JSON Lint lies at the other end. - Source: dev.to / over 2 years ago
Using infer, someone else exploited null-dereference checks to introduce simple affine types in C++. Cppcheck also checks for null-dereferences. Unfortunately, that approach means that borrow-counting references have a larger sizeof than non-borrow counting references, so optimizing the count away potentially changes the semantics of a program which introduces a whole new way of writing subtly wrong code. Source: about 3 years ago
For my own projects, I used cppcheck. You can check out that tool to get a feel. Depending on what industry your in, you might need to follow a standard like Misra. Source: over 3 years ago
Https://cppcheck.sourceforge.io/ (there are many other static analysis tools, I just haven't used them or didn't care for them). Source: over 3 years ago
Sounds like something that could simply be communicated with the team that writes the tests. Unless you have dozens of such classes. In that case, you could just use e.g. Cppcheck and add a rule (regular expression) that searches for usages of the forbidden classes. Source: over 3 years ago
SpotBugs is an open source static anlysis tool. "SpotBugs uses static analysis to inspect Java bytecode for occurrences of bug patterns." This means that SpotBugs runs against the compiled source source code, rather than raw Java files. Because it analyses bytecode, it can catch some types of bugs that source code analysis would not catch. - Source: dev.to / about 2 years ago
SpotBugs is a great tool for static code analysis. Recently I got two similar warnings in one of the codebases I work on And I had to fix it. - Source: dev.to / about 2 years ago
While at it you could also point them to static code analyzers such as error_prone, spotbugs and pmd (use all 3 at once - they complement each other in detecting different issues). Source: over 4 years ago
If you donโt have checkmarx/Vera code money, have you looked at https://find-sec-bugs.github.io/? It can be used with a few things such as https://spotbugs.github.io/ and sonarQ. Source: almost 5 years ago
Clang Static Analyzer - The Clang Static Analyzer is a source code analysis tool that finds bugs in C, C++, and Objective-C...
Dependency-Check - Dependency-Check is a utility that identifies project dependencies and checks if there are any...
Coverity Scan - Find and fix defects in your Java, C/C++ or C# open source project for free
Appknox - Appknox is aย cloud-based mobile app security solution to detect threats and vulnerabilities in the app.
lgtm.com - lgtm.com is a platform for code analytics.
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.