Coverity Reviews

I use the solution for static analysis.

The product has good API documentation. I’m quite happy with it. The product is easy to use.

Sometimes it's a bit hard to figure out how to use the product’s UI.

I have been using the solution for some years.

I have not faced any issues with the product’s stability.

The solution is scalable. Four people in my organization use the solution.

The initial setup is easy.

I am using the latest version of the product. I have also used Clang Static Analyzer. People planning to use the solution should try the open-source version first to understand how it works. We must have the paid version of the product to get all the resources and documentation. Overall, I rate the product an eight out of ten.

We are working on medical devices, and the code base is written in C++. We use Coverity to find the vulnerability in those C++ codes.

Coverity is easy to set up and has a less lengthy process to find vulnerabilities.

The solution's user interface and quality gate could be improved.

I have been using Coverity for four months.

Coverity has good stability.

I rate Coverity more than eight out of ten for stability.

Around 20 to 25 developers use Coverity in our organization.

I rate Coverity a seven to eight out of ten for scalability.

We use SonarQube for Java-based projects and Coverity for C and C++-based projects.

The solution’s initial setup is simple.

Overall, I rate Coverity a seven out of ten.

We use Coverity for static analysis of our code.

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. So either we are perfect, or the tool is missing something. 

I've been using Coverity for a couple of years.

I haven't had much experience trying to scale up Coverity. Only three people at our company work with it.

I encountered a bug with Coverity, and I opened a ticket. Support provided me with a workaround. So it's working at the moment, or at least it seems to be. They are on par with other tech support in terms of knowledge. However, their style of communication could use some improvement.

Setting up Coverity is highly complex. The upgrade procedure is also pretty tough. We've had trouble with it on at least one occasion. When I went ahead with it, it destroyed the installation. I couldn't go back. So it's challenging to understand from the documentation. It seems like they tried to cover all possible topics in their manuals, so they ended up scratching the surface of everything in the world except for the particular practical items that I needed.

Coverity is very expensive.

I rate Coverity five out of 10, but it's tough for me to judge because we decided to purchase it based on one requirement that no other static analysis tool could satisfy. For that reason, we haven't tried anything else. So, let's make an analogy. Let's say I used Sony TVs my entire life, and someone comes up and says, "Hey, there is a new brand of TVs. What do you think of them? Do you think they are good?" How would I know? By comparison, SonarQube seems to be more feature-rich for a standard programming language, and it works with more continuous integration tools.

• Raising the level of code quality, security, and robustness in the codebase
• Tracking and addressing code quality issues.
  

Coverity provides developers with a good, best practice, coding advice, and tracks risks of poor coding quality. Coverity reports have urged developers to improve the quality of their code.

• I like that it gives advice and training on how to resolve the most common quality issues. 
• Links to more details on each issue and the background and risks.
  

• Ability to follow source file s-links into the target location for issuing assignments through GIT.  Our current build environment uses symbolic links into the git repo and Coverity does not follow the link into the actual location of the source file to determine the git author.
• Single API for all interactions. I am not a fan of using both SOAP and REST APIs and Coverity offers a mix of functionality depending on the interface used. I would greatly prefer a full REST API with improved documentation for all actions including issuing assignments, streaming, and project creation. 

We are using GK and the latest version for port deployment.

I have been using Coverity for three and a half years.

Coverity is not stable but it is sufficient for our organization's requirements.

Coverity is scalable.

We contacted technical support to help us clean up an issue we had.

If they have a cluster structure, then definitely they should use Coverity. I would rate Coverity a nine out of ten.

We use it in our company during product development.

It provides reports about a lot of potential defects.

Its price can be improved. Price is always an issue with Synopsys.

I have been using Coverity for about three or four years.

It has good stability.

Its scalability is good. 

They are professional and very responsible. They have a local FAE.

It is not straightforward, but it is also not too complex. The learning curve needed for installing Coverity is okay.

It is expensive.

I would recommend this solution if you can afford it. If you have enough budget, it is one of the best solutions right now. There may be other cheaper solutions, but you get what you pay for.

We have been using Coverity for several years. We would not have continued using it if it was not a good solution. We always have some minor questions or improvements for them, and they always give us a relatively fast response.

I would rate Coverity a nine out of ten. Only its price should be improved.

We have a development team and we are using this product for static code analysis.

This product has definitely helped our organization. Based on what I have heard from the development team, they have found a lot of issues before code goes into production.

The most valuable feature is the integration with Jenkins. Jenkins can be used to automatically run it to perform the code analysis.

Integration with GitLab is helpful.

Coverity is too costly, which is why we are trying other tools. Ideally, it would have a user-based license that does not have a restriction in the number of lines of code.

We have been using Coverity for between five and six years.

Coverity is used across our entire organization.

The initial setup in the Windows environment was straightforward. However, for Linux, it has some complexity.

We have a separate team in the company that takes care of deployment. One person is enough for the task

The licensing fees are based on the number of lines of code. We may not need more than five user licenses but with a restriction on the number of lines of code, for a small company the cost will shoot up.

Our license for Coverity has expired and we are in the process of exploring new static code analysis tools. Ideally, we would like to have one that is low-cost.

One of the products that I have downloaded a trial version for is SonarQube. At this point, I have only installed the Windows version but I plan on testing the Linux version, as well.

In summary, this is a helpful product and the feedback that I have heard from the development team is good.

I would rate this solution an eight out of ten.

I am using the latest version for my business. I personally do product evaluations, and this product has improved the efficiency of my work.

The product improves the way that we do product evaluations.

It improves the quality of my work. 

They could improve the usability. For example, how you set things up, even though it's straightforward, it could be still be easier.

The stability works quite well.

The scalability is good enough.

We haven't had any problems with the product so far.

We did not have another solution before. We decided to purchase Coverity because the way we were working previously wasn't efficient. So, we were trying to improve our efficiency.

The initial setup was straightforward.

We have seen ROI.

The solution has helped to increase staff productivity and improved our work significantly by approximately 20 percent.

This solution seemed to fit our purposes.

Try it out for yourself, and decide whether it's useful for you.