Can my employer legally restrict me from contributing to open source projects on my own time via an NDA?

Can employers restrict open source contributions via NDAs? Generally, no, but IP assignment clauses matter. Use TermScore to analyze your contract today.

November 7, 2026TermScore Legal Intelligence GroupStatutory & Corpus Verified678 words

Can my employer legally restrict me from contributing to open source projects?

An NDA (Non-Disclosure Agreement) is designed to protect trade secrets, not to restrict your personal labor. However, employers often bundle restrictive 'Invention Assignment' clauses into employment contracts. While an NDA cannot legally stop you from coding, an overly broad IP assignment clause can grant your employer ownership of your open source contributions, effectively making it impossible to contribute legally.

The Difference Between NDAs and Invention Assignment Clauses

It is critical to distinguish between the two legal instruments often found in your onboarding packet:

  • NDAs (Non-Disclosure Agreements): These prohibit you from sharing proprietary company data, code, or trade secrets. They do not prevent you from writing your own code, provided you do not use company assets.
  • Invention Assignment Agreements: These state that any intellectual property (IP) you create during your employment belongs to the company. If this clause is not limited to 'work-related' tasks, it may encompass everything you write, including open source contributions.

Key takeaway: If your contract claims ownership of 'all inventions conceived during the term of employment,' you are at high risk. Always look for language that excludes work done on your own time without company resources.

Action Item: Search your contract for the term 'Invention Assignment' or 'Proprietary Information.' If the scope is not explicitly limited to company business, you need a carve-out.

Jurisdictional Protections: The 'Employee Invention' Statutes

Several U.S. states have enacted laws that limit the reach of invention assignment agreements. These laws generally protect your right to work on personal projects if you meet specific criteria.

StateKey Protection StatutePrimary Requirement
CaliforniaLabor Code Section 2870No company equipment/time used; not related to company business.
WashingtonRCW 49.44.140Developed entirely on own time; no company trade secrets used.
IllinoisEmployee Patent ActNo company equipment/time; relates to company business or R&D.
New JerseyN.J.S.A. 34:1B-265No company resources; not related to company's actual/anticipated business.

If you live in a state without these protections, your contract terms are governed by common law, which is often much more favorable to the employer. In these jurisdictions, the 'scope of employment' is interpreted broadly.

Action Item: Check if your state has an 'Employee Invention' statute. If it does, your contract cannot override these statutory rights.

Three Red Flags in Your Employment Contract

When reviewing your contract for open source compatibility, watch for these specific red flags:

  • 'Any and all' language: Clauses that claim ownership of 'any and all inventions' without a carve-out for personal projects.
  • Broad definitions of 'Company Business': If the definition of company business is vague, the employer can argue that your open source project competes with their future interests.
  • Equipment clauses: Language that claims ownership of any IP created using 'any company-provided equipment,' including laptops or cloud accounts.

How to Secure Permission to Contribute

If your contract is restrictive, you are not necessarily barred from contributing. You can negotiate a 'Side Project Carve-out' or a formal permission letter.

  1. Audit your project: Ensure your open source work is entirely unrelated to your employer's core product or service.
  2. Use personal hardware: Never use a company-issued laptop, VPN, or cloud account for your open source contributions.
  3. Request a written waiver: Ask your manager or HR for a simple email confirmation stating that the company waives its rights to your specific open source project.
  4. Check the license: Ensure your project uses a standard license (like MIT or Apache 2.0) that does not inadvertently grant your employer rights to your code.

Key takeaway: Never rely on verbal permission. If it isn't in writing, it does not exist in the eyes of a court.

Action Item: Draft a simple 'Open Source Contribution Agreement' template and ask your manager to sign it. Most tech-forward companies are happy to support open source if it doesn't conflict with their IP.

The Role of TermScore in Contract Analysis

Navigating the legalese of employment contracts is complex, and missing a single clause can put your personal projects at risk. TermScore uses advanced AI to instantly scan your employment agreements, identifying restrictive IP assignment clauses and highlighting potential conflicts with your open source contributions. By providing a clear, plain-English breakdown of your rights and obligations, TermScore helps you understand exactly what you are signing before you commit, ensuring your personal work remains yours.

Instant Clause Diagnostic

Check a suspicious clause

Paste a sentence or clause from your employment & nda to get an immediate statutory risk audit.

0/3000
§

TermScore Legal Intelligence Group

Audited for 2026 Standards

Researched and cross-referenced against statutory codes, judicial rulings, and TermScore's proprietary Corpus of 100,000+ analyzed contracts. Our intelligence unit continuously audits contract enforceability and predatory clause variance across all 50 US jurisdictions.

Methodology: Empirical Corpus + Statutory CodeEditorial Standards & Methodology →

Get the contract red-flag checklist

Join landlords and freelancers getting clause breakdowns and benchmark data. No spam.

Keep reading

Don't guess. Get your TermScore.

Upload your lease, employment contract, or agreement and let our AI flag every risk in seconds.

Score my document free