incident / Counsel and engineers assessing a potential copying claim
Investigating software copying: build a record others can examine
There is no universal percentage that proves software copying. A defensible investigation identifies the material being compared, the method, potential common sources, and the limits of the available record.
Organize the comparison
- Tie each input to a specific version, source, and preservation record.
- Separate observed similarities from common dependencies, generated code, standard patterns, and functional constraints.
- Retain reproducible steps and document observations that weaken the initial hypothesis.
Use an evidence matrix
For each issue, record the observation, supporting artifact, alternative explanation, missing evidence, and next authorized step. This helps counsel see both the support for a concern and the limits that should prevent overstatement.
The legal context
Protected expression and unprotected ideas or methods must be distinguished. Whether evidence establishes copying, actionable similarity, a defense, or a trade-secret issue is a legal assessment that technical tooling alone cannot make.
Source references
- U.S. Copyright Office: Computer Programs
- Supreme Court: Google LLC v. Oracle America (2021)
- 18 U.S.C. 1839: Trade secret definitions
General U.S.-focused information, subject to the facts and applicable jurisdiction. No legal advice, representation, or outcome is promised. Research checked 2026-10-10; review substantive facts with qualified counsel.