yujunjun/claude-task-master
1
0
Fork 0
mirror of https://github.com/eyaltoledano/claude-task-master.git synced 2025-06-27 00:29:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add License (#45)

Browse Source
This commit is contained in:
Ralph Khreish 2025-03-31 17:09:31 +02:00 committed by GitHub
parent 6e6407f683
commit 757fd478d2
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
10 changed files with 358 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
.changeset/slick-women-relate.md Normal file
View File

@ -0,0 +1,5 @@
---
"task-master-ai": patch
---
Add license to repo

25
LICENSE Normal file
View File

@ -0,0 +1,25 @@
Task Master License
MIT License
Copyright (c) 2025 — Eyal Toledano, Ralph Khreish
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
"Commons Clause" License Condition v1.0
The Software is provided to you by the Licensor under the License (defined below), subject to the following condition:
Without limiting other conditions in the License, the grant of rights under the License will not include, and the License does not grant to you, the right to Sell the Software.
For purposes of the foregoing, "Sell" means practicing any or all of the rights granted to you under the License to provide the Software to third parties, for a fee or other consideration (including without limitation fees for hosting or consulting/support services related to the Software), as part of a product or service whose value derives, entirely or substantially, from the functionality of the Software. Any license notice or attribution required by the License must also include this Commons Clause License Condition notice.
Software: All Task Master associated files (including all files in the GitHub repository "claude-task-master" and in the npm package "task-master-ai").
License: MIT
Licensor: Eyal Toledano, Ralph Khreish

90
LICENSE.md Normal file
View File

