We performed a comparison between Coverity and Klocwork based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison Result: Based on the parameters we compared, Klocwork comes out ahead of Coverity. Although both products have valuable features and can be estimated as high-end solutions, our reviewers found that Coverity is expensive and its support has a slow response time.
"One of the most valuable features is Contributing Events. That particular feature helps the developer understand the root cause of a defect. So you can locate the starting point of the defect and figure out exactly how it is being exploited."
"Coverity is scalable."
"The solution effectively identifies bugs in code."
"The solution has helped to increase staff productivity and improved our work significantly by approximately 20 percent."
"The most valuable feature of Coverity is the wrapper. We use the wrapper to build the C++ component, then we use the other code analysis to analyze the code to the build object, and then send back the result to the SonarQube server. Additionally, it is a powerful capabilities solution."
"The security analysis features are the most valuable features of this solution."
"This solution is easy to use."
"The most valuable feature is that there were not a whole lot of false positives, at least on the codebases that I looked at."
"One can increase the number of vendors, so the solution is scalable."
"It's integrated into our CI, continuous integration."
"The most valuable feature of Klocwork is finding defects while you're doing the coding. For example, if you have an IDE plug-in of Klocwork on Visual Studio or Eclipse, you can find the faults; similar to using spell check on Word, you can find out defects during the development phase, which means that you don't have to wait till the development is over to find the flaws and address the deficiencies. I also find language support in Klocwork good because it used to support only C, C++, C#, and Java, but now, it also supports Java scripts and Python."
"Klocwork's most valuable feature is the static code analysis feature. It detects the potential problem earlier to allow the developer to receive feedback quickly and then address it before it becomes a problem."
"We like using the static analysis and code refactoring, which are very valuable because of our requirements to meet safety critical levels and reliability."
"The ability to create custom checkers is a plus."
"Technical support is quite good."
"The tool helps the team to think beforehand about corner cases or potential bugs that might arise in real-time."
"Its price can be improved. Price is always an issue with Synopsys."
"The solution could use more rules."
"We use GitHub and Gitflow, and Coverity does not fit with Gitflow. I have to create a screen for our branches, and it's a pain for developers. It has been difficult to integrate Coverity with our system."
"Coverity could improve the ease of use. Sometimes things become difficult and you need to follow the guides from the website but the guides could be better."
"The solution's user interface and quality gate could be improved."
"I would like to see integration with popular IDEs, such as Eclipse."
"Ideally, it would have a user-based license that does not have a restriction in the number of lines of code."
"It should be easier to specify your own validation routines and sanitation routines."
"Klocwork has to improve its features to stay ahead of other free solutions."
"Now the only issue we have is that whenever we need to get the code we have to build it first. Then we can get the report."
"Klocwork does have a problem with true positives. It only found 30% of true positives in the Juliet test case."
"I would like to see better codes between projects and a more user-friendly desktop in the next release."
"Modern languages, such as Angular and .NET, should be included as a part of Klocwork. They have recently added Kotlin as a part of their project, but we would like to see more languages in Klocwork. That's the reason we are using Coverity as a backup for some of the other languages."
"We'd like to see integration with Agile DevOps and Agile methodologies."
"What needs improvement in Klocwork, compared to other products in the market, is the dashboard or reporting mechanisms that need to be a bit more flexible. The Klocwork dashboard could be improved. Though it's good, it's not as good as some of the other products in the market, which is a problem. The reporting could be more detailed and easier to sort out because sorting in Klocwork could be a bit more time-consuming, mainly when sorting defects based on filters, compared to how it's done on other tools such as Coverity."
"I hope that in each new release they add new features relating to the addition of checkers, improving their analysis engines etc."
Coverity is ranked 4th in Static Application Security Testing (SAST) with 33 reviews while Klocwork is ranked 11th in Static Application Security Testing (SAST) with 20 reviews. Coverity is rated 7.8, while Klocwork is rated 8.2. The top reviewer of Coverity writes "Best SAST tool to check software quality issues". On the other hand, the top reviewer of Klocwork writes "Their technical team helps us get the most out of the solution, but we've faced some stability problems in our environment". Coverity is most compared with SonarQube, Fortify on Demand, Checkmarx One, Veracode and Polyspace Code Prover, whereas Klocwork is most compared with SonarQube, Polyspace Code Prover, CodeSonar, Checkmarx One and Veracode. See our Coverity vs. Klocwork report.
See our list of best Static Application Security Testing (SAST) vendors.
We monitor all Static Application Security Testing (SAST) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.