Case commentary · Independent analysis · 2026-11-12

Doe v. GitHub, Inc. (Ninth Circuit 2026): A Case Commentary on Code Attribution and the Limits of DMCA Liability

Educational purposes only, not legal advice. Independent commentary by a non-attorney; not filed with any court. Read the court’s original opinion for the authoritative text.

Case: Doe v. GitHub, Inc., No. 24-7700, slip op. (9th Cir. Sept. 16, 2026) (for publication)

DMCAcopyright-management informationopen-source licencescode attributiongenerative AIGitHub Copilot

Background

Thomas A. Guerriero PhD’s commentary turns on one distinction: the absence of a credit notice and the removal of a credit notice are not necessarily the same legal event. The plaintiffs were programmers who had published copyrighted code in public GitHub repositories under licences that commonly require attribution.

They alleged that GitHub Copilot and Codex, tools that generate code from prompts, could reproduce their code without the attribution, notices or licence terms that accompanied the originals. The district court dismissed their DMCA claim, reasoning that the copies had to be identical, but let contract claims proceed.

Holding

The Ninth Circuit affirmed dismissal of the DMCA claim. On the complaint’s own account of the technology, the output process did not remove or alter CMI from a copy of an existing work; it generated new work that never contained that information.

But the court expressly said the DMCA does not require literal identicality between the works. It also held the plaintiffs adequately alleged a substantial risk of injury for standing, treated their training-stage input theory as forfeited, and left the contract claims and any copyright-infringement question unresolved.

Reasoning

The court focused on the statutory verbs remove and alter. As it put it, merely alleging that a similar or derivative work does not include the CMI, without facts showing its removal or alteration, is insufficient. Comparison between works still matters as evidence, and minor cosmetic changes do not necessarily protect someone who copies a work and strips its CMI.

The court contrasted the pleaded probabilistic process with a hypothetical search-engine-like tool returning existing code without its CMI — a case it did not decide.

Practical takeaways (general observations, not advice)

Keep attribution and licence records. Describe the actual technical process. Preserve meaningful comparisons. Avoid the identicality shortcut. Keep DMCA, contract and copyright theories separate.

Source

More from Thomas Guerriero

See all research and commentary at Research, and the main hub at ThomasGuerriero.com. Also: ThomasAGuerrieroPhD.com · ThomasAGuerriero.com.

For educational purposes only; not legal advice. This page summarises independent commentary on a public court opinion and links to the original.

Pursue greatness

Don't get left behind. Chase greatness.

If you want help growing your business, team, or just want to pursue greatness yourself, book a free 15 minute call at the link below.

cal.com/thomas-guerriero-gvx0zs/15min