Cppcheck
Clang Static Analyzer
Coverity Scan
lgtm.com
SonarQube
VisualCodeGrepper
Flawfinder
Parasoft C/C++test
RealityGraph.dev
CodeRabbit
SonarSource
Aikido Security
Reviewable
Review Assistant
Reality Graph is the context, validation, and evidence layer for AI-assisted software development. The problem: tools like Claude Code, Cursor, and Copilot generate code faster than teams can understand and review it โ creating verification debt. Reality Graph doesn't replace these tools; it structures the workflow around them: Task Contracts make goals and done-criteria explicit and checkable before the run, Context Packs deliver focused instead of noisy context, the Validation Map ties every change to tests and risks, and the Evidence Trail records what changed and what was checked. Everything runs local-first โ source code never leaves your machine. Advisory by default, no autonomous commits. Built in Berlin, currently in private closed beta.
Cppcheck RealityGraph.devNo features have been listed yet.
Cppcheck 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.
No RealityGraph.dev videos yet. You could help us improve this page by suggesting one.
Based on our record, Cppcheck seems to be more popular. 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: about 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: about 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
Clang Static Analyzer - The Clang Static Analyzer is a source code analysis tool that finds bugs in C, C++, and Objective-C...
CodeRabbit - Unleash AI on Your Code Reviews with CodeRabbit
Coverity Scan - Find and fix defects in your Java, C/C++ or C# open source project for free
SonarSource - Sonar empowers developers and organizations to achieve Clean Code, systematically and predictably.
lgtm.com - lgtm.com is a platform for code analytics.
Aikido Security - Secure your code, cloud, and runtime in one central system. Find and fix vulnerabilities fast and automatically.