No more typing reviews! Try our Samantha, our new voice AI agent.

CodeSonar vs Coverity Static comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

CodeSonar
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
7
Ranking in other categories
Application Security Tools (34th), Static Code Analysis (10th)
Coverity Static
Average Rating
7.8
Reviews Sentiment
6.5
Number of Reviews
43
Ranking in other categories
Static Application Security Testing (SAST) (10th)
 

Mindshare comparison

CodeSonar and Coverity Static aren’t in the same category and serve different purposes. CodeSonar is designed for Application Security Tools and holds a mindshare of 1.1%, down 1.5% compared to last year.
Coverity Static, on the other hand, focuses on Static Application Security Testing (SAST), holds 2.7% mindshare, down 7.7% since last year.
Application Security Tools Mindshare Distribution
ProductMindshare (%)
CodeSonar1.1%
SonarQube12.4%
Checkmarx One8.2%
Other78.3%
Application Security Tools
Static Application Security Testing (SAST) Mindshare Distribution
ProductMindshare (%)
Coverity Static2.7%
SonarQube14.2%
Checkmarx One9.1%
Other74.0%
Static Application Security Testing (SAST)
 

Featured Reviews

Mathieu ALBRESPY - PeerSpot reviewer
Intigration Developer at ez-Wheel
Nice interface, quick to deploy, and easy to expand
This is the first time I've used this kind of software. It was the only one we could apply to analyze with MISRA rules. At my new company, I tried to use Klocwork. I tried to use it, just once so I cannot compare it exactly with CodeSonar. I also have a plugin for my Visual Studio and I try to make it work. It's not easy, however, I don't think that we have this kind of functionality with CodeSonar. It can do some incremental analysis. However, since this feature is also available on CodeSonar, it would be a good idea to have a plugin on Visual Studio just to have a quick analysis.
BL
Software Quality Expert at Endress+Hauser AG
Useful for extra checks but not recommended for C++
We're currently facing a primary challenge with automation using Coverity. Each developer has a license and can perform manual checks, and we also have a nightly build that analyzes the entire software. The main issue is that the tool can't look behind submodules in our code base, so it doesn't see changes stored there. This limitation means it can't detect changes accurately, forcing us to analyze all files instead of just the modified ones. It struggles with repositories organized with different submodules. Although documentation suggests it's possible to configure Coverity to handle this, it requires effort. The solution's analysis tools are high-quality, but the web design could improve. For example, the data is organized into pages when there are many findings, such as ten thousand lines of information. Each page shows about a hundred items, and navigating through these pages (from items 100 to 200, 200 to 300, and so on) can be cumbersome. I've heard from a colleague about another Synopsys tool with a very good GUI. It might be a solution for us to include with Coverity. We invested in Coverity, but compared to SonarQube, it lacks a good interface. SonarQube has a responsive, intuitive GUI, but its analysis quality isn't as good as Coverity's. Coverity's interface isn't great, but its analysis is much better. We hope Synopsys will improve Coverity because it doesn't make a good impression when you first use it. We started with the command line and saw the results were very good. We moved from another tool with a slightly better GUI, but it crashed often, so Coverity was an improvement. When I used the solution earlier, I noticed some issues. It supports C++, which we use, but there's room for improvement. Coverity has two plug-ins. The newer one works well for languages like C# or Java and is very responsive. When we evaluated it with Synopsys, they presented it as easy to configure and install. However, C++ slows down significantly because it's analyzing in the background. It's not very responsive when typing, likely due to the many included files in C++ that need analysis. It's not as quick as with C# or other languages, where you get immediate feedback from Coverity. The classic plug-in is still supported but old-fashioned. It has a manual option, but I haven't checked it. The main problem for C++ users who prefer the old plug-in is responsiveness.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable features of CodeSonar were all the categorized classes provided, and reports of future bugs which might occur in the production code. Additionally, I found the buffer overflow and underflow useful."
"CodeSonar has helped our organization because it detects dead and nonusable parts of code to create a more optimized code."
"The solution is very stable and we have used it for a long time with no issues."
"It has been able to scale."
"What I like best about CodeSonar is that it has fantastic speed, analysis and configuration times."
"I would suggest trying out automated tools along with CodeSonar on your project, and you will find out that CodeSonar reports many more defects compared to other static analysis tools, so this is a very important tool."
"It has helped us a lot with some issues and has helped us avoid bad code."
"CodeSonar’s most valuable feature is finding security threats."
"It's very stable."
"Coverity integrates with issue-tracking systems like Jira and provides email notifications, alerts, and other features."
"The product has been beneficial in logging functionality, allowing me to categorize vulnerabilities based on severity. This aids in providing updated reports on subsequent scans."
"The solution effectively identifies bugs in code."
"Coverity provides developers with a good, best practice, coding advice, and tracks risks of poor coding quality."
"The features I find most valuable is that our entire company can publish the analysis results into our central space."
"If you have enough budget, it is one of the best solutions right now."
"It has the lowest false positives."
 

