Why does shipping AI-written code leave no record of which model wrote it?
Opportunity
AI assistants now author a significant and growing fraction of production code, but no artifact format records which model, version, or prompt produced a given function. When a vulnerability is traced to a pattern that a specific model generation reliably introduces, there is no way to query a codebase or package registry to find every function that shares the same origin. Software Bills of Materials standardized by SPDX and CycloneDX capture library dependencies, not authorship provenance of source code. The 2026 Cloudsmith supply-chain survey found 29 percent of respondents identify AI-generated package risk as their top open-source security concern, and three quarters of organizations treat SBOMs as static compliance artifacts rather than active governance instruments. The EU AI Act and the US Executive Order on AI both reference software supply-chain integrity but neither specifies w
Why it matters
AI authorship provenance is the SBOM gap that will define the next decade of software supply-chain audits and incident response.
How I score the opportunity
The Opportunity Score is my own read, not a measurement: how much it hurts, how often it bites, and how little exists to solve it today. Higher means I think it is more worth building.
How much pain it causes when it shows up.
How often people actually run into it.
How little good tooling exists for it today.
More problems worth solving
Why is the software we depend on most the worst to use?
TechWhy do I still own none of the data I generate?
TechWhy can I not get a receipt proving my data was actually deleted?
TechWhy can I not know if what is running matches what my SBOM declared?
TechWhy does every C2PA provenance chain break the moment content hits social media?
TechWhy can I not trace a production failure that crossed a message queue?