We performed a comparison between GitLab and Polyspace Code Prover 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 initial setup of GitLab is pretty simple, with no complications."
"Git hosting has an integration with ACD which is why we liked this solution in the first place."
"The most valuable features of GitLab are ease of use and highly intuitive UI and performance."
"Their CI/CD engine is very mature. It's very comprehensive and flexible, and compared to other projects, I believe that GitLab is number one right now from that perspective."
"GitLab is very well-organized and easy to use. Also, it offers most features that customers need."
"The code merging capability is something that we use very frequently."
"The merging feature makes it easy later on for the deployment."
"GitLab's best features are continuous integration and fast deployment."
"The product detects memory corruptions."
"Polyspace Code Prover has made me realize it differs from other static code analysis tools because it runs the code. So it's quite distinct in that aspect."
"The outputs are very reliable."
"Polyspace Code Prover is a very user-friendly tool."
"When we work on safety modules, it is mandatory to fulfill ISO 26262 compliance. Using Prover helps fulfill the standard on top of many other quality checks, like division by zero, data type casts, and null pointer dereferences."
"The pricing model of GitLab is an issue for me."
"I used Spring Cloud config and to connect that to GitLab was so hard."
"The solution does not have many built-in functions or variables so scripting is required."
"GitLab could improve the patch repository. It does not have support for Conan patch version regions. Additionally, better support for Kubernetes deployment is needed as part of the package."
"GitLab's Windows version is yet not available and having this would be an improvement."
"It can be free for commercial use."
"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."
"There was a problem with the build environment when we were looking at developing iOS applications. iOS build require Mac machines and there are no Mac machines provided by GitLab in their cloud. So to build for mobile iOS application, we needed to use our own Mac machine within our own infrastructure. If GitLab were to provide a feature such that an iOS application could also be built through GitLab directly, that would be great."
"One of the main disadvantages is the time it takes to initiate the first run."
"I'd like the data to be taken from any format."
"Using Code Prover on large applications crashes sometimes."
"Automation could be a challenge."
"The tool has some stability issues."
GitLab is ranked 7th in Application Security Tools with 70 reviews while Polyspace Code Prover is ranked 23rd in Application Security Tools with 5 reviews. GitLab is rated 8.6, while Polyspace Code Prover is rated 7.6. The top reviewer of GitLab writes "Powerful, mature, and easy to set up and manage". On the other hand, the top reviewer of Polyspace Code Prover writes "A stable solution for developing software components". GitLab is most compared with Microsoft Azure DevOps, Bamboo, SonarQube, AWS CodePipeline and Tekton, whereas Polyspace Code Prover is most compared with SonarQube, Coverity, Klocwork, CodeSonar and Veracode. See our GitLab vs. Polyspace Code Prover report.
See our list of best Application Security Tools 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.