@ -0,0 +1,90 @@
# Dual License
This project is licensed under two separate licenses:
1. [Business Source License 1.1](#business-source-license-11) (BSL 1.1) for commercial use of Task Master itself
2. [Apache License 2.0](#apache-license-20) for all other uses
## Business Source License 1.1
Terms: https://mariadb.com/bsl11/
Licensed Work: Task Master AI
Additional Use Grant: You may use Task Master AI to create and commercialize your own projects and products.
Change Date: 2025-03-30
Change License: None
The Licensed Work is subject to the Business Source License 1.1. If you are interested in using the Licensed Work in a way that competes directly with Task Master, please contact the licensors.
### Licensor
- Eyal Toledano (GitHub: @eyaltoledano)
- Ralph (GitHub: @Crunchyman-ralph)
### Commercial Use Restrictions
This license explicitly restricts certain commercial uses of Task Master AI to the Licensors listed above. Restricted commercial uses include:
1. Creating commercial products or services that directly compete with Task Master AI
2. Selling Task Master AI itself as a service
3. Offering Task Master AI's functionality as a commercial managed service
4. Reselling or redistributing Task Master AI for a fee
### Explicitly Permitted Uses
The following uses are explicitly allowed under this license:
1. Using Task Master AI to create and commercialize your own projects
2. Using Task Master AI in commercial environments for internal development
3. Building and selling products or services that were created using Task Master AI
4. Using Task Master AI for commercial development as long as you're not selling Task Master AI itself
### Additional Terms
1. The right to commercialize Task Master AI itself is exclusively reserved for the Licensors
2. No party may create commercial products that directly compete with Task Master AI without explicit written permission
3. Forks of this repository are subject to the same restrictions regarding direct competition
4. Contributors agree that their contributions will be subject to this same dual licensing structure
## Apache License 2.0
For all uses other than those restricted above. See [APACHE-LICENSE](./APACHE-LICENSE) for the full license text.
### Permitted Use Definition
You may use Task Master AI for any purpose, including commercial purposes, as long as you are not:
1. Creating a direct competitor to Task Master AI
2. Selling Task Master AI itself as a service
3. Redistributing Task Master AI for a fee
### Requirements for Use
1. You must include appropriate copyright notices
2. You must state significant changes made to the software
3. You must preserve all license notices
## Questions and Commercial Licensing
For questions about licensing or to inquire about commercial use that may compete with Task Master, please contact:
- Eyal Toledano (GitHub: @eyaltoledano)
- Ralph (GitHub: @Crunchyman-ralph)
## Examples
### ✅ Allowed Uses
- Using Task Master to create a commercial SaaS product
- Using Task Master in your company for development
- Creating and selling products that were built using Task Master
- Using Task Master to generate code for commercial projects
- Offering consulting services where you use Task Master
### ❌ Restricted Uses
- Creating a competing AI task management tool
- Selling access to Task Master as a service
- Creating a hosted version of Task Master
- Reselling Task Master's functionality

21
README.md
View File

@ -4,6 +4,25 @@
A task management system for AI-driven development with Claude, designed to work seamlessly with Cursor AI.
## Licensing
Task Master is licensed under the MIT License with Commons Clause. This means you can:
✅ **Allowed**:
- Use Task Master for any purpose (personal, commercial, academic)
- Modify the code
- Distribute copies
- Create and sell products built using Task Master
❌ **Not Allowed**:
- Sell Task Master itself
- Offer Task Master as a hosted service
- Create competing products based on Task Master
See the [LICENSE](LICENSE) file for the complete license text.
## Requirements
- Node.js 14.0.0 or higher
@ -385,7 +404,7 @@ task-master update-subtask --id=5.2 --prompt="Add rate limiting of 100 requests
task-master update-subtask --id=<parentId.subtaskId> --prompt="<prompt>" --research
```
Unlike the `update-task` command which replaces task information, the `update-subtask` command *appends* new information to the existing subtask details, marking it with a timestamp. This is useful for iteratively enhancing subtasks while preserving the original content.
Unlike the `update-task` command which replaces task information, the `update-subtask` command _appends_ new information to the existing subtask details, marking it with a timestamp. This is useful for iteratively enhancing subtasks while preserving the original content.
### Generate Task Files

15
bin/task-master.js
View File

@ -1,5 +1,20 @@
#!/usr/bin/env node
/**
* Task Master
* Copyright (c) 2025 Eyal Toledano, Ralph Khreish
*
* This software is licensed under the MIT License with Commons Clause.
* You may use this software for any purpose, including commercial applications,
* and modify and redistribute it freely, subject to the following restrictions:
*
* 1. You may not sell this software or offer it as a service.
* 2. The origin of this software must not be misrepresented.
* 3. Altered source versions must be plainly marked as such.
*
* For the full license text, see the LICENSE file in the root directory.
*/
/**
* Claude Task Master CLI
* Main entry point for globally installed package

15
index.js
View File

@ -1,5 +1,20 @@
#!/usr/bin/env node
/**
* Task Master
* Copyright (c) 2025 Eyal Toledano, Ralph Khreish
*
* This software is licensed under the MIT License with Commons Clause.
* You may use this software for any purpose, including commercial applications,
* and modify and redistribute it freely, subject to the following restrictions:
*
* 1. You may not sell this software or offer it as a service.
* 2. The origin of this software must not be misrepresented.
* 3. Altered source versions must be plainly marked as such.
*
* For the full license text, see the LICENSE file in the root directory.
*/
/**
* Claude Task Master
* A task management system for AI-driven development with Claude

2
package.json
View File

@ -34,7 +34,7 @@
"context"
],
"author": "Eyal Toledano",
"license": "MIT",
"license": "MIT WITH Commons-Clause",
"dependencies": {
"@anthropic-ai/sdk": "^0.39.0",
"@model-context-protocol/sdk": "^1.20.5",

15
scripts/init.js
View File

@ -1,5 +1,20 @@
#!/usr/bin/env node
/**
* Task Master
* Copyright (c) 2025 Eyal Toledano, Ralph Khreish
*
* This software is licensed under the MIT License with Commons Clause.
* You may use this software for any purpose, including commercial applications,
* and modify and redistribute it freely, subject to the following restrictions:
*
* 1. You may not sell this software or offer it as a service.
* 2. The origin of this software must not be misrepresented.
* 3. Altered source versions must be plainly marked as such.
*
* For the full license text, see the LICENSE file in the root directory.
*/
console.log('Starting task-master-ai...');
import fs from 'fs';

128
tasks/task_039.txt Normal file
View File

@ -0,0 +1,128 @@
# Task ID: 39
# Title: Update Project Licensing to Dual License Structure
# Status: done
# Dependencies: None
# Priority: high
# Description: Replace the current MIT license with a dual license structure that protects commercial rights for project owners while allowing non-commercial use under an open source license.
# Details:
This task requires implementing a comprehensive licensing update across the project:
1. Remove all instances of the MIT license from the codebase, including any MIT license files, headers in source files, and references in documentation.
2. Create a dual license structure with:
- Business Source License (BSL) 1.1 or similar for commercial use, explicitly stating that commercial rights are exclusively reserved for Ralph & Eyal
- Apache 2.0 for non-commercial use, allowing the community to use, modify, and distribute the code for non-commercial purposes
3. Update the license field in package.json to reflect the dual license structure (e.g., "BSL 1.1 / Apache 2.0")
4. Add a clear, concise explanation of the licensing terms in the README.md, including:
- A summary of what users can and cannot do with the code
- Who holds commercial rights
- How to obtain commercial use permission if needed
- Links to the full license texts
5. Create a detailed LICENSE.md file that includes:
- Full text of both licenses
- Clear delineation between commercial and non-commercial use
- Specific definitions of what constitutes commercial use
- Any additional terms or clarifications specific to this project
6. Create a CONTRIBUTING.md file that explicitly states:
- Contributors must agree that their contributions will be subject to the project's dual licensing
- Commercial rights for all contributions are assigned to Ralph & Eyal
- Guidelines for acceptable contributions
7. Ensure all source code files include appropriate license headers that reference the dual license structure.
# Test Strategy:
To verify correct implementation, perform the following checks:
1. File verification:
- Confirm the MIT license file has been removed
- Verify LICENSE.md exists and contains both BSL and Apache 2.0 license texts
- Confirm README.md includes the license section with clear explanation
- Verify CONTRIBUTING.md exists with proper contributor guidelines
- Check package.json for updated license field
2. Content verification:
- Review LICENSE.md to ensure it properly describes the dual license structure with clear terms
- Verify README.md license section is concise yet complete
- Check that commercial rights are explicitly reserved for Ralph & Eyal in all relevant documents
- Ensure CONTRIBUTING.md clearly explains the licensing implications for contributors
3. Legal review:
- Have a team member not involved in the implementation review all license documents
- Verify that the chosen BSL terms properly protect commercial interests
- Confirm the Apache 2.0 implementation is correct and compatible with the BSL portions
4. Source code check:
- Sample at least 10 source files to ensure they have updated license headers
- Verify no MIT license references remain in any source files
5. Documentation check:
- Ensure any documentation that mentioned licensing has been updated to reflect the new structure
# Subtasks:
## 1. Remove MIT License and Create Dual License Files [done]
### Dependencies: None
### Description: Remove all MIT license references from the codebase and create the new license files for the dual license structure.
### Details:
Implementation steps:
1. Scan the entire codebase to identify all instances of MIT license references (license files, headers in source files, documentation mentions).
2. Remove the MIT license file and all direct references to it.
3. Create a LICENSE.md file containing:
- Full text of Business Source License (BSL) 1.1 with explicit commercial rights reservation for Ralph & Eyal
- Full text of Apache 2.0 license for non-commercial use
- Clear definitions of what constitutes commercial vs. non-commercial use
- Specific terms for obtaining commercial use permission
4. Create a CONTRIBUTING.md file that explicitly states the contribution terms:
- Contributors must agree to the dual licensing structure
- Commercial rights for all contributions are assigned to Ralph & Eyal
- Guidelines for acceptable contributions
Testing approach:
- Verify all MIT license references have been removed using a grep or similar search tool
- Have legal review of the LICENSE.md and CONTRIBUTING.md files to ensure they properly protect commercial rights
- Validate that the license files are properly formatted and readable
## 2. Update Source Code License Headers and Package Metadata [done]
### Dependencies: 39.1
### Description: Add appropriate dual license headers to all source code files and update package metadata to reflect the new licensing structure.
### Details:
Implementation steps:
1. Create a template for the new license header that references the dual license structure (BSL 1.1 / Apache 2.0).
2. Systematically update all source code files to include the new license header, replacing any existing MIT headers.
3. Update the license field in package.json to "BSL 1.1 / Apache 2.0".
4. Update any other metadata files (composer.json, setup.py, etc.) that contain license information.
5. Verify that any build scripts or tools that reference licensing information are updated.
Testing approach:
- Write a script to verify that all source files contain the new license header
- Validate package.json and other metadata files have the correct license field
- Ensure any build processes that depend on license information still function correctly
- Run a sample build to confirm license information is properly included in any generated artifacts
## 3. Update Documentation and Create License Explanation [done]
### Dependencies: 39.1, 39.2
### Description: Update project documentation to clearly explain the dual license structure and create comprehensive licensing guidance.
### Details:
Implementation steps:
1. Update the README.md with a clear, concise explanation of the licensing terms:
- Summary of what users can and cannot do with the code
- Who holds commercial rights (Ralph & Eyal)
- How to obtain commercial use permission
- Links to the full license texts
2. Create a dedicated LICENSING.md or similar document with detailed explanations of:
- The rationale behind the dual licensing approach
- Detailed examples of what constitutes commercial vs. non-commercial use
- FAQs addressing common licensing questions
3. Update any other documentation references to licensing throughout the project.
4. Create visual aids (if appropriate) to help users understand the licensing structure.
5. Ensure all documentation links to licensing information are updated.
Testing approach:
- Have non-technical stakeholders review the documentation for clarity and understanding
- Verify all links to license files work correctly
- Ensure the explanation is comprehensive but concise enough for users to understand quickly
- Check that the documentation correctly addresses the most common use cases and questions

44
tasks/tasks.json
View File

@ -2164,6 +2164,50 @@
"priority": "high",
"details": "Implement a version check mechanism that runs automatically with every command execution:\n\n1. Create a new module (e.g., `versionChecker.js`) that will:\n - Fetch the latest version from npm registry using the npm registry API (https://registry.npmjs.org/task-master-ai/latest)\n - Compare it with the current installed version (from package.json)\n - Store the last check timestamp to avoid excessive API calls (check once per day)\n - Cache the result to minimize network requests\n\n2. The notification should:\n - Use colored text (e.g., yellow background with black text) to be noticeable\n - Include the current version and latest version\n - Show the exact upgrade command: 'npm i task-master-ai@latest'\n - Be displayed at the beginning or end of command output, not interrupting the main content\n - Include a small separator line to distinguish it from command output\n\n3. Implementation considerations:\n - Handle network failures gracefully (don't block command execution if version check fails)\n - Add a configuration option to disable update checks if needed\n - Ensure the check is lightweight and doesn't significantly impact command performance\n - Consider using a package like 'semver' for proper version comparison\n - Implement a cooldown period (e.g., only check once per day) to avoid excessive API calls\n\n4. The version check should be integrated into the main command execution flow so it runs for all commands automatically.",
"testStrategy": "1. Manual testing:\n - Install an older version of the package\n - Run various commands and verify the update notification appears\n - Update to the latest version and confirm the notification no longer appears\n - Test with network disconnected to ensure graceful handling of failures\n\n2. Unit tests:\n - Mock the npm registry response to test different scenarios:\n - When a newer version exists\n - When using the latest version\n - When the registry is unavailable\n - Test the version comparison logic with various version strings\n - Test the cooldown/caching mechanism works correctly\n\n3. Integration tests:\n - Create a test that runs a command and verifies the notification appears in the expected format\n - Test that the notification appears for all commands\n - Verify the notification doesn't interfere with normal command output\n\n4. Edge cases to test:\n - Pre-release versions (alpha/beta)\n - Very old versions\n - When package.json is missing or malformed\n - When npm registry returns unexpected data"
},
{
"id": 39,
"title": "Update Project Licensing to Dual License Structure",
"description": "Replace the current MIT license with a dual license structure that protects commercial rights for project owners while allowing non-commercial use under an open source license.",
"status": "done",
"dependencies": [],
"priority": "high",
"details": "This task requires implementing a comprehensive licensing update across the project:\n\n1. Remove all instances of the MIT license from the codebase, including any MIT license files, headers in source files, and references in documentation.\n\n2. Create a dual license structure with:\n - Business Source License (BSL) 1.1 or similar for commercial use, explicitly stating that commercial rights are exclusively reserved for Ralph & Eyal\n - Apache 2.0 for non-commercial use, allowing the community to use, modify, and distribute the code for non-commercial purposes\n\n3. Update the license field in package.json to reflect the dual license structure (e.g., \"BSL 1.1 / Apache 2.0\")\n\n4. Add a clear, concise explanation of the licensing terms in the README.md, including:\n - A summary of what users can and cannot do with the code\n - Who holds commercial rights\n - How to obtain commercial use permission if needed\n - Links to the full license texts\n\n5. Create a detailed LICENSE.md file that includes:\n - Full text of both licenses\n - Clear delineation between commercial and non-commercial use\n - Specific definitions of what constitutes commercial use\n - Any additional terms or clarifications specific to this project\n\n6. Create a CONTRIBUTING.md file that explicitly states:\n - Contributors must agree that their contributions will be subject to the project's dual licensing\n - Commercial rights for all contributions are assigned to Ralph & Eyal\n - Guidelines for acceptable contributions\n\n7. Ensure all source code files include appropriate license headers that reference the dual license structure.",
"testStrategy": "To verify correct implementation, perform the following checks:\n\n1. File verification:\n - Confirm the MIT license file has been removed\n - Verify LICENSE.md exists and contains both BSL and Apache 2.0 license texts\n - Confirm README.md includes the license section with clear explanation\n - Verify CONTRIBUTING.md exists with proper contributor guidelines\n - Check package.json for updated license field\n\n2. Content verification:\n - Review LICENSE.md to ensure it properly describes the dual license structure with clear terms\n - Verify README.md license section is concise yet complete\n - Check that commercial rights are explicitly reserved for Ralph & Eyal in all relevant documents\n - Ensure CONTRIBUTING.md clearly explains the licensing implications for contributors\n\n3. Legal review:\n - Have a team member not involved in the implementation review all license documents\n - Verify that the chosen BSL terms properly protect commercial interests\n - Confirm the Apache 2.0 implementation is correct and compatible with the BSL portions\n\n4. Source code check:\n - Sample at least 10 source files to ensure they have updated license headers\n - Verify no MIT license references remain in any source files\n\n5. Documentation check:\n - Ensure any documentation that mentioned licensing has been updated to reflect the new structure",
"subtasks": [
{
"id": 1,
"title": "Remove MIT License and Create Dual License Files",
"description": "Remove all MIT license references from the codebase and create the new license files for the dual license structure.",
"dependencies": [],
"details": "Implementation steps:\n1. Scan the entire codebase to identify all instances of MIT license references (license files, headers in source files, documentation mentions).\n2. Remove the MIT license file and all direct references to it.\n3. Create a LICENSE.md file containing:\n - Full text of Business Source License (BSL) 1.1 with explicit commercial rights reservation for Ralph & Eyal\n - Full text of Apache 2.0 license for non-commercial use\n - Clear definitions of what constitutes commercial vs. non-commercial use\n - Specific terms for obtaining commercial use permission\n4. Create a CONTRIBUTING.md file that explicitly states the contribution terms:\n - Contributors must agree to the dual licensing structure\n - Commercial rights for all contributions are assigned to Ralph & Eyal\n - Guidelines for acceptable contributions\n\nTesting approach:\n- Verify all MIT license references have been removed using a grep or similar search tool\n- Have legal review of the LICENSE.md and CONTRIBUTING.md files to ensure they properly protect commercial rights\n- Validate that the license files are properly formatted and readable",
"status": "done",
"parentTaskId": 39
},
{
"id": 2,
"title": "Update Source Code License Headers and Package Metadata",
"description": "Add appropriate dual license headers to all source code files and update package metadata to reflect the new licensing structure.",
"dependencies": [
1
],
"details": "Implementation steps:\n1. Create a template for the new license header that references the dual license structure (BSL 1.1 / Apache 2.0).\n2. Systematically update all source code files to include the new license header, replacing any existing MIT headers.\n3. Update the license field in package.json to \"BSL 1.1 / Apache 2.0\".\n4. Update any other metadata files (composer.json, setup.py, etc.) that contain license information.\n5. Verify that any build scripts or tools that reference licensing information are updated.\n\nTesting approach:\n- Write a script to verify that all source files contain the new license header\n- Validate package.json and other metadata files have the correct license field\n- Ensure any build processes that depend on license information still function correctly\n- Run a sample build to confirm license information is properly included in any generated artifacts",
"status": "done",
"parentTaskId": 39
},
{
"id": 3,
"title": "Update Documentation and Create License Explanation",
"description": "Update project documentation to clearly explain the dual license structure and create comprehensive licensing guidance.",
"dependencies": [
1,
2
],
"details": "Implementation steps:\n1. Update the README.md with a clear, concise explanation of the licensing terms:\n - Summary of what users can and cannot do with the code\n - Who holds commercial rights (Ralph & Eyal)\n - How to obtain commercial use permission\n - Links to the full license texts\n2. Create a dedicated LICENSING.md or similar document with detailed explanations of:\n - The rationale behind the dual licensing approach\n - Detailed examples of what constitutes commercial vs. non-commercial use\n - FAQs addressing common licensing questions\n3. Update any other documentation references to licensing throughout the project.\n4. Create visual aids (if appropriate) to help users understand the licensing structure.\n5. Ensure all documentation links to licensing information are updated.\n\nTesting approach:\n- Have non-technical stakeholders review the documentation for clarity and understanding\n- Verify all links to license files work correctly\n- Ensure the explanation is comprehensive but concise enough for users to understand quickly\n- Check that the documentation correctly addresses the most common use cases and questions",
"status": "done",
"parentTaskId": 39
}
]
}
]
}