<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Code Provenance on remixware.com</title>
    <link>https://remixware.com/tags/code-provenance/</link>
    <description>Recent content in Code Provenance 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/code-provenance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Remixware Now Checks Your Code Against SCANOSS With One Flag</title>
      <link>https://remixware.com/remixware-now-checks-your-code-against-scanoss-with-one-flag/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://remixware.com/remixware-now-checks-your-code-against-scanoss-with-one-flag/</guid>
      <description>&lt;p&gt;An index only knows the code you put in it. For everything else, Remixware 0.1 read the results of SCANOSS&amp;rsquo;s scanner, which compares files with a large knowledge base of public open source. That meant installing a Python tool, running it, and handing its results file to Remixware.&lt;/p&gt;&#xA;&lt;p&gt;Remixware 0.2 asks the SCANOSS service itself. Add &lt;code&gt;--scanoss&lt;/code&gt; to a scan or a check:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;remixware check . --scanoss&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;img src=&#34;https://remixware.com/images/scanoss-direct.png&#34; alt=&#34;What remixware check &amp;ndash;scanoss sends for one file of the sample shop: the file goes as 3.go, with its MD5 checksum, its size and hashes of its text, while the code and the file&amp;rsquo;s name stay on your machine.&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>The First Remixware Release Finds Copied Open Source Code and the Licence That Came With It</title>
      <link>https://remixware.com/the-first-remixware-release-finds-copied-open-source-code-and-the-licence-that-came-with-it/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://remixware.com/the-first-remixware-release-finds-copied-open-source-code-and-the-licence-that-came-with-it/</guid>
      <description>&lt;p&gt;Code gets into a project from all over the place. Somebody pastes a function from a library they like, or an AI assistant writes a helper that looks a lot like one it saw in training. It works, the tests pass, and nobody writes down where it came from. The terms of the project it was taken from came along with it anyway, and they don&amp;rsquo;t go away when the code moves.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Wide Coverage With SCANOSS, Offline Checks With Remixware</title>
      <link>https://remixware.com/wide-coverage-with-scanoss-offline-checks-with-remixware/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://remixware.com/wide-coverage-with-scanoss-offline-checks-with-remixware/</guid>
      <description>&lt;p&gt;Remixware compares your code with code you index, and an index only knows what you put in it. That&amp;rsquo;s enough for the libraries in your own stack, which is where most copies come from. But a function can come from anywhere, such as a project you never installed or an old gist.&lt;/p&gt;&#xA;&lt;p&gt;For those, Remixware works with &lt;a href=&#34;https://www.scanoss.com&#34;&gt;SCANOSS&lt;/a&gt;, which keeps a large knowledge base of public open source that you can check files against for free. SCANOSS finds the matches. Remixware applies your policy to them, sorts them into the same statuses as its own findings, writes the notices, and gives you one report and one pass or fail.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
