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

GitHub vs Mend.io comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 29, 2024
 

Categories and Ranking

GitHub
Ranking in Application Security Tools
7th
Average Rating
8.8
Reviews Sentiment
7.6
Number of Reviews
88
Ranking in other categories
Version Control (3rd)
Mend.io
Ranking in Application Security Tools
17th
Average Rating
8.4
Number of Reviews
29
Ranking in other categories
Software Composition Analysis (SCA) (7th), Static Code Analysis (4th), Software Supply Chain Security (1st)
 

Mindshare comparison

As of November 2024, in the Application Security Tools category, the mindshare of GitHub is 0.9%, up from 0.8% compared to the previous year. The mindshare of Mend.io is 3.3%, down from 4.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Security Tools
 

Featured Reviews

AjayKrishna - PeerSpot reviewer
Sep 11, 2024
Reduces project delivery times and costs
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. It would allow us to move from one class file to another more easily, helping us search quicker and follow the code flow completely within GitHub. This would be more convenient than having to import the code into our local IDE to look at the code flow and navigate through it. Adding this kind of IDE-like navigation within the tool would make the user experience more seamless and efficient.
Jeffrey Harker - PeerSpot reviewer
May 12, 2022
Easy to use, great for finding vulnerabilities, and simple to set up
Finding vulnerabilities is pretty easy. Mend (formerly WhiteSource) does a great job of that and we had quite a few when we first put this in place. Governance up until that time had been manual and when we tried to do manual governance of a large codebase, our chances of success were pretty minimal. Mend (formerly WhiteSource) does a very good job of finding the open-source, checking the versions, and making sure they're secure. They notify us of critical high, medium, and low impacts, and if anything is wrong. We find the product very easy to use and we use it as a core part of our strategy for scanning product code moving toward release. We use Mend (formerly WhiteSource) Smart Fix. I’d say pretty much everything in Mend (formerly WhiteSource) is easy to use. We really don't have too much difficulty using the product at all. I've implemented other scanners and tools and had much more trouble with those products than we've ever had with Mend (formerly WhiteSource). That’s extremely important. It's hard to sell to some of these teams to put any level of overhead on top of their product development efforts and the fact that Mend (formerly WhiteSource) is as easy as it is to use is a critical aspect of adoption here. It scores very highly on that scale. Mend (formerly WhiteSource) Smart Fix helps our developers fix vulnerable transitive dependencies. It's all very helpful to our development community. First of all, we're able to find that there are issues. Second of all, we're able to figure out very quickly what needs to be done to remediate the issues. Mend (formerly WhiteSource) helped reduce our mean time to resolution since adopting it. A lot of it is process improvement and technical aspects that can tell us how to go about remediating the issues. We get that out of Mend (formerly WhiteSource). Making the developers aware that these issues are there and insisting they be corrected and making the effort to do that visibly is very valuable to us. Overall, Mend (formerly WhiteSource) helped dramatically reduce the number of open-source software vulnerabilities running in our production at any given point in time. I won't give metrics, however, it's fair to say that our state before and after Mend (formerly WhiteSource) is dramatically different and moved in a positive direction. Mend's ability to integrate our developer's existing workflows, including their IDE repository and CI is good. Azure DevOps is really important. That's what the pipelines are. That's a very important piece of the entire puzzle. If this was just an external scanner where periodically we'd go through and scan our repos and give them a report, we’d do that with pen testing products, for example, for security testing. The problem is, by the time they get those reports, they've already shipped the code to multiple environments and it's too late to stop the train. With these features being baked into the pipelines like this, they know immediately. As a result, we're able to quickly take action to remediate findings.

Quotes from Members

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

Pros

"The product's initial setup phase is easy but it is always good to connect with GitHub's team that manages APIs."
"The solution is scalable."
"The most valuable feature is the source code management. It's very helpful and it's a great product."
"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 features are GitHub Actions for triggering workflows, GitHub Secrets for saving credentials without needing a third-party service, and the UI for identifying errors in the code when we commit."
"GitHub is convenient and easy to use."
"Has great integration with third-party tools."
"The deployment is fast since we just have to run the script, and once it's done, it takes a few minutes."
"The dashboard view and the management view are most valuable."
"Its ease of use and good results are the most valuable."
"There are multiple different integrations there. We use Mend for CI/CD that goes through Azure as well. It works seamlessly. We never have any issues with it."
"What is very nice is that the product is very easy to set up. When you want to implement Mend.io, it just takes a few minutes to create your organization, create your products, and scan them. It's really convenient to have Mend scanning your products in less than one hour."
"WhiteSource is unique in the scanning of open-source licenses. Additionally, the vulnerabilities aspect of the solution is a benefit. We don't use WhiteSource in the whole organization, but we use it for some projects. There we receive a sense of the vulnerabilities of the open-source components, which improves our security work. The reports are automated which is useful."
"We use a lot of open sources with a variety of containers, and the different open sources come with different licenses. Some come with dual licenses, some are risky and some are not. All our three use cases are equally important to us and we found WhiteSource handles them decently."
"We can take some measures to improve things, replace a library, or update a library which was too old or showed severe bugs."
"Mend has reduced our open-source software vulnerabilities and helped us remediate issues quickly. My company's policy is to ensure that vulnerabilities are fixed before it gets to production."
 

