Fortify Software Security Center vs GitHub Code Scanning comparison

OpenText and GitHub are both solutions in the Static Application Security Testing (SAST) category. OpenText is ranked #21 with an average rating of 9.0, while GitHub is ranked #13 with an average rating of 8.5. OpenText holds a 0.7% mindshare in SAST, compared to GitHub’s 1.6% mindshare. Additionally, 100% of OpenText users are willing to recommend the solution, compared to 100% of GitHub users who would recommend it.

Fortify Software Security C...

Read 8 Fortify Software Security Center reviews

729 Views
671 Comparison Views

100% willing to recommend

GitHub Code Scanning

Read 6 GitHub Code Scanning reviews

1,318 Views
1,265 Comparison Views

100% willing to recommend

Fortify Software Security C...

GitHub Code Scanning

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Oct 8, 2024

```html

Fortify Software Security Center and GitHub Code Scanning compete in identifying software vulnerabilities. Fortify Software Security Center is favored for user satisfaction and ease of deployment, while GitHub Code Scanning stands out for cost-effectiveness and integration capabilities.

Features: Fortify Software Security Center provides comprehensive vulnerability identification, risk analysis, and robust security protocols. GitHub Code Scanning offers seamless integration with CI/CD workflows, automated testing, and continuous monitoring capabilities.

Room for Improvement: Fortify Software Security Center could improve compatibility with modern development environments, synchronization with development tools, and flexibility. GitHub Code Scanning could enhance advanced threat detection, scanning speed, and threat metrics.

Ease of Deployment and Customer Service: Fortify Software Security Center is noted for a straightforward deployment process and responsive customer service. GitHub Code Scanning is appreciated for quick setup in cloud environments but would benefit from more comprehensive support options.

Pricing and ROI: Fortify Software Security Center is considered costly with a slower ROI, but its extensive feature set is seen as a long-term benefit. GitHub Code Scanning provides faster ROI and cost savings, making it appealing to smaller teams and budget-conscious enterprises.

```

To learn more, read our detailed Fortify Software Security Center vs. GitHub Code Scanning Report (Updated: December 2025).

Buyer's Guide

Fortify Software Security Center vs. GitHub Code Scanning

December 2025

Download the complete report

Helped 879,259 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

Fortify Software Security C...

Ranking in Static Application Security Testing (SAST)

21st

Average Rating

8.0

Reviews Sentiment

4.6

Number of Reviews

Ranking in other categories

No ranking in other categories

GitHub Code Scanning

Ranking in Static Application Security Testing (SAST)

13th

Average Rating

8.6

Reviews Sentiment

6.7

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of December 2025, in the Static Application Security Testing (SAST) category, the mindshare of Fortify Software Security Center is 0.7%, up from 0.3% compared to the previous year. The mindshare of GitHub Code Scanning is 1.6%, up from 0.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Static Application Security Testing (SAST) Market Share Distribution
Product	Market Share (%)
GitHub Code Scanning	1.6%
Fortify Software Security Center	0.7%
Other	97.7%

Static Application Security Testing (SAST)

Featured Reviews

Diego Caicedo Lescano

Chief Innovation Officer at SAGGA

Enables centralized analysis and improves governance through seamless tool integration

The main use case for Fortify Software Security Center is exceptional because we have governance and control through that console. You can centralize both static analysis and dynamic analysis, and correlate both analyses in one tool to get better results by combining those independent results from each solution. That is outstanding, and there is no tool I have seen on the market that offers these capabilities. I appreciate the interoperability with other solutions from Fortify Software Security Center. Because we are using Kiuwan, you can run Kiuwan analyses and integrate them with Fortify Software Security Center to get those results in a single console. That is a good console for centralizing things in one point. That is one of the best features of the on-premises Fortify.

Read full review

AbhishekKumar20

Software Development Manager at Amazon

Code scanning identifies vulnerabilities quickly and improves team response with minimal setup

