Cppcheck
Clang Static Analyzer
Coverity Scan
lgtm.com
SonarQube
VisualCodeGrepper
Flawfinder
Parasoft C/C++test
Prettier
ESLint
Tailwind CSS
VS Code
Next.js
Angular.io
GitHub
stylelint
Cppcheck PrettierCppcheck 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, Prettier seems to be a lot more popular than Cppcheck. While we know about 304 links to Prettier, we've tracked only 10 mentions of Cppcheck. 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
Line length, spacing, and indentation matter. My preference for code is roughly 80 to 110 characters. Longer lines become tiring to scan, while very short lines can create excessive wrapping. For formatting, tools like Prettier reduce debate and keep code visually consistent across contributors. - Source: dev.to / 25 days ago
137Foundry provides legacy modernization services that include dependency mapping as a foundational assessment phase. Prettier and ESLint are useful companion tools for enforcing code style consistency as the refactoring proceeds. Node.js and Python.org official documentation are authoritative references for understanding the import and module systems of those runtimes. - Source: dev.to / 3 months ago
Prettier and ESLint are useful tools for establishing consistent code style as a baseline before starting structural refactoring - style differences in a diff make behavioral changes harder to spot. OWASP provides useful checklists for security-critical code review that apply directly to the critical path review step. - Source: dev.to / 3 months ago
The matcher field takes a regex pattern. Edit|Write means this hook only fires when the Edit or Write tool is used. Claude running Bash, Read, or any other tool won't trigger it. The command itself uses jq to extract the file path from the tool input JSON, then pipes it to Prettier. Every file Claude touches gets formatted automatically. - Source: dev.to / 4 months ago
The better approach: let the agent write code however it wants, then run Prettier, Black, Ruff, or ESLint. Zero ambiguity. The agent doesn't need to think about formatting at all, which means fewer tokens spent and fewer decisions that could go wrong. - Source: dev.to / 5 months ago
Clang Static Analyzer - The Clang Static Analyzer is a source code analysis tool that finds bugs in C, C++, and Objective-C...
ESLint - The fully pluggable JavaScript code quality tool
Coverity Scan - Find and fix defects in your Java, C/C++ or C# open source project for free
Tailwind CSS - A utility-first CSS framework for rapidly building custom user interfaces.
lgtm.com - lgtm.com is a platform for code analytics.
VS Code - Build and debug modern web and cloud applications, by Microsoft
