FOSSA vs OpenText Static Application Security Testing comparison

The compared FOSSA and OpenText solutions aren't in the same category. FOSSA is ranked #10 in SCA , with an average rating of 8.0, and holds a 3.0% mindshare in the category. OpenText is ranked #4 in SCAS , with an average rating of 7.5, and holds a 6.4% mindshare. Additionally, 92% of FOSSA users are willing to recommend the solution, compared to 89% of OpenText users who would recommend it.

FOSSA

Read 15 FOSSA reviews

1,904 Views
1,847 Comparison Views

92% willing to recommend

OpenText Static Application...

Read 19 OpenText Static Application Security Testing reviews

4,414 Views
1,412 Comparison Views

89% willing to recommend

FOSSA

OpenText Static Application...

Comparison Buyer's Guide

Download the report

Executive Summary

We performed a comparison between FOSSA and OpenText Static Application Security Testing based on real PeerSpot user reviews.

Find out what your peers are saying about Snyk, Black Duck, Veracode and others in Software Composition Analysis (SCA).

To learn more, read our detailed Software Composition Analysis (SCA) Report (Updated: March 2026).

Buyer's Guide

Software Composition Analysis (SCA)

March 2026

Download the complete report

Helped 884,797 peers since 2012

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

FOSSA

Average Rating

8.6

Reviews Sentiment

7.9

Number of Reviews

Ranking in other categories

Software Composition Analysis (SCA) (10th)

OpenText Static Application...

Average Rating

8.2

Reviews Sentiment

6.9

Number of Reviews

Ranking in other categories

Static Code Analysis (4th)

Mindshare comparison

While both are Security Software solutions, they serve different purposes. FOSSA is designed for Software Composition Analysis (SCA) and holds a mindshare of 3.0%, down 3.3% compared to last year.
OpenText Static Application Security Testing, on the other hand, focuses on Static Code Analysis, holds 6.4% mindshare, down 11.3% since last year.

Software Composition Analysis (SCA) Mindshare Distribution
Product	Mindshare (%)
FOSSA	3.0%
Black Duck SCA	11.7%
Snyk	10.5%
Other	74.8%

Software Composition Analysis (SCA)

Static Code Analysis Mindshare Distribution
Product	Mindshare (%)
OpenText Static Application Security Testing	6.4%
Veracode	13.3%
Checkmarx One	10.1%
Other	70.19999999999999%

Static Code Analysis

Featured Reviews

reviewer2588340

Senior Software Engineer at a manufacturing company with 10,001+ employees

Dependency management enhanced with update suggestions but lacks precise vulnerability tracking

FOSSA does not show the exact line of code with vulnerabilities, which adds time to the process as we have to locate these manually. Some other tools like Check Point or SonarQube provide exact line numbers for bugs. Also, the process in FOSSA can be quite contradicting and not very straightforward for new users.

Read full review

Dristi Kurre

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.

Read full review

Quotes from Members

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

Pros

"Being able to know the licenses of the libraries is most valuable because we sell products, and we need to provide to the customers the licenses that we are using."

"The support team has just been amazing, and it helps us to have a great support team from FOSSA. They are there to triage and answer all our questions which come up by using their product."

"FOSSA provided us with contextualized, easily actionable intelligence that alerted us to compliance issues. I could tell FOSSA exactly what I cared about and they would tell me when something was out of policy. I don't want to hear from the compliance tool unless I have an issue that I need to deal with. That was what was great about FOSSA is that it was basically "Here's my policy and only send me an alert if there's something without a policy." I thought that it was really good at doing that."

"The most valuable feature is definitely the ease and speed of integrating into build pipelines, like a Jenkins pipeline or something along those lines. The ease of a new development team coming on board and integrating FOSSA with a new project, or even an existing project, can be done so quickly that it's invaluable and it's easy to ask the developers to use a tool like this. Those developers greatly value the very quick feedback they get on any licensing or security vulnerability issues."

"I am impressed with the tool’s seamless integration and quick results."

"One of the things that I really like about FOSSA is that it allows you to go very granular. For example, if there's a package that's been flagged because it's subject to a license that may be conflicts with or raises a concern with one of the policies that I've set, then FOSSA enables you to go really granular into that package to see which aspects of the package are subject to which licenses. We can ultimately determine with our engineering teams if we really need this part of the package or not. If it's raising this flag, we can make really actionable decisions at a very micro level to enable the build to keep pushing forward."

"The most valuable feature is its ability to identify all of the components in a build, and then surface the licenses that are associated with it, allowing us to make a decision as to whether or not we allow a team to use the components. That eliminates the risk that comes with running consumer software that contains open source components."

"I found FOSSA's out-of-the-box policy engine to be accurate and that it was tuned appropriately to the settings that we were looking for. The policy engine is pretty straightforward... I find it to be very straightforward to make small modifications to, but it's very rare that we have to make modifications to it. It's easy to use. It's a four-category system that handles most cases pretty well."

More FOSSA pros

"We've found the documentation to be very good."

