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

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

An NDA typically protects confidential information, but it is rarely the primary barrier to open-source contributions. The real legal threat lies in Invention Assignment Agreements, which often grant your employer ownership of everything you create during your employment, regardless of whether you used company resources.

Key takeaway: Do not confuse an NDA with an IP Assignment Agreement. An NDA prevents you from sharing secrets; an IP Assignment Agreement can legally strip you of the ownership of your personal code contributions.

Understanding the Legal Framework of IP Ownership

Most employment contracts for software engineers contain a broad "Invention Assignment" clause. These clauses are designed to ensure that the code you write for the company belongs to the company. However, poorly drafted clauses often capture "all inventions created during the term of employment," which can inadvertently include your weekend open-source projects.

The Scope of "Related to Business"

Courts generally look at whether your side project is "related to the employer's business." If you work for a database company and contribute to an open-source database project, your employer has a strong legal argument that they own your contributions. If you work for a fintech firm and contribute to a gardening app, the connection is much weaker.

• Direct Competition: Projects that compete with your employer's product are almost always prohibited.
• Company Resources: Using a company-issued laptop, VPN, or proprietary libraries is a "smoking gun" for employer ownership.
• Time and Effort: Working on projects during "company hours" (e.g., 9-to-5) creates a presumption of ownership.

State-Specific Protections for Employees

Several jurisdictions have enacted laws that limit the reach of broad invention assignment agreements. If you live in one of these states, your employer cannot force you to assign rights to inventions created on your own time, provided specific criteria are met.

Action Item: Check your contract for a "Section 2870" disclosure or similar language. If your state has these protections, ensure you formally disclose your side projects to your employer to trigger these legal safeguards.

Red Flags in Your Employment Contract

When reviewing your agreement, look for these specific red flags that indicate you may be restricted from open-source work:

• "All Inventions" Language: Phrases like "any and all ideas, concepts, or code developed during the term of employment" are excessively broad.
• Lack of Carve-outs: The absence of a "Prior Inventions" list where you can document your existing open-source work.
• Broad Definitions of Confidential Information: If the NDA defines "Confidential Information" to include "any work product," it may effectively block you from contributing to public repositories.

Key takeaway: If your contract lacks a carve-out for personal projects, you are technically in breach of contract every time you push code to a public repository. Always seek a written amendment or a "Side Letter" from your employer.

How to Secure Permission for Open-Source Contributions

If you find that your contract is restrictive, you do not necessarily need to quit. Many employers are willing to grant permission if you approach them professionally.

1. Audit your contributions: Identify the specific projects you want to contribute to.
2. Draft a formal request: Explain that the project is unrelated to the company's core business.
3. Offer a "No-Conflict" guarantee: Explicitly state that you will not use company hardware, proprietary code, or company time.
4. Get it in writing: An email from your manager or HR department is often sufficient to serve as a waiver.

Action Item: Create a "Prior Inventions" document today. List every open-source project you currently contribute to and provide it to your HR department to ensure these are excluded from your employment agreement.

The Role of TermScore in Contract Analysis

Navigating the intersection of employment law and intellectual property is complex. TermScore uses advanced AI to scan your employment agreements, identifying overly broad IP assignment clauses and restrictive covenants that could jeopardize your personal projects. By highlighting these risks before you sign, TermScore empowers you to negotiate better terms and protect your creative output. Upload your contract to TermScore today to see exactly where your rights stand.