Which repository revision, modules, forks, patches, plugins, and dependencies will be used?
LICENSE GUIDE · VERIFIED 2026-08-05
MonkeyCode is published under GNU AGPL-3.0.
The repository License file is the controlling source for the project code. This page provides evaluation questions, not legal advice or a substitute for reading the license and reviewing your specific use with qualified counsel.
VERIFIED FACTThe public chaitin/MonkeyCode repository identifies GNU Affero General Public License v3.0 as its license.
Open source permits inspection and use subject to the controlling terms. It does not mean “no obligations,” and this website does not determine how those obligations apply to your organization, modifications, distribution, network service, dependencies, trademarks, or hosted offering.
Review questions
Bring deployment facts to legal review.
Document the actual code, changes, users, distribution, network access, and third-party components.
Will your organization change covered code, and how will changes be tracked and maintained?
Who interacts with the modified program over a network and what source obligations may apply?
Will binaries, images, appliances, or modified copies be conveyed to another party?
Which license notices, corresponding source, build information, and offers must accompany use?
Review trademarks, content, model/provider terms, dependencies, and commercial service terms independently.
Evidence package
Keep a reproducible compliance record.
A current inventory is more useful than relying on a product label.
| Record | Minimum evidence |
|---|---|
| Version | Repository URL, commit or release, image digest, and deployment date |
| Changes | Patch set, fork history, build instructions, and responsible owner |
| Dependencies | Software bill of materials and all applicable license notices |
| Users and delivery | Who receives or accesses the software and by what mechanism |
| Review | Legal decision, assumptions, required actions, reviewer, and re-review trigger |
Common questions
AGPL-3.0, answered.
Source-backed direct answers: what does AGPL-3.0 mean?, can I use it commercially?, is it free? · plus the AGPL-3.0 compliance guide.
What license is MonkeyCode released under?
The public chaitin/MonkeyCode repository identifies the GNU Affero General Public License v3.0 (AGPL-3.0) as its license. The repository LICENSE file is the controlling source.
Can I use MonkeyCode commercially?
AGPL-3.0 permits commercial use under its terms. The obligations that matter most arise when you modify the tool and make the modified version available to others over a network; review your specifics with qualified counsel.
Is MonkeyCode free?
The source is free and open under AGPL-3.0, so you can obtain, run, and modify it without a license fee. Free to obtain is not the same as free to operate, which still carries infrastructure, model, and operations cost.
Does using MonkeyCode make my own code AGPL?
No. Using the tool to build your own software does not place your software under AGPL — the license covers the platform’s source, not the code you produce with it. Modifying and network-exposing the tool itself is the case to plan for.
Do I need a legal review?
For commercial, modified, or network-exposed deployments, yes. This page provides evaluation questions, not legal advice, and is not a substitute for reading the license and consulting counsel.
AUTHORITATIVE TEXT