"Its flexibility is most valuable. It is such a flexible tool. It can be implemented in a number of ways. It can do anything you want it to do. It can be fully automated within a DevOps pipeline. It can also be used in an ad hoc, special test case scenario and anywhere in between."

"You can really see what's happening after you've developed something."

"My initial setup of Fortify Static Code Analyzer was good."

"The most valuable features include its ability to detect vulnerabilities accurately and its integration with our CI/CD pipeline."

"Automating the Jenkins plugins and the build title is a big plus."

"We are satisfied with this solution."

"Fortify Static Code Analyzer tells us if there are any security leaks or not. If there are, then it's notifying us and does not allow us to pass the DevOps pipeline. If it is finds everything's perfect, as per our given guidelines, then it is allowing us to go ahead and start it, and we are able to deploy it."

More OpenText Static Application Security Testing pros

Cons

"On the dashboard, there should be an option to increase the column width so that we can see the complete name of the GitHub repository. Currently, on the dashboard, we see the list of projects, but to see the complete name, you have to hover your mouse over an item, which is annoying."

"I wish there was a way that you could have a more global rollout of it, instead of having to do it in each repository individually. It's possible, that's something that is offered now, or maybe if you were using the CI Jenkins, you'd be able to do that. But with Travis, there wasn't an easy way to do that. At least not that I could find. That was probably the biggest issue."

"On the legal and policy sides, there is some room for improvement. I know that our legal team has raised complaints about having to approve the same dependency multiple times, as opposed to having them it across the entire organization."

"I would like the FOSSA API to be broader. I would like not to have to interact with the GUI at all, to do the work that I want to do. I would like them to do API-first development, rather than a focus on the GUI."

"The solution provides contextualized, actionable, intelligence that alerts us to compliance issues, but there is still a little bit of work to be done on it. One of the issues that I have raised with FOSSA is that when it identifies an issue that is an error, why is it in error? What detail can they give to me? They've improved, but that still needs some work. They could provide more information that helps me to identify the dependencies and then figure out where they originated from."

"I would like more customized categories because our company is so big. This is doable for them. They are still in the stages of trying to figure this out since we are one of their biggest companies that they support."

"I want the product to include binary scanning which is missing at the moment. Binary scanning includes code and component matching through dependency management. It also includes the actual scanning and reverse engineering of the boundaries and finding out what is inside."

"If you have thousands of applications, organizing them all into teams or tags is challenging."

More FOSSA cons

"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."

"Not all languages are supported in Fortify."

"It can be tricky if you want to exclude some files from scanning. For instance, if you do not want to scan and push testing files to Fortify Software Security Center, that is tricky with some IDEs, such as IntelliJ. We found that there is an Exclude feature that is not working. We reported that to them for future fixing. It needs some work on the plugins to make them consistent across IDEs and make them easier."

"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."

"I have not seen a return on investment with Fortify Static Code Analyzer."

"It comes with a hefty licensing fee."

"Fortify's software security center needs a design refresh."

"I know the areas that they are trying to improve on. They've been getting feedback for several years. There are two main points. The first thing is keeping current with static code languages. I know it is difficult because code languages pop up all the time or there are new variants, but it is something that Fortify needs to put a better focus on. They need to keep current with their language support. The second thing is a philosophical issue, and I don't know if they'll ever change it. They've done a decent job of putting tools in place to mitigate things, but static code analysis is inherently noisy. If you just take a tool out of the box and run a scan, you're going to get a lot of results back, and not all of those results are interesting or important, which is different for every organization. Currently, we get four to five errors on the side of tagging, and it notifies you of every tiny inconsistency. If the tool sees something that it doesn't know, it flags, which becomes work that has to be done afterward. Clients don't typically like it. There has got to be a way of prioritizing. There are a ton of filter options within Fortify, but the problem is that you've got to go through the crazy noisy scan once before you know which filters you need to put in place to get to the interesting stuff. I keep hearing from their product team that they're working on a way to do container or docker scanning. That's a huge market mover. A lot of people are interested in that right now, and it is relevant. That is definitely something that I'd love to see in the next version or two."

More OpenText Static Application Security Testing cons

Pricing and Cost Advice

"The solution's pricing is good and reasonable because you can literally use a lot of it for free."

"FOSSA is not cheap, but their offering is top-notch. It is very much a "you get what you pay for" scenario. Regardless of the price, I highly recommend FOSSA."

"The solution's cost is a five out of ten."

"FOSSA is a fairly priced product. It is not either cheaper or expensive. The pricing lies somewhere in the middle. The solution is worth the money that we are spending to use it."

"Its price is reasonable as compared to the market. It is competitively priced in comparison to other similar solutions on the market. It is also quite affordable in terms of the value that it delivers as compared to its alternative of hiring a team."

"The setup costs and pricing for Fortify may vary depending on the organization's needs and requirements."

"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."

"I rate the pricing of Fortify Static Code Analyzer as a seven out of ten since it is a bit expensive."

"The price of Fortify Static Code Analyzer could be reduced."

