Attribution Ledger for AI Outputs
A browser and IDE extension that flags code snippets generated by an AI assistant and tries to identify which public packages and projects most likely contributed to that snippet, so developers can cite or avoid the source knowingly.
Working software engineers who use AI coding assistants daily and care about license hygiene
- Inline annotations that highlight a generated snippet and link to the top candidate open source sources it resembles
- A 'would this snippet be a derivative work?' quick check based on similarity and the upstream license
- A citation generator that drops proper attribution into the PR when you decide to keep the snippet
- A weekly digest showing which packages your AI assistant has been leaning on, so you know where to contribute back
Merlescu's piece crystallized the worry that 'the reasoning around the code' is what models strip away; an attribution layer is a concrete response that fits how developers actually work.
Multiple sources confirm 73% of developers use AI assistants daily and 80%+ of new GitHub devs use them in week one; the active Doe v. GitHub copyright lawsuit and M&A due-diligence concerns create acute enterprise pain.The AI Code Tracking Revolution: How to Automatically Identify AI Generated Code ↗GitHub Copilot Lawsuit Status 2026 ↗
The AI code provenance/attribution space is already crowded with direct competitors — LineageLens (Plus $12/dev/mo), TraceAI, Code Provenance by Qodana, codeprov, git-ai-project/git-ai, and LineageLens Base all address AI-generated code tracking inside VS Code/JetBrains; only the narrower 'identify contributing public packages' angle remains differentiated.LineageLens — Track AI-Generated Code ↗TraceAI - Code Attribution Tracker - Visual Studio Marketplace ↗Code Provenance by Qodana - JetBrains Marketplace ↗
LineageLens validates paid willingness-to-pay at $12/developer/month for Plus, with Max tier contact-sales for enterprise compliance; but Base and Lite tiers are free and Core extension on the open-source side is MIT-licensed, putting downward pressure on capture.LineageLens pricing tiers ↗AI-Generated Code Attribution: How to Track in Pull Requests ↗
Depends on whether attribution becomes a legal or cultural norm; somewhat uncertain.
A local browser/IDE extension tracking AI insertions is demonstrably buildable — several shipped extensions prove it; however, the distinctive 'identify which public package contributed to a snippet' step requires semantic/fuzzy matching against open-source corpora, which is hard, error-prone, and why most competitors stop at AI-vs-human attribution rather than source-package tracing.codeprov — Code Provenance Guard ↗LineageLens Base - Visual Studio Marketplace ↗