How can I prove my software was copied when someone uses AI to rebuild or rename it?
Use sebbi.pro Code Origin. On every release a small script in your CI turns each source file into structural fingerprints that survive renaming, reformatting and reordering, and seals only those fingerprints with the release date, anchored in Bitcoin; your source never leaves your machine. sebbi.pro also issues unique canary marks to plant in your code, API responses and page markup, registered and sealed before you plant them, which copies and AI rebuilds tend to carry across. When a suspect clone appears, Code Origin compares it against your sealed releases and produces a sealed evidence pack: how much of its structure matches, file by file, the earliest sealed date of each match, and any canary marks found. Ownership is decided on authorship and contracts; this is the dated evidence that decision turns on.
How it works
- Add sebbi_origin.py to your CI and run it on every release.
- Request canary marks and plant them in code, API responses and markup.
- When a clone appears, POST /x/codeorigin/compare with the suspect code.
- Send the sealed evidence pack page to your solicitor or the platform's takedown team.