"Although I am not responsible for the budget, Fortify SAST is expensive."

"From our standpoint, we are significantly better off with Fortify due to the favorable pricing we secured five years ago."

"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 licensing is expensive and is in the 50K range."

See which vendors are best for you

Use our free recommendation engine to learn which Software Composition Analysis (SCA) solutions are best for your needs.

See recommendations

884,797 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Manufacturing Company

20%

Financial Services Firm

10%

Comms Service Provider

Educational Organization

Financial Services Firm

28%

Manufacturing Company

Computer Software Company

Government

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

By reviewers
Company Size	Count
Small Business	5
Midsize Enterprise	1
Large Enterprise	8

By reviewers
Company Size	Count
Small Business	4
Midsize Enterprise	3
Large Enterprise	11

Questions from the Community

What is your experience regarding pricing and costs for FOSSA?

The solution's pricing is good and reasonable because you can literally use a lot of it for free. You have to pay for the features you need, which I think is fair. If you want to get value for free...

See all answers

What needs improvement with FOSSA?

See all answers

What is your primary use case for FOSSA?

I have worked with FOSSA primarily to manage the dependencies in our projects. For example, if I take a Spring Boot application, FOSSA helps in identifying mismatches or unsupported dependencies th...

See all answers

What do you like most about Fortify Static Code Analyzer?

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 pa...

See all answers

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...

See all answers

What needs improvement with Fortify Static Code Analyzer?

See all answers

Comparisons

Snyk vs FOSSA

Compared 25% of the time

Black Duck SCA vs FOSSA

Compared 22% of the time

JFrog Xray vs FOSSA

Compared 9% of the time

Mend.io vs FOSSA

Compared 8% of the time

More FOSSA Competitors

Black Duck SCA vs OpenText Static Application Security Testing

Compared 17% of the time

Veracode vs OpenText Static Application Security Testing

Compared 11% of the time

Snyk vs OpenText Static Application Security Testing

Compared 11% of the time

Sonatype Lifecycle vs OpenText Static Application Security Testing

Compared 7% of the time

Mend.io vs OpenText Static Application Security Testing

Compared 7% of the time

More OpenText Static Application Security Testing Competitors

Product Reports

Buyer's Guide

FOSSA

March 2026

Download FOSSA product report

Buyer's Guide

OpenText Static Application Security Testing

March 2026

OpenText Static Application Security Testing report

Download OpenText Static Application Security Testing product report

Also Known As

No data available

Fortify Static Code Analysis SAST

Overview

Up to 90% of any piece of software is from open source, creating countless dependencies and areas of risk to manage. FOSSA is the most reliable automated policy engine for legal teams to maintain license compliance, security to fix vulnerabilities, and engineering to improve code quality across the entire software supply chain. As the only developer-native open source management platform, FOSSA fully integrates with your existing CI/CD pipeline to provide complete visibility and context earlier in the software development lifecycle. For the first time, teams can collaboratively shift left and audit, analyze, control, and remediate license issues and vulnerabilities right in their existing workflows.

FOSSA

OpenText Static Application Security Testing empowers teams with efficient vulnerability detection and streamlined secure coding practices, offering comprehensive language support and seamless integration with development tools.

OpenText Static Application Security Testing enhances software security during development by accurately identifying vulnerabilities with minimal false positives. It integrates seamlessly with IDEs and CI/CD pipelines, making it highly efficient for early detection of security issues. Users benefit from its easy setup, clear documentation, and centralized portal for managing security findings. Despite facing challenges like high costs and complex configurations for certain languages, its role in facilitating compliance and streamlining secure coding processes is indispensable. Improvements are needed in areas such as outdated design, language support, and integration capabilities to meet evolving user expectations.

What features does OpenText Static Application Security Testing offer?

Seamless IDE Integration: Integrates effortlessly with development environments for real-time feedback.
Comprehensive Language Support: Covers a wide range of programming languages, enhancing detection accuracy.
Centralized Security Portal: Provides a streamlined interface for managing vulnerabilities.

What benefits and ROI should users consider?

Enhanced Security: Identifies vulnerabilities early, preventing potential breaches.
Time Efficiency: Automates processes and speeds up remediation efforts.
Compliance Facilitation: Assists in adhering to security standards and regulations.

Organizations across diverse sectors implement OpenText Static Application Security Testing primarily to secure applications during development phases. Its integration with tools like GitLab, Jenkins, and Azure DevOps ensures a robust security pipeline. By combining with Sonatype Nexus, secure code, and library management is achieved effectively.

OpenText

Sample Customers

AppDyanmic, Uber, Twitter, Zendesk, Confluent

Information Not Available

Buyer's Guide

Software Composition Analysis (SCA)

March 2026

Download Free Report

Find out what your peers are saying about Snyk, Black Duck, Veracode and others in Software Composition Analysis (SCA). Updated: March 2026.

DOWNLOAD NOW

884,797 professionals have used our research since 2012.

We monitor all Software Composition Analysis (SCA) 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.