OpenWork License Details: MIT and Fair Source License (FSL-1.1-MIT) Explained

OpenWork is licensed under a dual-license model: MIT License for the core codebase and Fair Source License (FSL-1.1-MIT) for the ee/ directory, with third-party dependencies retaining their original licenses.

OpenWork by different-ai uses a multi-license structure that balances open-source accessibility with commercial sustainability. Understanding these licensing details is essential for anyone using, modifying, or redistributing the codebase. This guide breaks down each license, its scope, and compliance requirements based on the actual source files in the repository.

Default MIT License for Core Code

The bulk of OpenWork falls under the permissive MIT License, defined in the root LICENSE file at the repository top level.

This license grants broad rights: use, copy, modify, merge, publish, distribute, sublicense, and sell copies of the software. The only requirement is retaining the original copyright and permission notice. The software is provided "as is" without warranty of any kind.

All files outside the ee/ directory and third-party components automatically fall under this default MIT License.

Fair Source License (FSL-1.1-MIT) for Enterprise Features

The /ee/LICENSE file introduces a Fair Source License (FSL-1.1-MIT) that governs all code within the ee/ directory.

This license resembles MIT with a critical addition: a "Competing Use" restriction. You cannot distribute the software in a commercial product that directly substitutes for OpenWork or any other product the licensor offers.

Permitted uses include:

• Internal tooling and infrastructure
• Non-commercial education and research
• Professional services offered to clients using the software

The FSL-1.1-MIT also includes a patent grant for permitted uses and automatic conversion to pure MIT after two years from the version date.

Third-Party Dependency Licenses

Dependencies listed in package.json and its lock files carry their original licenses (Apache 2.0, BSD-3, etc.). These licenses are preserved in node_modules and any accompanying NOTICE or LICENSE files within each package.

Package managers typically handle license attribution automatically, but redistributors should verify complete license coverage.

License Compliance When Redistributing

When packaging or redistributing OpenWork, include all three license layers:

1. Root MIT License — for non-ee code
2. /ee/LICENSE — Fair Source text for any ee/ files included
3. Dependency notices — original licenses for bundled third-party libraries

TypeScript Example: Adding License Headers to Built Bundles

// License header injection for distribution builds
import fs from 'fs';
import path from 'path';

// Extract MIT header from root LICENSE
const mitHeader = fs.readFileSync(
  path.resolve(__dirname, '../../LICENSE'),
  'utf8'
).split('\n').slice(0, 30).join('\n');

// Extract Fair Source header from ee/LICENSE
const fslHeader = fs.readFileSync(
  path.resolve(__dirname, '../../ee/LICENSE'),
  'utf8'
).split('\n').slice(0, 30).join('\n');

function prependHeader(filePath: string, isEE = false) {
  const header = isEE ? fslHeader : mitHeader;
  const content = fs.readFileSync(filePath, 'utf8');
  fs.writeFileSync(filePath, `${header}\n\n${content}`);
}

// Apply correct headers based on source origin
prependHeader('dist/main.js');               // MIT-licensed
prependHeader('dist/ee/feature.js', true);  // Fair Source-licensed

Bash Example: Packaging for Redistribution

# Complete packaging workflow with license compliance

git clone https://github.com/different-ai/openwork.git
cd openwork

pnpm install        # Records dependency licenses

pnpm run build      # Generates distribution

# Create archive with both license files

tar czf openwork-dist.tar.gz \
  LICENSE \
  ee/LICENSE \
  -C dist .

Key License Files in the Repository

File	Purpose	Direct Link
LICENSE	Default MIT license for core codebase	View LICENSE
ee/LICENSE	Fair Source License (FSL-1.1-MIT) for enterprise features	View ee/LICENSE
package.json	Dependency manifest with version information	View package.json
README.md	Project overview with licensing pointers	View README

Summary

• MIT License covers the majority of OpenWork code outside ee/, permitting virtually unrestricted use with attribution
• Fair Source License (FSL-1.1-MIT) restricts competing commercial use for ee/ directory code, converting to MIT after two years
• Third-party licenses remain intact for all dependencies, tracked via package.json and node_modules
• Include both LICENSE and ee/LICENSE when redistributing any portion of the codebase
• Use license headers and packaging scripts to ensure compliance in distribution builds

Frequently Asked Questions

Can I use OpenWork in a commercial SaaS product?

Yes, with boundaries. MIT-licensed code can be used freely. FSL-1.1-MIT code in ee/ cannot be used in a product that directly competes with OpenWork itself. Internal use and client services are permitted. After two years, FSL-1.1-MIT code converts to standard MIT.

What happens to the Fair Source restriction after two years?

FSL-1.1-MIT includes an automatic conversion clause. Two years after a version's release date, that version's license becomes pure MIT—dropping the competing use restriction entirely. This provides long-term open access while protecting early commercial viability.

Do I need to open-source my modifications to OpenWork?

No. Neither MIT nor FSL-1.1-MIT imposes copyleft requirements. You can modify and keep changes private, provided you retain license notices. The FSL-1.1-MIT only restricts distribution of competing products, not modification or internal use.

How do I identify which files fall under which license?

Check the file path: anything under ee/ uses FSL-1.1-MIT; everything else uses MIT. Third-party files in node_modules/ carry their own licenses as indicated in their respective LICENSE files and package.json metadata.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}