We just raised a $30M Series A: Read our story

WhiteSource OverviewUNIXBusinessApplication

WhiteSource is #3 ranked solution in top Software Composition Analysis (SCA) tools and #8 ranked solution in application security tools. IT Central Station users give WhiteSource an average rating of 8 out of 10. WhiteSource is most commonly compared to SonarQube:WhiteSource vs SonarQube. WhiteSource is popular among the large enterprise segment, accounting for 72% of users researching this solution on IT Central Station. The top industry researching this solution are professionals from a computer software company, accounting for 35% of all views.
What is WhiteSource?

The leading solution for agile open source security and license compliance management, WhiteSource integrates with the DevOps pipeline to detect vulnerable open source libraries in real-time.

It provides remediation paths and policy automation to speed up time-to-fix. It also prioritizes vulnerability alerts based on usage analysis.

We support over 200 programming languages and offer the widest vulnerability database aggregating information from dozens of peer-reviewed, respected sources.

WhiteSource Buyer's Guide

Download the WhiteSource Buyer's Guide including reviews and more. Updated: November 2021

WhiteSource Customers

Microsoft, Autodesk, NCR, Comcast, Nokia, Forgerock, indeed.com, GE digital, KPMG, LivePerson, Jack Henry and Associates

WhiteSource Video

Pricing Advice

What users are saying about WhiteSource pricing:
  • "Pricing is competitive."
  • "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."

WhiteSource Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
reviewer1261788
VP R&D at a computer software company with 51-200 employees
Real User
Top 20
Policy automation and automatic fix suggestions help us to save time in finding and solving problems

Pros and Cons

  • "With the fix suggestions feature, not only do you get the specific trace back to where the vulnerability is within your code, but you also get fix suggestions."
  • "The UI is not that friendly and you need to learn how to navigate easily."

What is our primary use case?

We use WhiteSource mainly to automate open source vulnerability detection and remediation, as well as for license compliance.

I’m less on the side of the license but mainly use the service to get control over vulnerabilities, detect the ones that affect us and remediate accordingly.

We integrate WhiteSource to our pipeline via CI server integration and now started using the GitHub integration too. We also run an agent in specific use cases.

How has it helped my organization?

WhiteSource improved our team’s ability to deal with vulnerabilities in a timely manner. Most of the time the alerts pile up and no one wants to deal with it, but the process now is much more simplified and convenient. It is still a task, but the service reduces the time spent on it significantly. It is very easy to use and the research decreased to almost none.

The GitHub integration provides us with the option to prevent security issues related to our open source libraries pre-build. It helped our teams discover vulnerabilities before usage, and fix issues within our existing environment and workflow.

What is most valuable?

The policy automation on effective vulnerabilities feature had a major impact on how we address open source vulnerabilities since it focuses on effective vulnerabilities and directs you to the specific methods. Other services will give a much larger list to remediate. I believe it cuts around 80% of alerts.

With the fix suggestions feature, not only do you get the specific trace back to where the vulnerability is within your code, but you also get fix suggestions. It sounds simple but I haven’t seen this capability with any other solution. This saves quite some time.

There are more small things within the UI that focus on giving the quickest remediation path, and I believe this is the WhiteSource’s strongest area.

What needs improvement?

The UI is not that friendly and you need to learn how to navigate easily. It also doesn’t run as smoothly as I would want or expect, and I believe it requires some improvements. That said, the Success team is very attentive and does reply and answer related matters quite fast.

Currently, effective vulnerabilities are only available in two languages, which is great, but I would be very happy to see more languages. It does cover most of our libraries, but we do have other languages in use. More coverage on that aspect would be helpful.

For how long have I used the solution?

I have been using WhiteSource for one and a half years.

What do I think about the stability of the solution?

We evaluated a few tools before moving forward with WhiteSource, and I have used other free tools as well. Comparing WhiteSource to others, some are stronger in terms of stability and UI performance, but don’t provide as much value as WhiteSource (by far).

On the results side, the databases are updated regularly and the results are very accurate. We requested some libraries for review here and there, but nothing major. 99.9% of the time we have accurate and proactive data.

What do I think about the scalability of the solution?

We started off slowly with WhiteSource and never experienced any issues around this topic.

