We performed a comparison between GitLab and Klocwork based on real PeerSpot user reviews.
Find out in this report how the two Application Security Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The stability is good."
"The code merging capability is something that we use very frequently."
"I have found the most valuable feature is security control. I also like the branching and cloning software."
"The scalability is good."
"GitLab is very useful for pipelines, continuous integration, and continuous deployment. It is also stable."
"GitLab is very well-organized and easy to use. Also, it offers most features that customers need."
"The most valuable features of GitLab are ease of use and highly intuitive UI and performance."
"CI/CD and GitLab scanning are the most valuable features."
"One can increase the number of vendors, so the solution is scalable."
"The most valuable feature is the Incremental analysis."
"There is a central Klocwork server at our headquarter in France so we connect the client directly to the server on-premises remotely."
"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."
"There's a feature in Klocwork called 'on-the-fly analysis', which helps developers to find and fix the defects at the time of development itself."
"It's integrated into our CI, continuous integration."
"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."
"The tool helps the team to think beforehand about corner cases or potential bugs that might arise in real-time."
"The solution could improve by providing more integration into the CI/CD pipeline, an autocomplete search tool, and more supporting documentation."
"We would like to generate document pages from the sources."
"We have only seen a couple of issues on Gitlab, which we use for building some of the applications."
"Some of the scripts that we encountered in GitLab were not fully functional and threw up errors."
"Even if I say I want some improvement, they will say it is already planned in the first quarter, second quarter, or third quarter. That said, most everything is quite improved already, and they're improving even further still."
"For as long as I have used GitLab, I haven't encountered any major limitations. However, I think that perhaps the search functionality could be better."
"GitLab would be improved with the addition of templates for deployment on local PCs."
"GitLab could improve by having more plugins and better user-friendliness."
"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 has to improve its features to stay ahead of other free solutions."
"The way to define the rules is too complex. The definition/rules for static analysis could be automated according to various SILs, so as to avoid confusion."
"The main problem is that since it only parses the code, the warnings or the problems that are given as a result of the report can sometimes require a lot of effort to analyze."
"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."
"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."
"This solution could be improved if they offered support of more languages including Ada and Golang. They currently only support seven languages."
"We bought Klocwork, but it was limited to one little program, but the program is now sort of failing. So, we have a license for usage on a program that is sort of failing, and we really can't use the license on anything else."
GitLab is ranked 7th in Application Security Tools with 70 reviews while Klocwork is ranked 16th in Application Security Tools with 20 reviews. GitLab is rated 8.6, while Klocwork is rated 8.2. The top reviewer of GitLab writes "Powerful, mature, and easy to set up and manage". 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". GitLab is most compared with Microsoft Azure DevOps, Bamboo, SonarQube, AWS CodePipeline and Tekton, whereas Klocwork is most compared with SonarQube, Coverity, Polyspace Code Prover and CodeSonar. See our GitLab vs. Klocwork report.
See our list of best Application Security Tools vendors and best Static Application Security Testing (SAST) vendors.
We monitor all Application Security Tools 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.
