# Open-source notice Updated: October 20, 2026 The Koder desktop app and the KARMEN LOOP kernel that ships with it (together, “the software”) use open-source software. The authors offer that software to everyone under an open-source license, and they keep their copyright. This notice lists the open-source components the software uses, their versions, sources, and licenses. It also states the rights those licenses give you, the license duties we meet, and how to get the source. License texts and copyright notices in this notice are read from the original files that ship with each component. The third-party list is generated by a script from the metadata of the components that ship with the app. ## 1. The main open-source components 1.1 The KARMEN LOOP kernel. In the installer you can download now, the kernel that actually runs is one we wrote. 1.2 Runtimes. So the software can run on your computer, the installer includes two runtimes: Node.js 24.21.0 (MIT License) and CPython 3.12.15 (Python Software Foundation License). CPython is provided as a standalone build. Their license texts are in the install folder. Source links are in the component list at the end of this page. The exact version (commit), the place in the software, and the full license text of a main component are under “Components and full license texts” later on this page. Every third-party component is in the “Third-party components” list at the end of this page. ## 2. Modifications We have not modified the source files of the runtimes that ship in the installer. If we later modify the source of an open-source component that still ships with the app, we will add a clear note in the modified file, and this section will name the file, the date, and what changed. ## 3. Rights the open-source licenses give you 3.1 The MIT License. The MIT License lets anyone who receives a copy deal in the software without restriction and without a fee, including the rights to use, copy, modify, merge, publish, distribute, sublicense, and sell copies, provided the copyright notice and the permission notice appear in all copies or substantial portions of the software. The software is provided “as is,” without warranty. 3.2 Apache License 2.0. Under Apache License 2.0, each contributor grants you a perpetual, worldwide, non-exclusive, no-charge, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute the work and derivative works of it, and a corresponding patent license (if you file a lawsuit claiming the work infringes a patent, that patent license ends on the day you file). You may read and modify the source, build on it, include it in your own commercial system, and distribute a product if you meet the license. When you distribute, you give the recipient a copy of Apache License 2.0, you add a clear notice in files you changed, you keep all copyright, patent, trademark, and attribution notices from the original in the source form of a derivative work you distribute, and if the original includes a NOTICE file you include those attribution notices in a reasonable way. Apache License 2.0 does not grant the right to use the licensor’s trade name, trademark, service mark, or product name. The work is provided “as is,” without warranty. If a component in the installer is under Apache License 2.0, we keep the notices in that component’s own license file. 3.3 Other licenses. Third-party components also use ISC, BSD-2-Clause, BSD-3-Clause, BlueOak-1.0.0, 0BSD, CC0-1.0, Unlicense, Python-2.0, Zlib, MPL-2.0, LGPL-3.0, and others. The third-party list says which. Those licenses also require the copyright notice and the license text to be kept. In particular: 1. MPL-2.0 (Mozilla Public License 2.0) is a weak copyleft license at the file level. The software ships components released under MPL-2.0 without modifying them. Source for those files can be obtained from the sources named in the list. If we modify an MPL-2.0 file, we will provide the source of the modified file as that license requires. 2. LGPL-3.0 (GNU Lesser General Public License 3.0). If the third-party list includes a library released under LGPL-3.0, it is provided as a separate library, and you can replace it with a version you build yourself. 3. For a dual-licensed component (for example “MIT OR GPL-3.0-or-later”), we chose the permissive license (MIT). 4. A few components marked “not declared” do not name a license in their metadata. We are checking their license files one by one. ## 4. How to get the source Node.js, CPython, and their licenses ship in the install folder, and you can read them there. Links to each component’s upstream repository are in the component notes on this page and in the third-party list. If you need a copy of the source of the version of a bundled component that we used, contact us as section 6 describes. We will provide it within a reasonable time, and we will charge no more than the actual cost, if there is a cost. ## 5. What the base service is The software itself does not provide a large language model. The model service you use is one you choose and open. That service’s own terms, privacy policy, and billing rules apply. We are not a parent, a partner, an authorized agent, or an endorser of the operator of those services. Web search sends the query to a public search service. Fetching a page opens that address directly. ## 6. Contact Questions about this notice, or a request for a source copy: KARMENLOOP Official Team. Team location: Shanghai, China. Contact email: info@karmenloop.com. ## 7. Trademarks The names and marks of the runtimes that ship with the installer belong to their respective owners. This notice uses those names to say what is included and under which license. That is not an association with this software, and it is not an endorsement of this software by those owners.