AI-Generated Code License Auditor

Scan repos for licensing and copyright risks in LLM-generated code

Problem

Developers are asking: courts say LLM output can't be copyrighted, yet projects like Linux keep accepting AI-generated code—what does that mean for licenses? Individuals and small teams can't tell which commits contain AI-generated content, whether it conflicts with existing licenses, or what needs disclosure.

Solution

A CLI/CI tool scans git history and PRs, combining optional AI-generation markers, commit metadata, and code similarity detection to flag potential LLM-generated segments. It generates license compatibility reports and disclosure suggestions so teams can complete compliance records before merging.

Users

Open-source maintainers, small software companies using AI coding assistants, compliance-sensitive teams

MVP

Scan commits with AI-generation markers; detect license headers in changed files; generate a simple HTML report listing risky files; support GitHub Action PR comments; provide ignore-rule configuration

Revenue

Open-source core plus private-repo team subscription ($29–$99/mo) tiered by repo count; enterprise plan with custom policies and audit logs

Why now

AI coding tools are mainstream, so AI-generated code entering main branches is normal, yet there are no consensus tools for copyright and licensing. A lightweight checker can own the 'AI code compliance' mindshare early.