Does an employment NDA prevent me from contributing to open source projects on my personal time?

An employment NDA alone rarely prohibits open source contributions, but most employment contracts include an Invention Assignment Agreement that does. If your contract claims ownership of all work related to your employer's business, your personal projects could be legally owned by your company, regardless of when you wrote them.

Understanding the Difference: NDA vs. Invention Assignment

Employees often conflate NDAs with Invention Assignment Agreements. While an NDA restricts the disclosure of confidential information, an Invention Assignment Agreement dictates who owns the intellectual property (IP) you create. If you contribute to open source, you are creating IP. If that IP falls under the scope of your employment contract, you may be inadvertently signing away your rights to your own code.

Key Contractual Red Flags

• Broad Scope: Language that claims ownership of any work "related to the company's business or anticipated research."
• Resource Usage: Clauses that grant the company ownership if you use any company equipment, including laptops or software licenses.
• Time Constraints: Provisions that claim ownership of work created "during the term of employment," regardless of whether it was done on personal time.

Key takeaway: Always check your contract for an "Exclusion List" or "Prior Inventions" schedule. If you don't see one, your employer may claim ownership of everything you build while employed.

Action Item: Locate your original employment offer letter and the attached Proprietary Information and Inventions Agreement (PIIA). Highlight every clause mentioning "Inventions," "Works Made for Hire," or "Intellectual Property."

Jurisdictional Protections

Your location significantly impacts your rights. Some states have enacted laws that limit an employer's ability to claim ownership of employee inventions.

Even in these states, the protection is not absolute. If your project uses company trade secrets or proprietary code, the statutory protections will not shield you from a breach of contract claim.

How to Safely Contribute to Open Source

If you want to contribute to open source without risking your career, follow this systematic approach:

1. Audit your contract: Identify if your work is "related" to your employer's business.
2. Request a carve-out: If you have a specific project, ask your manager or HR for a written waiver or an amendment to your PIIA that explicitly excludes that project.
3. Use personal hardware: Never use company-issued laptops, cloud accounts, or software licenses for personal projects.
4. Maintain separation: Keep your personal GitHub account strictly separate from your work email and professional identity.

When to Seek Legal Counsel

You should consult an attorney if your employer refuses to sign a waiver and you are working on a project that is even tangentially related to your job. The cost of a legal consultation is significantly lower than the potential loss of your intellectual property or a lawsuit for breach of contract.

Key takeaway: Never assume that "personal time" is a legal shield. If the work is related to your employer's business, they may have a valid claim to your code.

Action Item: If you are starting a new project, document the date, time, and hardware used. Keep a "clean room" log to prove the project was developed independently of your employment duties.

The Role of AI in Contract Analysis

Manually reviewing complex employment agreements is prone to human error, often leading to missed clauses that could jeopardize your side projects. TermScore uses advanced AI to instantly scan your employment contracts, identifying restrictive IP assignment clauses and potential conflicts with your open source contributions. By providing a clear, plain-English breakdown of your obligations, TermScore empowers you to negotiate better terms or seek the necessary waivers before you commit your first line of code to a public repository.