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
4th
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 May 2026, in the Static Code Analysis category, the mindshare of CodeSonar is 3.8%, up from 3.0% compared to the previous year. The mindshare of OpenText Static Application Security Testing is 5.5%, down from 12.0% 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.5%
CodeSonar3.8%
Other90.7%
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 most valuable features of CodeSonar were all the categorized classes provided, and reports of future bugs which might occur in the production code. Additionally, I found the buffer overflow and underflow useful."
"What I like best about CodeSonar is that it has fantastic speed, analysis and configuration times."
"There is nice functionality for code surfing and browsing."
"It has been able to scale."
"The tool is very good for detecting memory leaks."
"The most valuable features of CodeSonar were all the categorized classes provided, and reports of future bugs which might occur in the production code."
"CodeSonar’s most valuable feature is finding security threats."
"The most valuable feature of CodeSonar is the catching of dead code. It is helpful."
"The integration Subset core integration, using Jenkins is one of the good features."
"My initial setup of Fortify Static Code Analyzer was good."
"I like Fortify Software Security Center or Fortify SSC. This tool is installed on each developer's machine, but Fortify Software Security Center combines everything. We can meet there as security professionals and developers. The developers scan their code and publish the results there. We can then look at them from a security perspective and see whether they fixed the issues. We can agree on whether something is a false positive and make decisions."
"We are satisfied with this solution."
"Fortify Static Code Analyzer tells us if there are any security leaks or not, and if there are, then it's notifying us and does not allow us to pass the DevOps pipeline, but if it finds everything is perfect as per our given guidelines, then it allows us to go ahead and start it, and we are able to deploy it."
"Automating the Jenkins plugins and the build title is a big plus."
"Fortify Static Code Analyzer's most valuable features are its ability to provide best practices for fixing code and its examples and capabilities to address security problems in the code."
"We write software, and therefore, the most valuable aspect for us is basically the code analysis part."
 

Cons

"It was expensive."
"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."
"There could be a shared licensing model for the users."
"The scanning tool for core architecture could be improved."
"It would be beneficial for the solution to include code standards and additional functionality for security."
"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."
"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."
"It would be beneficial for the solution to include code standards and additional functionality for security."
"Fortify's software security center needs a design refresh."
"The price can be improved."
"The pricing is a bit high. It would be nice if it was more competitive."
"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."
"Fortify Static Code Analyzer has a bit of a learning curve, and I don't find it particularly helpful in narrowing down the vulnerabilities we should prioritize."
"It comes with a hefty licensing fee."
"Currently, we get four to five errors on the side of tagging, and it notifies you of every tiny inconsistency."
"Fortify Static Code Analyzer is a good solution, but sometimes we receive false positives."
 

Pricing and Cost Advice

"The application’s pricing is high compared to other tools."
"Pricing is a bit costly."
"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 licensing is expensive and is in the 50K range."
"Although I am not responsible for the budget, Fortify SAST is expensive."
"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."
"The setup costs and pricing for Fortify may vary depending on the organization's needs and requirements."
"The price of Fortify Static Code Analyzer could be reduced."
"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."
"From our standpoint, we are significantly better off with Fortify due to the favorable pricing we secured five years ago."
"I rate the pricing of Fortify Static Code Analyzer as a seven out of ten since it is a bit expensive."
report
Use our free recommendation engine to learn which Static Code Analysis solutions are best for your needs.
893,221 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
24%
Computer Software Company
8%
University
7%
Financial Services Firm
7%
Financial Services Firm
28%
Manufacturing Company
9%
Computer Software 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.
893,221 professionals have used our research since 2012.