We use Coverity during the software integration phase. We have a lot of components so we use Coverity to build the components, analyze and publish the data into sonar server and that's our work.
Software Integration Engineer at Thales
Enables our entire company to publish the analysis results into our central space
Pros and Cons
- "The features I find most valuable is that our entire company can publish the analysis results into our central space."
- "The setup takes very long."
What is our primary use case?
How has it helped my organization?
Depending on our product's needs, we defined the rule set to check and improve the source code.
What is most valuable?
The features I find most valuable is that our entire company can publish the analysis results into our central space. That allows us to see the latest quality of all components on the sonar web page.
What needs improvement?
My personal opinion is that the webpage of the last version of Coverity is not very easy to use. They've made some unnecessary changes and now I can't see all the analysis results or my status from when we started using the solution up to now. Because we have many components on the integration field, it is sometimes hard to find files of one specific component because we use relative path. When I look at the components, they all look very similar. But that is just my personal opinion.
I would also like to see a more user-friendly user interface and configuration. I can see the menu on the left but it's a little different from the other tools that I use, but this is perhaps only a personal thing.
Buyer's Guide
Coverity
November 2024
Learn what your peers think about Coverity. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
For how long have I used the solution?
We have been working on Coverity for about a year and a half
What do I think about the stability of the solution?
Coverity is a very stable solution.
What do I think about the scalability of the solution?
I believe the solution is scalable. Sometimes I want to put one component in a certain project, and I need to find what's the best way for us. We have a lot of users using Coverity and we will adapt it into our program.
How are customer service and support?
Most of the time I just do some research myself and Google their webpage to see how I can find a solution for my problem. The program has a tools team to help find the solutions.
Which solution did I use previously and why did I switch?
My personal business used other tools that offered sonar language tracking. We used a mix of programs with specific options and some standard gcc options. But last year our team preferred to use more visual tools to follow the whole company's policy. That is why we chose Coverity.
How was the initial setup?
We have an administrator for the deployment, so I am only a user. I just added a few projects and streams, and use the data extracted from the compilation, and run the analysis. The setup did take a long time, however.
What about the implementation team?
We implement through an in-house tools team.
What was our ROI?
I don't care it so much.
What's my experience with pricing, setup cost, and licensing?
For the setup, it's better to adapt the solution from the mature projects.
Don't care so much the pricing and licensing being the end user.
Which other solutions did I evaluate?
Before choosing, we tried to use gcc compiler options, i.e.
EXT_GCOV_FLAGS='-fprofile-arcs -ftest-coverage'
EXT_GCOV_LDFLAGS=-fprofile-arcs
EXT_CC_FLAGS=-fdiagnostics-show-option
GCOV_LIB=-lgcov
What other advice do I have?
I will suggest that when they use the program for a new project, they should just copy the data from a mature solution to the new project because the setup really takes a long time. We spent a lot of time to set Coverity up because I thought of creating the project in the Coverity server and use Coverity for the sonar part properly. But it took a long time. I will give the solution a 7.5 rating out of ten. When we officially use all the data, it will accumulate more experiences and then we will have different opinions.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Angestellter at a computer software company with 11-50 employees
A scalable and easy-to-use solution that can be easily deployed
Pros and Cons
- "The product is easy to use."
- "Sometimes it's a bit hard to figure out how to use the product’s UI."
What is our primary use case?
I use the solution for static analysis.
What is most valuable?
The product has good API documentation. I’m quite happy with it. The product is easy to use.
What needs improvement?
Sometimes it's a bit hard to figure out how to use the product’s UI.
For how long have I used the solution?
I have been using the solution for some years.
What do I think about the stability of the solution?
I have not faced any issues with the product’s stability.
What do I think about the scalability of the solution?
The solution is scalable. Four people in my organization use the solution.
How was the initial setup?
The initial setup is easy.
What other advice do I have?
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.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Coverity
November 2024
Learn what your peers think about Coverity. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
Consaltant at a tech consulting company with 501-1,000 employees
An easy-to-set-up solution used to find vulnerabilities in C++ codes, but its user interface could be improved
Pros and Cons
- "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."
What is our primary use case?
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.
What is most valuable?
Coverity is easy to set up and has a less lengthy process to find vulnerabilities.
What needs improvement?
The solution's user interface and quality gate could be improved.
For how long have I used the solution?
I have been using Coverity for four months.
What do I think about the stability of the solution?
Coverity has good stability.
I rate Coverity more than eight out of ten for stability.
What do I think about the scalability of the solution?
Around 20 to 25 developers use Coverity in our organization.
I rate Coverity a seven to eight out of ten for scalability.
Which solution did I use previously and why did I switch?
We use SonarQube for Java-based projects and Coverity for C and C++-based projects.
How was the initial setup?
The solution’s initial setup is simple.
What other advice do I have?
Overall, I rate Coverity a seven out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Works
It gives advice and training on how to resolve the most common quality issues, but the REST implementation is sub-par
What is our primary use case?
- Raising the level of code quality, security, and robustness in the codebase
- Tracking and addressing code quality issues.
How has it helped my organization?
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.
What is most valuable?
- 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.
What needs improvement?
- 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.
For how long have I used the solution?
One to three years.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Software Developer at Altair
Scalable, good for cluster structures, and has helpful technical support
Pros and Cons
- "Coverity is scalable."
- "Coverity is not stable."
What is our primary use case?
We are using GK and the latest version for port deployment.
For how long have I used the solution?
I have been using Coverity for three and a half years.
What do I think about the stability of the solution?
Coverity is not stable but it is sufficient for our organization's requirements.
What do I think about the scalability of the solution?
Coverity is scalable.
How are customer service and support?
We contacted technical support to help us clean up an issue we had.
What other advice do I have?
If they have a cluster structure, then definitely they should use Coverity. I would rate Coverity a nine out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Sr. QA Engineer at a computer software company with 1-10 employees
Good tech support but it doesn't report errors like it should
Pros and Cons
- "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."
- "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."
What is our primary use case?
We use Coverity for static analysis of our code.
What needs improvement?
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.
For how long have I used the solution?
I've been using Coverity for a couple of years.
What do I think about the scalability of the solution?
I haven't had much experience trying to scale up Coverity. Only three people at our company work with it.
How are customer service and support?
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.
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
Coverity is very expensive.
What other advice do I have?
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.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Director at a manufacturing company with 10,001+ employees
Stable, scalable, and provides reports about a lot of potential defects
Pros and Cons
- "It provides reports about a lot of potential defects."
- "Its price can be improved. Price is always an issue with Synopsys."
What is our primary use case?
We use it in our company during product development.
What is most valuable?
It provides reports about a lot of potential defects.
What needs improvement?
Its price can be improved. Price is always an issue with Synopsys.
For how long have I used the solution?
I have been using Coverity for about three or four years.
What do I think about the stability of the solution?
It has good stability.
What do I think about the scalability of the solution?
Its scalability is good.
How are customer service and technical support?
They are professional and very responsible. They have a local FAE.
How was the initial setup?
It is not straightforward, but it is also not too complex. The learning curve needed for installing Coverity is okay.
What's my experience with pricing, setup cost, and licensing?
It is expensive.
What other advice do I have?
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.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Technical Specialist at a tech services company with 201-500 employees
Integrates well with Jenkins and GitLab, and has helped us find errors before going into production
Pros and Cons
- "The most valuable feature is the integration with Jenkins."
- "Ideally, it would have a user-based license that does not have a restriction in the number of lines of code."
What is our primary use case?
We have a development team and we are using this product for static code analysis.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
We have been using Coverity for between five and six years.
What do I think about the scalability of the solution?
Coverity is used across our entire organization.
How was the initial setup?
The initial setup in the Windows environment was straightforward. However, for Linux, it has some complexity.
What about the implementation team?
We have a separate team in the company that takes care of deployment. One person is enough for the task
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Download our free Coverity Report and get advice and tips from experienced pros
sharing their opinions.
Updated: November 2024
Product Categories
Static Application Security Testing (SAST)Popular Comparisons
SonarQube Server (formerly SonarQube)
Veracode
GitLab
Checkmarx One
OWASP Zap
SonarQube Cloud (formerly SonarCloud)
Fortify on Demand
Acunetix
PortSwigger Burp Suite Professional
HCL AppScan
Qualys Web Application Scanning
Klocwork
Invicti
Parasoft SOAtest
Kiuwan
Buyer's Guide
Download our free Coverity Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- What is the difference between Coverity and SonarQube?
- What is the biggest difference between Coverity and SonarQube?
- How would you decide between Coverity and Sonarqube?
- What Application Security Solution Do You Use That Is DevOps Friendly?
- Which is the most comprehensive open source Web Security Testing tool?
- What is the best Application Security Testing platform?
- When evaluating Application Security Testing, what aspect do you think is the most important to look for?
- SAST vs. DAST: Which is better for application security testing?
- What tools do you rely on for building a DevSecOps pipeline?
- What does the Log4j/Log4Shell vulnerability mean for your company?