Can an employment NDA restrict my right to contribute to open source projects on my own time?
Can an employment NDA stop you from contributing to open source? Learn how IP assignment clauses work and how to protect your side projects with TermScore.
Can an employment NDA restrict your open source contributions?
Yes, an employment NDA or Intellectual Property (IP) assignment agreement can effectively restrict your right to contribute to open source projects. Even if you work on your own time, broad "work-for-hire" clauses often claim ownership of any code developed during your employment, potentially forcing you to hand over your personal projects to your employer.
Key takeaway: Never assume that "working on my own time" provides a legal shield. If your contract is poorly drafted, your employer may legally own the copyright to your open source contributions.
Understanding the Mechanics of IP Assignment
Most employment contracts contain an "Inventions Assignment" clause. This is distinct from an NDA, which protects trade secrets. An assignment clause dictates who owns the output of your labor. If the language is overly broad, it may capture any software you write, even if it is unrelated to your job description.
The "Scope of Employment" Trap
Courts generally look at whether the invention relates to the employer's business. However, "business" is often defined broadly in contracts to include any research or development the company is currently pursuing or might pursue in the future. If you contribute to a project that even tangentially touches your employer's tech stack, you are at risk.
- Broad Clauses: Claim ownership of anything created during the term of employment.
- Narrow Clauses: Limited to inventions that relate directly to the employer's current products or services.
- Equipment Clauses: Claim ownership of anything created using company-provided hardware or software.
Action Item: Review your contract for the definition of "Inventions" or "Developments." If it does not explicitly exclude personal projects, you are potentially exposed.
Jurisdictional Protections: State-Specific Laws
Some states provide statutory protections that override overly aggressive employment contracts. These laws generally prevent employers from claiming ownership of inventions created entirely on your own time without using company resources.
| State | Key Protection |
|---|---|
| California | Labor Code 2870 protects inventions developed on your own time without company equipment. |
| Washington | RCW 49.44.140 limits employer claims to inventions related to the employer's business. |
| Illinois | Employee Patent Act protects inventions developed on personal time without company resources. |
Action Item: Check if your employment contract includes a "Notice" clause stating that these state laws apply. If you live in a protected state, ensure your contract acknowledges these rights.
How to Protect Your Open Source Work
If you are a frequent contributor to open source, you must take proactive steps to ensure your contributions remain yours.
- Negotiate an IP Exclusion List: Before signing, provide a list of existing personal projects to be excluded from the agreement.
- Request an Open Source Policy: Ask if the company has a formal policy for open source contributions. Many tech companies have an internal approval process that grants a blanket waiver for specific projects.
- Use Personal Hardware: Never use company-issued laptops, cloud accounts, or software licenses for your personal open source work.
- Separate Your Identities: Use a personal email address and a separate GitHub account for your side projects.
Key takeaway: If you are in a high-stakes role, request an "IP carve-out" addendum. This is a simple document that explicitly lists your personal projects and confirms the company has no claim to them.
The Risk of "Shadow" Ownership
If you contribute to a project and your employer later claims ownership, the legal consequences are severe. They could force you to remove the code, demand you assign the copyright to them, or even terminate your employment for breach of contract. Furthermore, if you contribute to a project under an open source license (like MIT or GPL), you may have inadvertently licensed your employer's IP to the public, creating a massive legal liability for the company.
How TermScore Can Help
Analyzing complex legal language for IP "gotchas" is difficult without a legal background. TermScore uses AI to scan your employment agreements, identifying broad assignment clauses and hidden risks that could threaten your personal projects. By highlighting these specific sections, TermScore empowers you to negotiate better terms or seek professional legal counsel before you sign. Upload your contract to TermScore today to see exactly what you are agreeing to.
Check a suspicious clause
Paste a sentence or clause from your employment & nda to get an immediate statutory risk audit.
TermScore Legal Intelligence Group
Audited for 2026 StandardsResearched 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.
Get the contract red-flag checklist
Join landlords and freelancers getting clause breakdowns and benchmark data. No spam.
Keep reading
Employment & NDA
Can an employment NDA legally prohibit me from contributing to open source projects on my own time?
Employment & NDA
Does an employment NDA cover personal side projects created on my own time without company equipment?
Employment & NDA
Can an employer enforce an NDA to claim ownership of side projects built on your own time?
Employment & NDA
Does an employment NDA restrict listing specific software frameworks on my resume?
Employment & NDA
Can an employment NDA restrict my participation in online technical communities or hackathons?
Employment & NDA
Can an employment NDA legally restrict discussing technical project methodologies in job interviews?