That said, I’m not sure if it plays a part in the UI issues.

How are customer service and technical support?

Technical support is the best I’ve ever worked with.

They really take seriously customers' requests (and we sent over quite a few), and always reach out to help us make the most out of the platform.

I have never received a late reply, and the CS has a really good relationship with the team.

Which solution did I use previously and why did I switch?

We didn't use anything before, only manually.

How was the initial setup?

The initial setup was quick and easy. The CS team and the documentation were very helpful. We kicked off in a few days and the integration went smoothly.

Which other solutions did I evaluate?

We’ve evaluated Snyk, also used their free version and free dependency checkers.


Disclosure: I am a real user, and this review is based on my own experience and opinions.
reviewer1250697
User at a tech vendor with 1,001-5,000 employees
Vendor
Top 20
Vulnerability and license alerts help us stay compliant with software releases

Pros and Cons

  • "Attribution and license due diligence reports help us with aggregating the necessary data that we, in turn, have to provide to satisfy the various licenses copyright and component usage disclosures in our software."
  • "Some detected libraries do not specify a location of where in the source they were matched from, which is something that should be enhanced to enable quicker troubleshooting."

What is our primary use case?

Our primary use for WhiteSource is security and license risk detection in open-source, third-party libraries and components. We run scans from multiple source control and build systems (TFS, ADO, Jenkins, ...). Some of our scans are automated, while others are done manually with the unified file agent in offline mode scan, and then the resulting "wsjson" file is uploaded to the WS SaaS portal.

How has it helped my organization?

We moved from Black Duck to WhiteSource as it was a more modern and scalable solution, with better integration support to various build and source environments. The ease of running scans and getting results quickly enables our developers to address issues quicker. 

What is most valuable?

The most valuable features of this solution are:

  1. The vulnerability and license alerts are the main purposes of us utilizing this tool. We don't want to ship software and mistakenly include a GPL component. Similarly, we want to stay up to date on all vulnerabilities in third-party libraries so we can take action if our software solutions are impacted.
  2. Implementing policies is helpful because it's great when certain "no-nos" can be codified as policies and auto-rejected.
  3. Attribution and license due diligence reports help us with aggregating the necessary data that we, in turn, have to provide to satisfy the various licenses copyright and component usage disclosures in our software.

What needs improvement?

Places in need of improvement are:

  1. Some detected libraries do not specify a location of where in the source they were matched from, which is something that should be enhanced to enable quicker troubleshooting.
  2. Manual uploads of "wsjson" files can only be done by a global admin. Product administrators should be given this right for uploading files to their products/projects.
  3. Better support for proxies is needed when running the unified file agent behind a proxy. It can be made to work, but the Java proxy config and cert trust for MitM traffic inspection are very painful to set up.

For how long have I used the solution?

We have been using WhiteSource for two years.

What do I think about the stability of the solution?

In our two years of usage, there has been a negligible amount of downtime. We have, however, experienced occasional issues with certain features of the offer that created some friction and grumblings from our devs using the portal, but those have typically been resolved fairly quickly. 

What do I think about the scalability of the solution?

This is a SaaS offering that has so far taken everything we have thrown at it (150+ products, with multiple projects in each). Certain reports that aggregate data globally could take a while to churn, but well within acceptable time-frames.

How are customer service and technical support?

Responses are quick; TS works hard to resolve issues quickly. 

Which solution did I use previously and why did I switch?

Prior to this solution, we used Black Duck. As of two years ago, when we made the switch, WhiteSource's UI was more modern, the SaaS solution more scalable, and the integration capabilities far superior. The detection accuracy between the two was quite similar. 

How was the initial setup?

Setting up the tool for automated usage is very straightforward. Follow the documentation carefully and you will likely be fully up and running in between 15 and 60 mins.

What about the implementation team?

We implemented this solution using our in-house team.

What's my experience with pricing, setup cost, and licensing?

Pricing is competitive.

Which other solutions did I evaluate?

We also use NPM Audit and Snyk, but as an augmentation; not as competitors. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Learn what your peers think about WhiteSource. Get advice and tips from experienced pros sharing their opinions. Updated: November 2021.
552,695 professionals have used our research since 2012.
reviewer1257792
Co Founder at a consumer goods company with 11-50 employees
Real User
Top 10
Provides full visibility and gives us peace of mind working with open-source libraries

