Why does shipping AI-written code leave no record of which model wrote it?
機会
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
重要な理由
AI authorship provenance is the SBOM gap that will define the next decade of software supply-chain audits and incident response.
機会をどう評価するか
Opportunity Scoreは測定値ではなく、私自身の見解です。どれほど痛みを伴うか、どれほど頻繁に影響を与えるか、そして今日時点で解決策がいかに少ないか。スコアが高いほど、構築する価値が高いと私は考えています。
それが現れたときにどれほどの痛みをもたらすか。
実際にどれほど頻繁に人々がそれに直面するか。
今日時点で、それに対する優れたツールがいかに少ないか。