Cons

"The product must document the CI/CD process more."
"GitHub could add some more security features."
"There could be some improvements related to the automation of certain processes, especially with the integration of artificial intelligence."
"Lacks sufficient support in terms of professional services that could be provided."
"The support team needs to have a well-defined SLA model since it is an area where the tool currently has some shortcomings."
"The solution could have better support for the Markdown language."
"GitHub uses basic configuration, but messaging is not clear."
"I would want to see some form of code security scanning implemented."
"The UI can be slow once in a while, and we're not sure if it's because of the amount of data we have, or it is just a slow product, but it would be nice if it could be improved."
"The initial setup could be simplified."
"The dashboard UI and UX are problematic."
"WhiteSource Prioritize should be expanded to cover more than Java and JavaScript."
"It should support multiple SBOM formats to be able to integrate with old industry standards."
"WhiteSource needs improvement in the scanning of the containers and images with distinguishing the layers."
"We specifically use this solution within our CICD pipelines in Azure DevOps, and we would like to have a gate so that if the score falls below a certain value then we can block the pipeline from running."
"We have ended our relationship with WhiteSource. We were using an agent that we built in the pipeline so that you can scan the projects during build time. But unfortunately, that agent didn't work at all. We have more than 500 projects, and it doubled or tripled the build time. For other projects, we had the failure of the builds without any known reason. It was not usable at all. We spent maybe one year working on the issues to try to make it work, but it didn't in the end. We should be able to integrate it with ID and Shift Left so that the developers are able to see the scan results without waiting for the build to fail."
 

Pricing and Cost Advice

"We are currently paying nothing for GitHub."
"The basic licensing model is free, and if you need to have technical support and such things, then it does cost something. You only need to pay extra if you need technical support."
"The price of this solution is reasonable."
"I haven't had to pay anything for GitHub, I use the free version."
"There are no licensing fees for the features that we use."
"GitHub is an open-source product, but when using the free-to-use version, anyone can see the code we're working on."
"I am using the free version of the solution. However, there are some costs my organization pays."
"I think, in terms of price, GitHub is okay compared to other tools."
"Mend is costly but not overly expensive. The license was quite expensive this year, but we managed to negotiate the price down to the same as last year. At the same time, it's a good value. We're getting what we're paying for and still not using all the features. We could probably get more out of the tool and make it more valuable. At the moment, we don't have the capacity to do that."
"WhiteSource is much more affordable than Veracode."
"The solution involves a yearly licensing fee."
"Over the last two years, they have tried to add more and more features to their license packages, but the price is a little bit high, comparatively."
"Pricing is competitive."
"This is an expensive solution."
"As we were using an SaaS-based service, the solution must be scalable, although my understanding is that this is based on the licensing model one is using."
"We are paying a lot of money to use WhiteSource. In our company, it is not easy to argue that it is worth the price. ​"
report
Use our free recommendation engine to learn which Application Security Tools solutions are best for your needs.
815,854 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
13%
Computer Software Company
12%
Financial Services Firm
11%
Government
7%
Financial Services Firm
18%
Computer Software Company
16%
Manufacturing Company
12%
Insurance Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

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 have not paid for GitHub as I use the free version for personal projects. Organizations may take separate servers from GitHub based on their needs, yet I am unaware of the pricing details.
What needs improvement with GitHub?
GitHub could improve in resolving conflicts when multiple developers modify the same line of code. Introducing a feature to manage and resolve conflicts directly within the application rather than ...
How does WhiteSource compare with SonarQube?
Red Hat Ceph does well in simplifying storage integration by replacing the need for numerous storage solutions. This solution allows for multiple copies of replicated and coded pools to be kept, ea...
How does WhiteSource compare with Black Duck?
We researched Black Duck but ultimately chose WhiteSource when looking for an application security tool. WhiteSource is a software solution that enables agile open source security and license compl...
What do you like most about Mend.io?
The best feature is that the Mend R&D team does their due diligence for all the vulnerabilities. In case they observe any important or critical vulnerabilities, such as the Log4j-related vulner...
 

Comparisons

 

Also Known As

No data available
WhiteSource, Mend SCA, Mend.io Supply Chain Defender, Mend SAST
 

Learn More

 

Overview

 

Sample Customers

Dominion Enterprises, NASA, Braintree, SAP, CyberAgent
Microsoft, Autodesk, NCR, Target, IBM, vodafone, Siemens, GE digital, KPMG, LivePerson, Jack Henry and Associates
Find out what your peers are saying about GitHub vs. Mend.io and other solutions. Updated: October 2024.
815,854 professionals have used our research since 2012.