Pros and Cons

  • "It gives us full visibility into what we're using, what needs to be updated, and what's vulnerable, which helps us make better decisions."
  • "WhiteSource Prioritize should be expanded to cover more than Java and JavaScript."

What is our primary use case?

We needed a tool to ensure that we are not using vulnerable libraries or open-source libraries with a copyleft license. We integrated WhiteSource with our repositories and CI server and set up automated policies to reject copyleft licensed libraries because our legal department doesn't allow them. We also have it open Jira issues automatically when a vulnerable library is detected and assign it to an engineer so we can shorten our response time to vulnerabilities detected in our applications. It integrates nicely with our existing workflow.

How has it helped my organization?

The best thing is that it changed the mindset of our developers. They are now more aware and proactive when it comes to the security risks in open source vulnerabilities and the need to update packages from time to time.

It gives us full visibility into what we're using, what needs to be updated, and what's vulnerable, which helps us make better decisions.

The WhiteSource prioritization feature provides us with the greatest value as it has cut down the number of security alerts by about 90%. It is only relevant for Java and JS for now, but we understand more is yet to come. This has saved us a lot of time.

What is most valuable?

WhiteSource is very accurate and covers all of our languages (including C++).

WhiteSource Prioritize is amazing. If we are using a vulnerable library, it shows us if we are actually using the vulnerable method or not. This saves us a lot of time that we can instead invest in other projects.

It also does a great job of automating many activities we used to do manually. Now the system does it for us and it generates a great security dashboard that shows us whether our remediation velocity is improving or not.

What needs improvement?

WhiteSource Prioritize should be expanded to cover more than Java and JavaScript.
We are currently using WhiteSource Prioritize for Java and it cuts our vulnerability alerts by almost 90%. However, Prioritize doesn't cover python or other languages at this point and our developers are required to deal with many open source security alerts. The problem is that now our developers are aware that most open source security alerts are not impacting the security of their applications and it's harder to get their cooperation. We are waiting for WhiteSource to announce support ifor Python and other languages.

For how long have I used the solution?

We have been using WhiteSource for almost a year.

What do I think about the stability of the solution?

From my experience, WhiteSource is pretty solid.

How are customer service and technical support?

We had a problem with a new library that their engine didn't process. I wrote them an email and got a response within an hour. Two days later they added it to their system.

They provide accurate results and our customer success manager is great.

No complaints so far.

Which other solutions did I evaluate?

We tested Black Duck as well but detected quite a lot of false positives.

What other advice do I have?

The good thing is that their product just keeps getting better. They are very attentive to their customers.

All in all, if you care about security, this product is a must. We all love open source, but I was always afraid of the headache in handling all the licensing/updates/vulnerabilities. The peace of mind we have now is a total game-changer.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Alon Michaeli
Founder & CEO at Data+
Real User
Top 10
Good reporting and trace analysis allows us to find and solve open-source concerns quickly

Pros and Cons

  • "Our dev team uses the fix suggestions feature to quickly find the best path for remediation."
  • "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."

What is our primary use case?

We use WhiteSource mainly to:

  1. Detect and automate vulnerability remediation. We started to research solutions since our dev teams are unable to meet sprint deadlines and keep track of product security. Most of our code scans are automated and integrated within our pipeline, which integrates with our CI server. With some, we run them manually using an agent. We recently started using the repository integration with Github, too, pre-build.
  2. License reporting and attribution reports. We use attribution reports and due diligence reports to asses risks associated with open-source licenses.

How has it helped my organization?

WhiteSource is very easy to run and use. It reduced significantly the time our developers used to spend on issues in open-source libraries. We used a free tool before and the number of alerts was too high to handle.

We recently implemented WhiteSource on our Github account.

It provides our developers with better visibility into open source libraries within their code environment, which helps the company in ensuring dev adoption.

When it comes to open-source licenses, it really simplified reporting as it provides an inventory list in a simple report. Before WhiteSource it was almost impossible, mostly due to transitive dependencies.

What is most valuable?

