Can my employer claim ownership of my open-source contributions?

Yes, if your employment agreement includes an 'Invention Assignment' clause that covers all work created during your tenure, your employer may legally claim ownership of any open-source code you write, even on your own time, unless you negotiate an exclusion.

How do I protect my personal open-source projects?

Request a written 'Prior Inventions' disclosure, ensure you use separate hardware, avoid using company resources, and negotiate an 'IP Exclusion' addendum to your employment contract.

A TermScore is an AI-generated risk rating from 0 to 100 that evaluates the fairness and risk level of any legal document. A score of 86-100 means the contract is highly favorable, while 0-30 indicates dangerous terms you should walk away from.

What types of documents can TermScore analyze?

TermScore analyzes any legal document including freelance contracts, employment agreements, residential leases, NDAs, brand sponsorship deals, SaaS vendor agreements, and rental applications. Upload PDFs, Word documents, or images.

How much does TermScore cost?

TermScore offers a free plan with 3 scores per month. The Team plan is $15/month for 30 scores, and the Professional plan is $50/month for 500 scores with team collaboration features.

Is my document data secure?

Yes. Documents are processed in memory and analysis results are stored encrypted. TermScore never shares your document data with third parties and you can delete your data at any time from your dashboard.

Does a standard employment NDA prohibit the use of open-source libraries used during my tenure?

Q: Does a standard employment NDA prohibit the use of open-source libraries?

No, a standard NDA typically protects confidential information and trade secrets, not public open-source code. However, broader 'Invention Assignment' clauses often found in the same document may claim ownership of your contributions to those libraries if created during work hours.

Does a standard employment NDA prohibit the use of open-source libraries?

No, a standard Non-Disclosure Agreement (NDA) does not prohibit the use of open-source libraries. NDAs are designed to protect proprietary trade secrets and confidential business information. However, your employment contract likely contains an 'Invention Assignment' clause that can inadvertently claim ownership of your open-source contributions if they are developed using company time or resources.

The Distinction Between NDAs and Invention Assignments

It is critical to distinguish between the two most common clauses in tech employment contracts. An NDA focuses on secrecy, while an Invention Assignment focuses on ownership.

The NDA Component

An NDA restricts you from sharing your employer's internal codebases, API keys, or strategic roadmaps. Open-source libraries are, by definition, public. Therefore, using a library like React, Pandas, or TensorFlow does not violate an NDA because you are not disclosing secret information; you are utilizing public tools.

The Invention Assignment Component

This is where developers face legal risk. Most employment agreements state that any 'work product' created during your employment—or using company equipment—belongs to the employer. If you contribute to an open-source project while on the clock, the company could technically claim they own the copyright to your contribution.

Key takeaway: Always check your contract for an 'Invention Assignment' or 'Work for Hire' section. This is the clause that poses a risk to your open-source contributions, not the NDA itself.

Risk Factors for Open-Source Contributors

Employers generally do not care about your open-source contributions unless they intersect with the company's core business. However, you should evaluate your risk based on the following criteria:

Company Equipment: Using a company-issued laptop to push code to GitHub creates a strong presumption of employer ownership.
Time of Creation: Code written during standard business hours (e.g., 9:00 AM to 5:00 PM) is legally vulnerable.
Relevance to Business: If your open-source project competes with your employer’s product, the risk of litigation increases by over 80%.
Use of Proprietary Tools: Integrating company-specific APIs into an open-source library is a direct breach of most NDAs.

Comparison of Contractual Protections

Clause Type	Primary Purpose	Impact on Open Source
NDA	Confidentiality	Minimal; public code is not confidential.
Invention Assignment	Ownership	High; can claim your personal contributions.
Non-Compete	Market Restriction	Moderate; limits where you can contribute.
IP Exclusion	Carve-out	Positive; protects your personal projects.

How to Protect Your Personal Projects

If you are an active contributor to the open-source community, follow these steps to insulate yourself from potential legal claims:

Disclose Prior Inventions: Maintain a written list of all open-source projects you owned before starting your current role and provide this to HR upon hiring.
Use Personal Hardware: Never use company-issued laptops, servers, or cloud accounts for personal coding.
Separate Accounts: Ensure your GitHub/GitLab account is not linked to your corporate email address.
Negotiate an IP Exclusion: Ask for an addendum that explicitly excludes your specific open-source projects from the Invention Assignment clause.

Jurisdictional Nuances

Jurisdiction plays a massive role in how these clauses are enforced. For example, in California, Labor Code Section 2870 provides significant protection for employees, stating that an employer cannot claim ownership of inventions developed entirely on an employee's own time without using the employer's equipment or trade secrets. However, this protection does not apply if the invention relates directly to the employer's business or actual/anticipated research.

Key takeaway: Even in employee-friendly states like California, the 'related to the employer's business' exception is broad. Never assume you are safe without a formal IP exclusion agreement.

Actionable Steps for Developers

Before contributing to your next repository, perform a quick audit of your contract. If you find broad language regarding 'all intellectual property created during the term of employment,' you should consult with your manager or legal counsel to clarify your status. Most tech-forward companies are happy to sign a simple waiver for personal projects if they do not conflict with the company's commercial interests.

TermScore can automatically analyze your employment contract to identify high-risk Invention Assignment clauses and provide plain-English summaries of your obligations, helping you understand exactly what you can and cannot contribute to open-source projects without legal exposure.