Mend.io Reviews

The license management of WhiteSource was at a good level. As compared to other tools that I have used, its functionality for the licenses for the code libraries was quite good. Its UI was also fine.

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.

I have used this solution for one year. 

I wouldn't call it stable because we could not build it into the pipeline, and it caused failures.

They were quite responsive, but in the end, they couldn't help with anything to make it work. For any feature requests that we had on our side, they always claimed that they were part of the roadmap, but after that, nothing happened.

It was quite straightforward. It was intended to be done on the DevOps side. It was nothing special. It didn't work after the setup. It caused build failures.

I would rate WhiteSource a three out of ten considering the fact that we couldn't use it while we were paying for it. It had good features, but we couldn't use it.

We use this solution for scanning NodeJS and Maven projects during the CI/CD processes. We have hundreds of scans per day for any project that runs on our CI and passes the release build.

This means that any release build runs the WhiteSource scan before deployment to production clusters, which ensures that we are pretty covered in terms of licenses for open source dependencies.

We are running on top of hundreds of microservices and thousands of daily builds, of which part of them are moving to production deployment eventually.  

In general, we are covered for open source licensing issues and CVE errors on particular versions for open source dependencies. Moreover, we have covered ourselves for security auditing by stating that we are users of WhiteSource.

The most valuable feature is the unified JAR to scan for all langs (wss-scanner jar). It helps us to scan easily and is agnostic to the technology.

The dashboard UI and UX are problematic. This solution looks like a 1995 web site and it's very hard to understand what the issue is and why it failed.

I have been using WhiteSource for almost five years.

The stability is great.

Our account manager is the best!

This is my first open-source scanning solution.

The setup was performed independently.

I didn't choose it but I saw a demo of Synk.

Improve the UI please... developers cannot find themselves in this dashboard.

With WhiteSource, we have been able to automate the scan of our Open Source dependencies. Before, it was a 50% automated in-house solution.

• Open Source dependencies scan
• Common Vulnerabilities and Exposures (CVE) detection
• Useful license and copyright reports.
• Dashboards to manage the risk by product or by organisation.

We are using a lot of Open Source components to develop our products. WhiteSource is the perfect tool to manage the Open Source governance. All our continuous integration stack is using WhiteSource to scan our dependencies (Maven, NPM, Docker).

Next, we are integrating the WhiteSource reports in our products (in a legal-notices folder) to store all the copyright and licensing information. WhiteSource replaced a painful and complex in-house solution, now it's fully automated.

Notifications could be improved. Everything else is OK.

If one of our products is using a dependency with a black-listed license (LGPL, for example) we like to notify the developer who added this dependency. And we use the same notification if you try to use a component with no license or no copyright information.

No issues.

No issues.

Customer Service:

A nine out of 10. They are really reactive when we have a question.

Technical Support:

A nine out of 10. They are really reactive when we have a question.

We were using an in-house solution based on some Maven plugins. The process was not fully-automated. We were looking for a fully-automated solution.

Really straightforward. The first scan was ready in 30 minutes.

My team (release engineering) implemented WhiteSource for our company.

We are really happy to use WhiteSource. A lot of time has been saved and the results are more accurate.

The setup cost is cheap. For our company, we received a good price to manage unlimited products and versions.

We did a comparison with Black Duck, but WhiteSource was better at managing the Open Source stuff.

We are a happy customer.

Its ease of use and good results are the most valuable.

It would be good if it can do dynamic code analysis. It is not necessarily in that space, but it can do more because we have too many tools.

Their partner relationship support is a little bit confusing. They haven't really streamlined the support process when we buy through a reseller. They should improve their process.

I have been using this solution for one month. I am using its latest version.

We are still implementing it. We haven't gone through scalability, but we don't expect any problem.

Their support is average. Their partner relationship support is a little bit confusing. They haven't really streamlined the support process when we buy through a reseller. 

The initial setup was pretty straightforward. The deployment took about three weeks.

We did it ourselves.

I would rate WhiteSource a nine out of ten. It is a good product.

The inventory management as well as the ability to identify security vulnerabilities has been the most valuable for our business. 

The turnaround time for upgrading databases for this tool as well as the accuracy could be improved. 

It would be good if containerization could be included under the current licensing but this is not something I have looked into.

I have been using this solution for four years.

This is a stable solution.

This is a scalable solution. 

This solution offers good support which we have used multiple times. 

Positive

The initial setup of this solution was straightforward and easy.

This is an expensive solution. 

When setting up this solution, it is important to have clear cut planning and to define the automation rules. 

I would recommend using WhiteSource. It has an edge over other tools in the market and is a faster solution. 

WhiteSource is easy to integrate with the CICD pipeline and runs standalone scans as it is a SaaS deployment. Integration of this solution does not require much time or knowledge. 

I would rate this solution a nine out of ten. 

I use this solution for product inventory trace and 3PPs handling in aspect of License Compliance & Security.

I've been using both the UI & API.

At first, WhiteSource was great in regards to have a clear picture of what we use in our products.

Then later, we started having different issues with WhiteSource, especially in our containers/Docker images. The problem has not been resolved yet, even after many followups on this matter.

The most valuable features are the reporting, customizing libraries "In-house, White list, license selection", comparing the products/projects, and License & Copyright resolution.

WhiteSource needs improvement in the scanning of the containers and images with distinguishing the layers.

This solution needs better support and customer service.

I have been using WhiteSource for one year.