No more typing reviews! Try our Samantha, our new voice AI agent.

CodeSonar vs OpenText Static Application Security Testing comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 29, 2026

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

CodeSonar
Ranking in Static Code Analysis
10th
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
7
Ranking in other categories
Application Security Tools (30th)
OpenText Static Application...
Ranking in Static Code Analysis
5th
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
19
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Static Code Analysis category, the mindshare of CodeSonar is 3.6%, up from 3.0% compared to the previous year. The mindshare of OpenText Static Application Security Testing is 5.0%, down from 11.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Static Code Analysis Mindshare Distribution
ProductMindshare (%)
OpenText Static Application Security Testing5.0%
CodeSonar3.6%
Other91.4%
Static Code Analysis
 

Featured Reviews

Mathieu ALBRESPY - PeerSpot reviewer
Intigration Developer at ez-Wheel
Nice interface, quick to deploy, and easy to expand
This is the first time I've used this kind of software. It was the only one we could apply to analyze with MISRA rules. At my new company, I tried to use Klocwork. I tried to use it, just once so I cannot compare it exactly with CodeSonar. I also have a plugin for my Visual Studio and I try to make it work. It's not easy, however, I don't think that we have this kind of functionality with CodeSonar. It can do some incremental analysis. However, since this feature is also available on CodeSonar, it would be a good idea to have a plugin on Visual Studio just to have a quick analysis.
DK
Lead Information Security Analyst at a financial services firm with 10,001+ employees
Focuses on detailed scans to find critical vulnerabilities while ensuring minimal false positives
I think Fortify Static Code Analyzer could be improved by updating the number of rule packs according to the latest vulnerabilities we find each year. We have updated to a version that is one less than the current latest version. It would be really helpful to include trending vulnerabilities and how to manage them. While it includes all the OWASP top factors, AI has come into the picture, so those updates should also be considered. I haven't thought much about additional features for improvement since I am using it daily. Most of our work revolves around scanning and providing the results, which sometimes feels like a crunch. However, I believe rule pack updates should be implemented. It feels easy to upgrade to the latest version as well.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The solution is very stable and we have used it for a long time with no issues."
"It has been able to scale."
"The most valuable feature of CodeSonar is the catching of dead code. It is helpful."
"CodeSonar has helped our organization because it detects dead and nonusable parts of code to create a more optimized code."
"It has helped us a lot with some issues and has helped us avoid bad code."
"What I like best about CodeSonar is that it has fantastic speed, analysis and configuration times."
"What I like best about CodeSonar is that it has fantastic speed, analysis and configuration times. Its detection of all runtime errors is also very good, though there were times it missed a few. The configuration of logs by CodeSonar is also very fantastic which I've not seen anywhere else. I also like the GUI interface of CodeSonar because it's very user friendly and the tool also shows very precise logs and results."
"There is nice functionality for code surfing and browsing."
"You can really see what's happening after you've developed something."
"Automating the Jenkins plugins and the build title is a big plus."
"The stability of the solution is pretty good. There are no bugs or glitches."
"The most valuable features include its ability to detect vulnerabilities accurately and its integration with our CI/CD pipeline."
"Integrating the Fortify Static Code Analyzer into our software development lifecycle was straightforward. It highlights important information beyond just syntax errors. It identifies issues like password credentials and access keys embedded in the code."
"I recommend this product due to its good pricing, extensive language support, valuable features, and additional features like Fortify Academy."
"We've found the documentation to be very good."
"The integration Subset core integration, using Jenkins is one of the good features."
 

Cons

