<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Due Diligence on remixware.com</title>
    <link>https://remixware.com/tags/due-diligence/</link>
    <description>Recent content in Due Diligence on remixware.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://remixware.com/tags/due-diligence/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Getting Ready for a Code Audit Before a Sale or a Big Customer</title>
      <link>https://remixware.com/getting-ready-for-a-code-audit-before-a-sale-or-a-big-customer/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://remixware.com/getting-ready-for-a-code-audit-before-a-sale-or-a-big-customer/</guid>
      <description>&lt;p&gt;Sooner or later someone outside the team asks what&amp;rsquo;s in your code. A company that wants to buy yours runs a scan as part of due diligence, or a large customer&amp;rsquo;s procurement team sends a questionnaire about open source. Both are asking the same thing: is there code in here that the company doesn&amp;rsquo;t have the right to ship the way it ships it?&lt;/p&gt;&#xA;&lt;p&gt;The worst time to find out is when their report lands. A GPL file in the core product turns into a price cut or a promise to rewrite it before closing. Running the same kind of check months earlier turns it into an ordinary task.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