Cons

"It was difficult for us to apply a rule, especially to a part of the code, and not apply it to the rest of the code."
"The MISRA guidelines were not appropriately reported and there were some flags or errors."
"There could be a shared licensing model for the users."
"It was expensive."
"In a future release, the solution should upgrade itself to the current trends and differentiate between the languages. If there are any classifications that can be set for these programming languages that would be helpful rather than having everything in the generic category."
"It would be beneficial for the solution to include code standards and additional functionality for security."
"In terms of areas for improvement, the use case for CodeSonar was good, but compared to other tools, it seems CodeSonar isn't a sound static analysis tool, and this is a major con I've seen from it. Right now, in the market, people prefer sound static analysis tools, so I would have preferred if CodeSonar was developed into a sound static analysis tool formally, in terms of its algorithms, so then you can see it extensively used in the market because at the moment, here in India, only fifty to sixty customers use CodeSonar. If the product is developed into a sound static analysis tool, it could compete with Polyspace, and from its current fifty customers, that number could go up to a hundred."
"The scanning tool for core architecture could be improved."
"The level of vulnerability that this solution covers could be improved compared to other open source tools."
"I had tried integrating the tool with Azure DevOps, but the report I got stated that my team faced many challenges."
"Coverity takes a lot of time to dereference null pointers."
"This is a pretty expensive solution. The overall value of the solution could be improved if the price was reduced."
"We actually specified several checkers, but we found some checkers had a higher false positive rate. I think this is a problem. Because we have to waste some time is really the issue because the issue is not an issue. I mean, the tool pauses or an issue, but the same issue is the filter now.Some check checkers cannot find some issues, but sometimes they find issues that are not relevant, right, that are not really issues. Some customisation mechanism can be added in the next release so that we can define our Checker. The Modelling feature provided by Coverity helps in finding more information for potential issues but it is not mature enough, it should be mature. The fast testing feature for security testing campaign can be added as well. So if you correctly integrate it with the training team, maybe you can help us to find more potential issues."
"The product lacks sufficient customization options."
"We'd like it to be faster."
"Coverity is far from perfection, and I'm not 100 percent sure it's helping me find what I need to find in my role. We need exactly what we are looking for, i.e. security errors and vulnerabilities. It doesn't seem to be reporting while we are changing our code."
 

Pricing and Cost Advice

"The application’s pricing is high compared to other tools."
"Our organization purchased a license to use the solution."
"Pricing is a bit costly."
"The solution's price depends on the number of licenses needed and the source code for the project."
"I would rate the tool's pricing a one out of ten."
"I rate Coverity's price a ten on a scale of one to ten, where one is cheap and ten is expensive."
"Coverity’s price is on the higher side. It should be lower."
"Offers varying prices for different companies"
"The tool was fairly priced."
"The solution's pricing is comparable to other products."
"The tool's price is somewhere in the middle. It's neither cheap nor expensive. I would rate the pricing a five out of ten."
"Coverity is quite expensive."
report
Use our free recommendation engine to learn which Application Security Tools solutions are best for your needs.
903,147 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
24%
Computer Software Company
8%
Financial Services Firm
7%
University
7%
Manufacturing Company
29%
Computer Software Company
9%
Financial Services Firm
7%
Comms Service Provider
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise1
Large Enterprise2
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise6
Large Enterprise31
 

Questions from the Community

Ask a question
Earn 20 points
How would you decide between Coverity and Sonarqube?
We researched Coverity, but in the end, we chose SonarQube. SonarQube is a tool for reviewing code quality and security. It helps to guide our development teams during code reviews by providing rem...
What needs improvement with Coverity?
The price is a concern, and there are a lot of false positives coming through. Support with Coverity is adequate, but they take a longer time to respond. The core support is not straightforward, an...
 

Comparisons

 

Also Known As

No data available
Synopsys Static Analysis
 

Overview

 

Sample Customers

Viveris, Micrel Medical Devices, Olympus, SOFTEQ, SONY
SAP, Mega International, Thales Alenia Space
Find out what your peers are saying about SonarSource Sàrl, Checkmarx, Veracode and others in Application Security Tools. Updated: June 2026.
903,147 professionals have used our research since 2012.