"It would be beneficial for the solution to include code standards and additional functionality for security."
"The scanning tool for core architecture could be improved."
"In a future release, the solution should upgrade itself to the current trends and differentiate between the languages. If there are any classifications that can be set for these programming languages that would be helpful rather than having everything in the generic category."
"It was expensive."
"CodeSonar could improve by having better coding rules so we did not have to use another solution, such as MISRA C."
"It was difficult for us to apply a rule, especially to a part of the code, and not apply it to the rest of the code."
"The MISRA guidelines were not appropriately reported and there were some flags or errors."
"In terms of areas for improvement, the use case for CodeSonar was good, but compared to other tools, it seems CodeSonar isn't a sound static analysis tool, and this is a major con I've seen from it. Right now, in the market, people prefer sound static analysis tools, so I would have preferred if CodeSonar was developed into a sound static analysis tool formally, in terms of its algorithms, so then you can see it extensively used in the market because at the moment, here in India, only fifty to sixty customers use CodeSonar. If the product is developed into a sound static analysis tool, it could compete with Polyspace, and from its current fifty customers, that number could go up to a hundred."
"Not all languages are supported in Fortify."
"The generation of false positives should be reduced."
"Streamlining the upgrade process and enhancing compatibility would make it easier for us to keep our security tools up-to-date."
"The price can be improved."
"The generation of false positives should be reduced."
"Fortify Static Code Analyzer is a good solution, but sometimes we receive false positives. If they could reduce the number of false positives it would be good."
"False positives need improvement in the future. Fortify's vulnerability remediation guidance helps improve code security, but I think they need to improve the focus of the solution, as it still contains many bugs and needs a thorough review."
"Their licensing is expensive."
 

Pricing and Cost Advice

"Our organization purchased a license to use the solution."
"The solution's price depends on the number of licenses needed and the source code for the project."
"The application’s pricing is high compared to other tools."
"Pricing is a bit costly."
"There is a licensing fee, and if you bring them to the company and you want them to do the installation and the implementation in the beginning, there is a separate cost. Similarly, if you want consultation or training, there is a separate cost. I see it as suitable only for enterprises. I do not see it suitable for a small business or individual use."
"From our standpoint, we are significantly better off with Fortify due to the favorable pricing we secured five years ago."
"It has a couple of license models. The one that we use most frequently is called their flexible deployment. We use this one because it is flexible and based on the number of code-contributing developers in the organization. It includes almost everything in the Fortify suite for one developer price. It gives access to not just the secure code analyzer (SCA) but also to FSC, the secure code. It gives us accessibility to scan central, which is the decentralized scanning farm. It also gives us access to the software security center, which is the vulnerability management platform."
"The setup costs and pricing for Fortify may vary depending on the organization's needs and requirements."
"The licensing is expensive and is in the 50K range."
"I rate the pricing of Fortify Static Code Analyzer as a seven out of ten since it is a bit expensive."
"Although I am not responsible for the budget, Fortify SAST is expensive."
"The price of Fortify Static Code Analyzer could be reduced."
report
Use our free recommendation engine to learn which Static Code Analysis solutions are best for your needs.
900,644 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
24%
Computer Software Company
8%
Financial Services Firm
7%
University
7%
Financial Services Firm
27%
Computer Software Company
9%
Manufacturing Company
9%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise1
Large Enterprise2
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise3
Large Enterprise11
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for Fortify Static Code Analyzer?
My experience with the pricing, setup costs, and licensing has been good. We have the scan machines, and we are planning to request more from Micro Focus now. We have calls every month or every oth...
What needs improvement with Fortify Static Code Analyzer?
I think Fortify Static Code Analyzer could be improved by updating the number of rule packs according to the latest vulnerabilities we find each year. We have updated to a version that is one less ...
What is your primary use case for Fortify Static Code Analyzer?
Our main use cases for Fortify Static Code Analyzer typically involve trying to figure out the critical vulnerabilities. It depends on the type of scans that we are doing, whether it is a release s...
 

Also Known As

No data available
Fortify Static Code Analysis SAST
 

Overview

 

Sample Customers

Viveris, Micrel Medical Devices, Olympus, SOFTEQ, SONY
Information Not Available
Find out what your peers are saying about CodeSonar vs. OpenText Static Application Security Testing and other solutions. Updated: April 2026.
900,644 professionals have used our research since 2012.