Code moves between projects all the time, and its licence travels with it whether anyone notices or not. A GPL function lands in an MIT project. A copyright line gets lost. An AI assistant reproduces a chunk of somebody’s library word for word. Usually nobody finds out until someone else checks: a customer’s legal team, a buyer doing due diligence, or the original author.
Remixware lets you check first. It scans a project for code copied from open source, including copies an AI assistant produced, works out each piece’s licence, and tells you what that licence asks of you: a notice to add, or a conflict to sort out.
The Pitch in Four Numbers
- 98% of planted copies of 100 tokens or more found, renamed and cut-down copies included, scanning against 14 real projects.
- 0 copies traced to the wrong project, out of 2,880.
- 0 false alarms in 99,198 lines from 9 projects that weren’t in the index.
- Apache 2.0, free, with the test logs published on GitHub.
How It Works
Remixware reads source code as tokens. Comments and layout are stripped out and names are normalised, so a copy with new formatting and renamed variables still matches. It keeps hashes from every file and looks for long shared runs between your code and the code it’s comparing against.
Each match is traced to a component. The licence comes from that component’s licence files, its manifest, and any notice at the top of the copied file. A combination table turns all of it into a status: conflict, no licence, review, attribution missing, or fine. The report puts each copied snippet beside its source.
You build the index yourself from whatever you want to compare against, like your dependencies or a project you suspect. For broad checks against public open source, Remixware uses the free SCANOSS service or reads results from SCANOSS’s own scanner. On its own it makes no network connections. With the --scanoss flag it sends fingerprints only, never your code or file names.
It reads more than twenty-five languages, from Go, C, Java and Python to Rust, Swift, Kotlin, PHP, SQL and shell.
The Dependency Gate
Releases 0.3 to 0.5 added a gate for pull requests. It compares the pull request’s lockfiles with main’s and fails the ones that bring in risky dependencies. It reads pnpm, Yarn and uv lockfiles, runs as a GitHub Action, checks Rust crates for build scripts, and reads licences carefully enough not to mistake a stronger obligation for a weaker one. The current version is 0.5.0.
The sample report for an online shop finds two licence conflicts, one copy with no licence and five copies missing attribution. The project’s case studies go through real code: CoyIM’s copied code and kept licence, the 18 libraries pip vendors, TorchServe’s extra package indexes and more.
Who It’s For
- Development teams who want to know what they’ve copied before they ship.
- Teams leaning on AI coding assistants, which sometimes reproduce open-source code verbatim.
- Companies heading into a sale or an investment round, where code provenance comes up in due diligence.
- Open-source maintainers who want to check how their code is being reused.
Limits
It can’t find every copy. The original has to be in an index or in SCANOSS’s knowledge base. It skips copies shorter than 50 tokens or 5 lines, because short code looks alike across projects. Some findings need a human, and it marks those for review. And it isn’t legal advice. It tells you where code came from and what its licence says, so you can decide what to do or when to call a lawyer.
The Four-Question Screening
Every project featured here gets the same four questions, the way you’d screen a startup idea.
1. Where is the money in it?
Remixware is free, and the site lists no paid offering. The market it sits in is real and paying: software composition analysis and open-source licence compliance is a business big vendors already sell into, mostly to large companies. The paid paths are a hosted version with history and dashboards, a curated index of popular open source so teams don’t build their own, audit reports for due diligence and M&A, and support for companies whose legal teams need a named vendor. AI-generated code makes the question more urgent every month.
2. What real problem does it solve?
Licence obligations hidden in copied code. Dependency scanners see the packages you declare. They don’t see the function someone pasted in three years ago, or the block an AI assistant wrote that happens to match a GPL library. Those are the copies that surprise people at the worst moment.
3. The technology in plain words
Think of a plagiarism checker for code. It ignores the spacing and the variable names and looks at the shape of what’s written, so a paraphrased copy still gets caught. Then it looks up the original’s terms of use and tells you whether you owe a credit line, have a real conflict, or are fine.
4. Moat and differentiation
The big compliance vendors are large platforms with large prices. Remixware is a free command-line tool that runs locally and sends nothing anywhere by default, with published accuracy numbers: 98% found, zero wrong attributions, zero false alarms on the test set. That’s a credible way into teams too small for the big vendors. The moat that can grow is the accuracy record, the licence combination logic, and the quality of the index it compares against.
Why It Matters
AI assistants are writing a growing share of code, and some of what they write comes from somewhere. Nobody wants to discover in due diligence that their product includes a copied library under terms they never met. A fast, private check before shipping is cheap insurance.
Follow the Project
Start with the quick start, read the guide to what open-source licences ask of you, see the sample reports, or get the code from the Remixware repository on GitHub. Remixware is listed with the other open-source projects on SoftDevStudio.com, and more featured projects are in the Projects section.