I have been using Git for approximately 13-14 years. I have used GitHub Code Scanning for about three to four years. The primary purpose is to identify any vulnerability in the code itself. The system logs vulnerabilities that we can immediately examine to see all the error-prone areas. The AI functionalities include predefined agents that scan through and immediately provide responses regarding the best nomenclature or code coverage percentage. It's actually a one-time setup, and the team benefits as long as they push code and changes in the repository itself. Every time we push something, we immediately check the total deviation, whether our code coverage has improved, or if any vulnerability has been identified. There is always a metrics dashboard that we can see and identify. Primarily, GitHub is used for doing the versioning itself in the repository. With vulnerability functionality being provided and AI agents available, it makes a complete package. As soon as we publish our code, we immediately get to know the test code coverage. This immediately informs us about all the vulnerable areas which are not being fully tested. If we address those areas, most vulnerabilities are resolved. Even after tests are added, if by any chance the test is not treated cleanly or corner cases are missed, GitHub Code Scanning immediately flags those corners. It's always beneficial to have because it's not humanly possible to check all corner case scenarios, but as a system where they diagnose each line item, that's very helpful.

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

"The reporting is very useful because you can always view an entire list of the issues that you have."

"The overall rating for this tool is ten out of ten."

"I like the explanation of issues provided by Fortify Software Security Center."

"This is a stable solution at the end of the day."

"It's very important because they want to scan their source code every day, so we provide CICD integration to our customers so they can auto build and auto test every day, get reports, and fix issues."

"Software Security Center is highly customizable and helps me test all vulnerability data against the latest conventions like OWASP Top Ten, CVE Top twenty-five, and several other legal compliances."

"You can easily download the tool's rule packs and update them."

"The main use case for Fortify Software Security Center is exceptional because we have governance and control through that console."

More Fortify Software Security Center pros

"The solution helps identify vulnerabilities by understanding how ports communicate with applications running on a system. Ports are like house numbers; to visit someone's house, you must know their number. Similarly, ports are used to communicate with applications. For example, if you want to use an HTTP web server, you must use port 80. It is the port on which the web application or your server listens for incoming requests."

"GitHub Code Scanning has positively impacted my organization as it helps us recognize errors and avoid many later issues which may arise."

"The static code analysis capability in GitHub Code Scanning is a very powerful feature, providing the ability to identify vulnerabilities and ensure code quality."

"We use GitHub Code Scanning mostly for source code management."

"It's very scalable, very easy to handle, and very intuitive."

"GitHub Code Spaces brings significant value with its simplicity and ease of use."

Cons

"Improvements needed for Software Security Center include better aggregation views of datasets."

"Fortify Software Security Center's setup is really painful."

"Improvements needed for Software Security Center include better aggregation views of datasets."

"The support for Fortify on-premises is the same as for the other products. I would say the support is not good and I would rate it a three out of ten."

"The product's overlap feature is restrictive and requires more customization efforts, which can be expensive."

"This solution is difficult to implement, and it should be made more comfortable for the end-users."

"We are having issues with false positives that need to be resolved."

"I am not satisfied with the percentage of false positives, which is around eighteen percent."

"One area for improvement could be the ability to have an AI system digest the reports generated from code scanning and provide a summary. Currently, the reports can be extensive, and users may overlook details, such as outdated libraries, which could be highlighted for attention."

"When running code scans, GitHub Code Scanning provides recommendations for probable fixes. However, integrating a feature where developers receive real-time highlights of vulnerabilities when checking in or merging a PR would be beneficial."

"GitHub Code Scanning should add more templates."

"At times it becomes very annoying as it highlights certain things which are intuitive. They require code coverage for those aspects as an extra overhead."

Pricing and Cost Advice

"The solution is priced fair."

"This is a costly solution that could be cheaper."

"As a Fortify partner company providing technical support, I find the product expensive in our country, where local, inexpensive products are available."

