Try our new research platform with insights from 80,000+ expert users

Contrast Security Assess vs GitHub comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 25, 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

Contrast Security Assess
Ranking in Application Security Tools
30th
Average Rating
8.8
Reviews Sentiment
7.2
Number of Reviews
11
Ranking in other categories
Static Application Security Testing (SAST) (27th)
GitHub
Ranking in Application Security Tools
4th
Average Rating
8.8
Reviews Sentiment
6.7
Number of Reviews
97
Ranking in other categories
Version Control (3rd), Agile and DevOps Services (2nd)
 

Mindshare comparison

As of February 2026, in the Application Security Tools category, the mindshare of Contrast Security Assess is 1.3%, up from 0.5% compared to the previous year. The mindshare of GitHub is 1.3%, up from 0.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Security Tools Market Share Distribution
ProductMarket Share (%)
GitHub1.3%
Contrast Security Assess1.3%
Other97.4%
Application Security Tools
 

Featured Reviews

reviewer1605099 - PeerSpot reviewer
Director of Threat and Vulnerability Management at a consultancy with 10,001+ employees
We're gathering vulnerability data from multiple environments in real time, fundamentally changing how we identify issues in applications
The solution is very accurate in identifying vulnerabilities. In cases where we are performing application assessment using Contrast Assess, and also using legacy application security testing tools, Contrast successfully identifies the same vulnerabilities that the other tools have identified but it also identifies significantly more. In addition, it has visibility into application components that other testing methodologies are unaware of. Assess also provides the option of helping developers incorporate security elements while they're writing code. It depends on whether individual developers decide to utilize the information that's provided to them from the solution, but it definitely gives them visibility into more environments. It gives them an opportunity to remediate vulnerabilities well before production deployments.
Murathan OK - PeerSpot reviewer
Software Development Manager at a media company with 10,001+ employees
CI/CD workflows have become streamlined and AI support has improved collaborative development
We are using GitHub because it is open-source software, which is the most valuable solution for us. The open source and community support are very good. We are always up-to-date with the community, and integration difficulty is very low. If you integrate any CI/CD solutions on GitHub, it's very easy. We started using GitHub about three months ago with AI integration. For our deployments, some developers can be very shy about asking for descriptions on their commits. We are using AI support for comments and deployment management, which is beautiful. We are not using the GitHub API for automating workflows in our projects. I give GitHub a five-star rating for the review capabilities. I also give GitHub five stars for integration with third-party applications. There is a lot of integration available on GitHub. If you want to integrate something, even if it could be integrated before GitHub, you can make your code and integrate your own in-house applications. It's a very easy and powerful aspect of GitHub.

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 accurate in identifying vulnerabilities. In cases where we are performing application assessment using Contrast Assess, and also using legacy application security testing tools, Contrast successfully identifies the same vulnerabilities that the other tools have identified but it also identifies significantly more. In addition, it has visibility into application components that other testing methodologies are unaware of."
"When we access the application, it continuously monitors and detects vulnerabilities."
"Assess has an excellent API interface to pull APIs."
"The most valuable feature is the continuous monitoring aspect: the fact that we don't have to wait for scans to complete for the tool to identify vulnerabilities. They're automatically identified through developers' business-as-usual processes."
"The accuracy of the solution in identifying vulnerabilities is better than any other product we've used, far and away. In our internal comparisons among different tools, Contrast consistently finds more impactful vulnerabilities, and also identifies vulnerabilities that are nearly guaranteed to be there, meaning that the chance of false positives is very low."
"No other tool does the runtime scanning like Contrast does. Other static analysis tools do static scanning, but Contrast is runtime analysis, when the routes are exercised. That's when the scan happens. This is a tool that has a very unique capability compared to other tools. That's what I like most about Contrast, that it's runtime."
"By far, the thing that was able to provide value was the immediate response while testing ahead of release, in real-time."
"We use the Contrast OSS feature that allows us to look at third-party, open-source software libraries, because it has a cool interface where you can look at all the different libraries. It has some really cool additional features where it gives us how many instances in which something has been used... It tells us it has been used 10 times out of 20 workloads, for example. Then we know for sure that OSS is being used."
"If you want to share documents, you can create articles and diagrams with GitHub and share."
"The technical support of the solution is good, and our company has used it for GitHub upgrades."
"A great feature is being able to have different repositories and different kinds of projects in a single solution at a single time. It's just a click away."
"I find the most valuable collaboration between our peers to be a seamless collaboration between our peers. We can connect and change our code, allowing us to be agile in our projects. Since we're talking about DevOps, we're using Jenkins in our pipeline. It helps speed up the process by automating the DevOps workflow."
"The most valuable aspects of GitHub are version control and parallel development. I also appreciate the forking part, which allows us to release a specific set of features to the environment."
"The learning curve is small."
"The solution is scalable."
"GitHub allows us the option to push files from a non-UA method or directly upload files from the UA. You can integrate GitHub with Jenkins to do CI/CD."
 

Cons

