Based on our record, ESLint seems to be a lot more popular than Cppcheck. While we know about 231 links to ESLint, 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.
Eslint: It analyzes our code to quickly find problems. We will use the default setup provided by Vite. - Source: dev.to / 3 days ago
A big part of my work revolves around JavaScript tooling, and as such it's important to keep an eye on the ecosystem and see where things are going. It's no secret that recently lots of projects are native-ying (??) parts of their codebase, or even rewriting them to native languages altogether. Esbuild is one of the first popular and successful examples of this, which was written in Go. Other examples are Rspack... - Source: dev.to / 6 days ago
ESLint: A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. - Source: dev.to / about 1 month ago
Automating code checks with static code analysis allows us to enforce code styling effectively. By integrating tools into our workflow, we can identify errors at an early stage, while coding instead of blocking us at the end. For instance, flake8 checks Python code for style and errors, eslint performs similar checks for JavaScript, and prettier automatically formats code to maintain consistency. - Source: dev.to / about 1 month ago
If you're a developer, you're surely familiar with Prettier and ESLint. With over 8 years of existence, they have established themselves as references in the JavaScript ecosystem. - Source: dev.to / about 1 month ago
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 / 3 months 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: 12 months 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 1 year 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 1 year 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 1 year ago
Prettier - An opinionated code formatter
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.
Clang Static Analyzer - The Clang Static Analyzer is a source code analysis tool that finds bugs in C, C++, and Objective-C...
CodeClimate - Code Climate provides automated code review for your apps, letting you fix quality and security issues before they hit production. We check every commit, branch and pull request for changes in quality and potential vulnerabilities.
Coverity Scan - Find and fix defects in your Java, C/C++ or C# open source project for free
Codacy - Automatically reviews code style, security, duplication, complexity, and coverage on every change while tracking code quality throughout your sprints.