The most valuable features for us are:

  1. Fix suggestions. Our dev team uses the fix suggestions feature to quickly find the best path for remediation. Before that you would have to research online for fixes, and most of the time it’s not that straightforward.
  2. Trace analysis. Trace analysis enables our team to get the fix, including a clear path to the vulnerable method. This saves quite some time.
  3. Open-source inventory reports. These reports are easy to manage and provide a clear view of our open-source assets. There’s also an option to create policies around that.

What needs improvement?

The changes that we would like to see are mostly usability issues.

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 UI is also too crowded. I believe that less information, or a different data summary, can be more readable. I know this is something they’re currently working on, but not sure where it stands. 

Reporting could be easier, as it does not export filtered-down lists. It would be really valuable to add the ability to customize options in the reports.

For how long have I used the solution?

We have been using WhiteSource for one and a half years.

What do I think about the stability of the solution?

Stable.

What do I think about the scalability of the solution?

Didn't have any problems related to scale so far.

Which solution did I use previously and why did I switch?

No

What was our ROI?

I can easily generate reports and get a quick overview of my status.

Which other solutions did I evaluate?

Yes, Snyk

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
reviewer1255491
VP R&D at a tech services company with 11-50 employees
Real User
Top 20
Easy open-source vulnerability checking has streamlined our software security process

Pros and Cons

  • "For us, the most valuable tool was open-source licensing analysis."
  • "If anything, I would spend more time making this more user-friendly, better documenting the CLI, and adding more examples to help expand the current documentation."

What is our primary use case?

We use WhiteSource to monitor our open-source usage. Specifically to avoid legal issues with open-source licensing, which may deter potential buyers or investors. Additionally, we analysed the code for security vulnerabilities.

We found the effective vulnerabilities report very useful since it lowered the number of actual defects found in the product and saved us a lot of work. Our environment is made of micro-services running in Kubernetes using NodeJS and Typescript for the backend, and AngularJS for the frontend. We use MongoDB, Redis, RabbitMQ, and ELK. 

How has it helped my organization?

WhiteSource allowed us to minimize our exposure to open-source vulnerabilities with ease. Aside from identifying the out-dated or compromised packages really easily, it allows us to actually see which vulnerabilities are effectively relevant for us. In this case, it saved us *A LOT* of refactors and redesigns of code, which would have been considered vulnerable otherwise.

We integrated WhiteSource into our build system to ensure we keep our code secure and don't introduce new problems as we go. This allows us to have more predictability into the work process as security now becomes a constant work-in-progress instead of a major bulk of work every now and then.

What is most valuable?

For us, the most valuable tool was open-source licensing analysis. Although we don't use it on a weekly basis, when we needed to produce a reliable analysis of our open-source licensing exposure, we found it very very effective. Considering the alternatives, which were to analyse manually, WhiteSource saved us a ton of work that we really needed to complete in a short time. It would have involved finding all the different packages, be them in package.json files or analyse the docker images, and then find their effective license, which in itself is not a simple task.

What needs improvement?

The agent usage was not as smooth as the online experience. It lacks in terms of documentation and the errors and warnings it produces are not always very clear. We were able to get it up and running in a short while by getting help from support, which was very approachable and reliable.

If anything, I would spend more time making this more user-friendly, better documenting the CLI, and adding more examples to help expand the current documentation.

I would also like to get better integration with Google Docs.

For how long have I used the solution?

We have been using WhiteSource for a few months.

Which solution did I use previously and why did I switch?

We did not use another solution prior to this one.

Which other solutions did I evaluate?

We did not evaluate other options.

What other advice do I have?

Overall, this is a great product.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
reviewer1264290
Project Manager at a wellness & fitness company with 11-50 employees
Real User
Top 20
Good license and copyright information reporting, and integrates with Jira for ticketing

Pros and Cons

  • "The reporting capability gives us the option to generate an open-source license report in a single click, which gets all copyright and license information, including dependencies."
  • "It would be nice to have a better way to realize its full potential and translate it within the UI or during onboarding."

What is our primary use case?

We started using WhiteSource mainly to scan dependencies and detect open-source licenses, copyright information, and vulnerabilities.