"Contrast's ability to support upgrades on the actual agents that get deployed is limited. Our environment is pretty much entirely Java. There are no updates associated with that. You have to actually download a new version of the .jar file and push that out to your servers where your app is hosted. That can be quite cumbersome from a change-management perspective."
"I would like to see them come up with more scanning rules."
"The solution should provide more details in the section where it shows that third-party libraries have CVEs or some vulnerabilities."
"The product's retesting part needs improvement. The tool also needs improvement in the suggestions provided for fixing vulnerabilities. It relies more on documentation rather than on quick fixes."
"Contrast Security Assess covers a wide range of applications like .NET Framework, Java, PSP, Node.js, etc. But there are some like Ubuntu and the .NET Core which are not covered. They have it in their roadmap to have these agents. If they have that, we will have complete coverage."
"Regarding the solution's OSS feature, the one drawback that we do have is that it does not have client-side support. We'll be missing identification of libraries like jQuery or JavaScript, and such, that are client-side."
"The solution needs to improve flexibility...The scalability of the product is a problem in the solution, especially from a commercial perspective."
"The out-of-the-box reporting could be improved. We need to write our own APIs to make the reporting more robust."
"The storage for this solution could be improved."
"I think one area where GitHub could improve is its search and navigation functionality within repositories. For example, we use IDEs like IntelliJ or Visual Studio Code when developing code. These IDEs allow us to easily navigate from one piece of code to another file where a method is being called. It would be really helpful if the solution could add this navigation feature."
"There are still areas for improvement with GitHub Actions and their deployment workflows, as they have made significant progress but are not yet polished."
"GitHub could expand the limits of the free version."
"The solution could have better support for the Markdown language."
"GitHub could improve in resolving conflicts when multiple developers modify the same line of code."
"They're improving the work items to track the progress of the team, but in my experience, Azure DevOps is better in this functionality. GitHub needs to improve the form to track the progress of the work done by a team."
"In complex cases, we have to use the terminal for conflict resolution. If those conflicts could be resolved visually in the editor, that would be much better."
 

Pricing and Cost Advice

"The good news is that the agent itself comes in two different forms: the unlicensed form and the licensed form. Unlicensed gives use of that software composition analysis for free. Thereafter, if you apply a license to that same agent, that's when the instrumentation takes hold. So one of my suggestions is to do what we're doing: Deploy the agent to as many applications as possible, with just the SCA feature turned on with no license applied, and then you can be more choosy and pick which teams will get the license applied."
"I like the per-application licensing model... We just license the app and we look at different vulnerabilities on that app and we remediate within the app. It's simpler."
"The solution is expensive."
"The product's pricing is low. I would rate it a two out of ten."
"You only get one license for an application. Ours are very big, monolithic applications with millions of lines of code. We were able to apply one license to one monolithic application, which is great. We are happy with the licensing. Pricing-wise, they are industry-standard, which is fine."
"It's a tiered licensing model. The more you buy, as you cross certain quantity thresholds, the pricing changes. If you have a smaller environment, your licensing costs are going to be different than a larger environment... The licensing is primarily per application. An application can be as many agents as you need. If you've got 10 development servers and 20 production servers and 50 QA servers, all of those agents can be reporting as a single application that utilizes one license."
"For what it offers, it's a very reasonable cost. The way that it is priced is extremely straightforward. It works on the number of applications that you use, and you license a server. It is something that is extremely fair, because it doesn't take into consideration the number of requests, etc. It is only priced based on the number of onboarded applications. It suits our model as well, because we have huge traffic. Our number of applications is not that large, so the pricing works great for us."
"We pay a licensing fee for GitHub, which could be cheaper."
"If I consider the market standards, the product's price is pocket-friendly."
"Regarding pricing, I'd rate it eight out of ten. It's decent and not too expensive, and small businesses can also afford it. With AWS taking CodeCommit out of the market, I don't see many competitors for small companies in terms of GitHub."
"It’s an open-source solution."
"The licensing model for GitHub is user-based. Whenever the new developer joins we have to get a new license and register their ID. The overall price of the solution is reasonable."
"The licensing model from GitHub is very clear."
"I use the free version of the tool."
"If there are only 10 people using a particular repository, then GitHub is free. But if we increase the number of users, we need to pay the normal charge for GitHub."
report
Use our free recommendation engine to learn which Application Security Tools solutions are best for your needs.
881,757 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
23%
Manufacturing Company
11%
Computer Software Company
10%
Comms Service Provider
6%
Marketing Services Firm
11%
Financial Services Firm
9%
Comms Service Provider
7%
Computer Software Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise3
Large Enterprise6
By reviewers
Company SizeCount
Small Business42
Midsize Enterprise13
Large Enterprise49
 

Questions from the Community

Ask a question
Earn 20 points
What do you like most about GitHub?
The control is the most valuable feature as developers can work on a single code.
What is your experience regarding pricing and costs for GitHub?
I was paying approximately one hundred dollars annually about a year ago. I am uncertain of the current cost, but GitHub without Copilot is free as far as I know. I am not paying anything for my Gi...
What needs improvement with GitHub?
Security could make GitHub better. OWASP Top Ten security advisors could be integrated on GitHub, and it could provide checks and advice. That would be much better. Additionally, LLM integration on...
 

Also Known As

Contrast Assess
No data available
 

Overview

 

Sample Customers

Williams-Sonoma, Autodesk, HUAWEI, Chromeriver, RingCentral, Demandware.
Dominion Enterprises, NASA, Braintree, SAP, CyberAgent
Find out what your peers are saying about Contrast Security Assess vs. GitHub and other solutions. Updated: February 2026.
881,757 professionals have used our research since 2012.