Glossary · Coding agents
Software license
A software license sets out the permissions and conditions that apply to using software. It explains what you may do with the program or its source code, such as running, modifying or redistributing it, while different licenses grant different rights and impose different requirements.
Software license: the explanation
A license states the terms under which rights holders make software available. For a project whose code is published, it helps establish which forms of reuse are permitted, as explained in the [GitHub documentation](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository). You can usually look for a dedicated license file or relevant product terms. Before reusing a component, also check the scope of the text: individual files, dependencies or other parts of the same project may be covered by different conditions and notices.
Licenses reflect different approaches to distributing and reusing software. Some broadly permit modification and redistribution subject to conditions. Others restrict those activities or define how proprietary software may be used. Your practical task is to connect the wording to your plans, such as personal use, internal adaptation or distribution to customers. Requirements may involve retaining notices, providing particular materials or meeting other specified conditions. The applicable obligations depend on the actual license text and the circumstances of your use.
An AI tool may involve several overlapping sets of terms. Its code, dependencies, model files and remote services do not necessarily share one license. The code license alone does not explain a service’s privacy practices or establish rights over every item processed through it. If your intended use raises a significant legal question, a general glossary explanation cannot resolve it. You need to examine the relevant texts in relation to the particular components, distribution arrangements and activities involved in your situation.
A concrete example
You want to adapt an MCP server for a community organisation and share the modified version with another group. You locate its license and check the conditions for modification and redistribution. You also review the components you plan to add. A publicly accessible repository does not answer those questions by itself. The terms of the service that the server connects to may need separate consideration before you share the setup.
Why it matters
The license can determine whether a tool fits the way you intend to work and share adaptations. Checking it early helps avoid building on permissions you have misunderstood. For an agent, consider the code, any model files and connected services separately. A statement that software is free of charge does not summarise these rights, and access to source code does not automatically permit every kind of reuse.
Common misconceptions
- Software that costs nothing does not necessarily give you permission to modify or redistribute its code, because the price of access and the rights granted by the applicable license are separate matters that require separate attention.
- A publicly visible repository is not automatically open source software, because being able to read the code does not establish the rights to modify, reuse and redistribute it under an appropriate license and its stated conditions.
Related terms: coding agents
- GitHub stars
- GitHub stars are markers that users can add to repositories on GitHub to save them or express interest.
- fork
- A fork is a version of a software project developed separately from an existing project.
- commit
- A commit is a record in a Git repository’s history that represents a project state and connects it to the project’s development.
- command-line interface
- A command-line interface is a way to control a program by entering text instructions, usually in a terminal.
- IDE
- An IDE is an integrated development environment, an application that brings together tools for creating and examining software.
Where this site covers it
The term appears on 2,329 pages of this site. A few of them:
- Hermes Agent reference guide: installation, memory and skills, models, costs, and limitations Guide
- 9Router: review, pricing, security and alternatives Agent
- AAS Core: review, pricing, security and alternatives Agent
- AG-UI: review, pricing, security and alternatives Agent
- Agent Lightning: review, pricing, security and alternatives Agent
- Agent Reach: review, pricing, security and alternatives Agent
- Agentic Bug Hunter: review, pricing, security and alternatives Agent
- B: review, pricing, security and alternatives Agent
Go further
Frequently asked questions
Where can you find the license?
Look for a license file, notices in source files and the project documentation. For an application or hosted service, also review the relevant terms. Confirm that the wording applies to the component and version you actually plan to use.
What if no license is stated?
Do not assume that accessible code permits unrestricted reuse. Look for further information or ask the rights holders what permissions they grant. If the use would create obligations for your organisation, have the specific circumstances reviewed before relying on assumptions.
Does it cover the model too?
Not necessarily. Tool code and model files may be supplied under different terms, while a remote service may impose another set of conditions. Identify the applicable text for each component you actually use rather than assuming one license covers everything.
Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score