Name: RCF Protocol
Rating: 5.0 (1 reviews)

You want security researchers to audit your code, but not AI systems to train on it. Traditional licenses (MIT, Apache, GPL) don't address this gap.

Because MIT and Apache never protected your logic — only your text.

Your code stays exactly as it is — you're just adding inline markers and generating an audit file. No forking your repo, no weird build steps, no lock-in.

The DMCA §1202 angle is the part that actually surprised me. Machine-readable copyright markers have real legal teeth — stripping them isn't a gray area. That's a smarter legal hook than anything I've seen in open-source licensing before.

I've been shipping open-source libraries for a few years and the AI scraping problem has been in the back of my mind for a while. When I found RCF Protocol I was skeptical — most "IP protection" tools are either pure legal theater or too invasive to actually integrate into a real codebase.

Tried rcf-cli on one of my repos in about 15 minutes.

The workflow is straightforward: you annotate the blocks you care about with [RCF:PROTECTED], run rcf-cli scan, and get back a signed RCF-AUDIT-REPORT.json with SHA-256 hashes of every protected block. The rcf-guardian GitHub Action then watches every PR and flags any tampering automatically.

RCF Protocol

Protect code from AI training, keep it visible

Protect code from AI training, keep it visible

RCF Protocol Reviews

The community submitted 1 review to tell us what they like about RCF Protocol, what RCF Protocol can do better, and more.

What's great

What needs improvement

vs Alternatives