GitHub as prior art — when open source blocks a patent
Short answer: Public repositories, packages, and gists can destroy novelty (§102) and feed obviousness combinations (§103). If your “invention” already shipped in a popular repo, a patent application is usually the wrong spend.
Software inventors search patents and miss GitHub. Examiners and competitors do not. A README, MIT-licensed library, or Stack Overflow–adjacent snippet published before your filing date can anticipate your claims — including code you never saw if it was publicly available.
What counts as public prior art for code
- Public GitHub / GitLab / Bitbucket repos (even if unstarred)
- npm, PyPI, crates.io, and other package registries
- Docs sites, changelogs, and RFCs describing the mechanism
- Your own early commits and marketing posts (self-disclosure)
AI coding tools raise the risk
Copilot, Cursor, and ChatGPT often surface patterns already common upstream. That does not prove your code is copied — but it means the prior-art neighborhood is crowded. Score the inventive module and review overlap before you file. Tool guide: patent GitHub Copilot code.
How to search without becoming a librarian
- Search for the mechanism (conflict-free sync, attestation flow), not the brand name
- Check patents and open-source neighbors
- Run Patent PreCheck for a free prior-art teaser against a 1,500,000+ corpus
- Upgrade to Interactive Code Review for deep overlap narrative before counsel hours
If you find close art
Narrow claims to what is truly different, improve the technical story for Alice, or choose trade secret if disclosure would not help. Related: prior art search for code.