We’ve managed to establish an integration with our CICD pipelines and use pretty much all of the automation that is offered, including automated policies.

How has it helped my organization?

We were able to integrate the product naturally into our development process and it provided results really fast. You can easily use the unified agent and connect your CICD tools. It scans all of your source code quickly and it took us just a few minutes to run. The REST API is really good as well.

In the past, running similar tools or trying to get feedback on our open-source state was almost impossible.

Our primary goal was to get the license reports, but now we have a full end-to-end process that automates all license management, open-source license approval, rejection, ticket assignment, and more.

What is most valuable?

Our use case focuses on licenses, so the most valuable feature would probably be the license reports and policies, which is why we reached out in the first place.

The reporting capability gives us the option to generate an open-source license report in a single click, which gets all copyright and license information, including dependencies.

We use the Policies feature to approve or reject automatically open-source licenses, according to preset company policy.

With respect to ticketing, we use the JIRA integration to assign a problematic open-source library. It opens a ticket on our end and it is assigned automatically to the right owner. It saves a lot of hassle and simplifies the process internally.

What needs improvement?

It would be nice to have a better way to realize its full potential and translate it within the UI or during onboarding.

For how long have I used the solution?

We have been using WhiteSource for six months.

Which other solutions did I evaluate?

Given the different solutions in that space, WhiteSource was the best solution for our needs. We’ve found it was able to manage all dependencies, automate alerts, and provide us with easy and quick license reports, attribution and copyright information.

What other advice do I have?

I believe we’re still in a stage where we’re trying to gain all the benefits of the solution and understand what features can be maximized.

The product is simple on one hand as it's so easy to use, run and get insights from, but on the other hand, it offers so much that it’s hard to fully grasp all its capabilities.

I’m not sure I have the best knowledge so far to recommend features and capabilities since this is very new to us. Currently, we’re happy to have something that addresses our needs.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
SK
Principal Software Architect at a tech services company with 10,001+ employees
Real User
Top 20
Scalable and stable, with a broad range of features

Pros and Cons

  • "The solution boasts a broad range of features and covers much of what an ideal SCA tool should."
  • "The initial setup could be simplified."

What is our primary use case?

To my knowledge, we are using the latest, SaaS, version. 

What is most valuable?

The solution boasts a broad range of features and covers much of what an ideal SCA tool should. It covers the containers. One can create his teams and, should he encounter an issue, send an alert to the team's DL. 

I am quite happy with WhiteSource. It is very good and provides many things, including extensive reports involving vulnerabilities. 

What needs improvement?

I am not clear if WhiteSource provides on-premises service. I know that its competitors provide on-premises and SaaS-based services for the same licensing fee and model, but I am not sure if this applies to WhiteSource, as well. I believe it does not. 

It is preferable to use on-cloud services, although on-premises one should equally be an option, if I would prefer to not go for SaaS-based hosting. The licensing model should be the same for the different options. 

The initial setup could be simplified. 

For how long have I used the solution?

I have been using WhiteSource for more than a year. 

What do I think about the stability of the solution?

The solution is very stable. 

What do I think about the scalability of the solution?

It is a preferequisite that the solution is scalable, as it is SaaS-based. 

How are customer service and technical support?

I have not had experience with customer support. 

How was the initial setup?

The initial setup was of an intermediate complexity. It was neither complex, nor straightforward. It could have been easier. Understandably, it involved a certain amount of configuration. 

What's my experience with pricing, setup cost, and licensing?

I cannot comment on billing, as this was handled by other departments in my previous organization. 

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. 

Which other solutions did I evaluate?

The reason I logged into the IT Central Station web site is because I was looking for crisp documentation so that I may compare WhiteSource with Black Duck. I did not find what I was looking for. All I found was a conglomerate of user experiences, not the research reports I was searching for.

I am currently using both of these products.

What other advice do I have?

I rate Whitesource as an eight out of ten. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
ZD
Business Process Analyst at a financial services firm with 1,001-5,000 employees
Real User
Top 20
Unstable, caused build failures, and doubled or tripled the build time

Pros and Cons

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

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have used this solution for one year. 

What do I think about the stability of the solution?

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

How are customer service and technical support?

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.

How was the initial setup?

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.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.