{"id":25807,"date":"2014-09-04T23:40:19","date_gmt":"2014-09-05T03:40:19","guid":{"rendered":"http:\/\/www.opensource.im\/?p=25807"},"modified":"2014-09-04T23:40:19","modified_gmt":"2014-09-05T03:40:19","slug":"ma-due-diligence-open-source-report-and-license-analysis-service-now-offered-by-whitesource-software","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/open-source-software\/ma-due-diligence-open-source-report-and-license-analysis-service-now-offered-by-whitesource-software.php","title":{"rendered":"M&#038;A Due Diligence: Open Source Report and License Analysis Service Now Offered by WhiteSource Software"},"content":{"rendered":"<p><p>    Woodbury, NY (PRWEB) September 04, 2014  <\/p>\n<p>    Open source software components, while free to use, have a    license attached to them. The license lists the requirements    that the company using the open source software needs to meet.    Certain licenses may impose restrictions on the intellectual    property of the software products that use them. Also, failing    to meet license requirements could make the use of the open    source components illegal.  <\/p>\n<p>    Therefore, investigating which open source components are    included in a software product and how they are used is a    standard part of every M&A due diligence process.  <\/p>\n<p>    In addition to M&A, open source due diligence is standard    in OEM deals, where the licensor is often required to indemnify    the licensee. Increasingly, we see software buyers insisting on    due diligence because they are concerned that legal action    against a vendor will affect their operation.  <\/p>\n<p>    While open source due diligence has always been a standard    requirement for most transactions, the growing percentage of    open source components in commercial software means that manual    due diligence or the use of software scanners is no longer an    option.  <\/p>\n<p>    Ron Rymon, a serial entrepreneur and active chairman of    WhiteSource software, was involved in two open source due    diligence processes:  <\/p>\n<p>    I was involved in two M&A transactions  and the open    source due diligence process in each transaction was completely    different. When negotiating the sale of the first company, we    had to work very hard to create a report of the open source    components that we used and their licenses. We spent a few man    weeks including some very long nights working on the open    source report, while negotiating the deal during the day. It    was very hard. This is why we started WhiteSource says Rymon.  <\/p>\n<p>    WhiteSource creates a full open source report, including risk    and compliance analysis, in one click. So when I sold the    second company, we were able to produce the report in minutes.  <\/p>\n<p>    WhiteSource now offers an Open Source Due Diligence package,    aiming at providing a quick and cost-effective answer to the    need of producing an open source analysis for an M&A,    private equity, OEM and software purchasing deals. To contact    WhiteSource here.  <\/p>\n<p>    Want to hear more about Ron Rymons M&A experience and    about the WhiteSource solution?  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>More:<br \/>\n<a target=\"_blank\" href=\"http:\/\/www.prweb.com\/releases\/2014\/09\/prweb12143762.htm\/RK=0\/RS=n7RuRCZEW_E8Ou0sZGarvMs3ZYQ-\" title=\"M&A Due Diligence: Open Source Report and License Analysis Service Now Offered by WhiteSource Software\">M&A Due Diligence: Open Source Report and License Analysis Service Now Offered by WhiteSource Software<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Woodbury, NY (PRWEB) September 04, 2014 Open source software components, while free to use, have a license attached to them. The license lists the requirements that the company using the open source software needs to meet. Certain licenses may impose restrictions on the intellectual property of the software products that use them. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-25807","post","type-post","status-publish","format-standard","hentry","category-open-source-software"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/25807"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=25807"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/25807\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=25807"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=25807"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=25807"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}