"GitHub Code Scanning is a moderately priced solution."

"The minimum pricing for the tool is five dollars a month."

See which vendors are best for you

Use our free recommendation engine to learn which Static Application Security Testing (SAST) solutions are best for your needs.

See recommendations

879,259 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Manufacturing Company

18%

Financial Services Firm

10%

Government

Computer Software Company

12%

Financial Services Firm

10%

Manufacturing Company

Transportation Company

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

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

No data available

Questions from the Community

What is your experience regarding pricing and costs for Micro Focus Software Security Center?

The pricing for the on-premises Fortify is expensive.

See all answers

What needs improvement with Micro Focus Software Security Center?

In my opinion, there are no areas that could be improved with Fortify Software Security Center. I would say it is a good product and a mature product. However, the SAST has many improvement areas. ...

See all answers

What is your primary use case for Micro Focus Software Security Center?

We have installed Fortify Static Code Analysis, SAST, in Ecuador in two customers. The Fortify ScanCentral includes three components: SAST, Fortify Software Security Center, and the WebInspect.

See all answers

What is your experience regarding pricing and costs for GitHub Code Scanning?

The organization pays for the license of GitHub Code Scanning, but specific price details are unknown.

See all answers

What needs improvement with GitHub Code Scanning?

In my opinion, areas of GitHub Code Scanning that could be improved include that a few things are not visible to us, such as where it stores data and which path. There is a separate team for that w...

See all answers

What advice do you have for others considering GitHub Code Scanning?

I am an end user only here with GitHub Code Scanning. I currently might be using the latest version of GitHub Code Scanning, but I don't remember the specific version. I have not utilized the real-...

See all answers

Comparisons

Checkmarx One vs Fortify Software Security Center

Compared 16% of the time

OpenText Core Application Security vs Fortify Software Security Center

Compared 14% of the time

Acunetix vs Fortify Software Security Center

Compared 10% of the time

Checkmarx IaC Security / KICS vs Fortify Software Security Center

Compared 9% of the time

Appvance AIQ Platform vs Fortify Software Security Center

Compared 4% of the time

More Fortify Software Security Center Competitors

SonarQube vs GitHub Code Scanning

Compared 30% of the time

Coverity Static vs GitHub Code Scanning

Compared 20% of the time

Aikido Security vs GitHub Code Scanning

Compared 9% of the time

HCL AppScan vs GitHub Code Scanning

Compared 7% of the time

Polaris Platform vs GitHub Code Scanning

Compared 3% of the time

More GitHub Code Scanning Competitors

Product Reports

Buyer's Guide

Static Application Security Testing (SAST)

November 2025

Download Fortify Software Security Center product report

Buyer's Guide

GitHub Code Scanning

December 2025

Download GitHub Code Scanning product report

Also Known As

Micro Focus Software Security Center, Application Security Center, HPE Application Security Center, WebInspect

No data available

Overview

Software Security Center enables management, development, and security teams to work together to triage, track, validate, automate, and manage software security activities.

OpenText

Code scanning is a feature that you use to analyze the code in a GitHub repository to find security vulnerabilities and coding errors. Any problems identified by the analysis are shown in GitHub.

GitHub

Sample Customers

Neosecure, Acxiom, Skandinavisk Data Center A/S, Parkeon

Information Not Available

Buyer's Guide

Fortify Software Security Center vs. GitHub Code Scanning

December 2025

Free Report: Fortify Software Security Center vs. GitHub Code Scanning

Find out what your peers are saying about Fortify Software Security Center vs. GitHub Code Scanning and other solutions. Updated: December 2025.

DOWNLOAD NOW

879,259 professionals have used our research since 2012.

See our Fortify Software Security Center vs. GitHub Code Scanning report.

See our list of best Static Application Security Testing (SAST) vendors.

We monitor all Static Application Security Testing (SAST) 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.