License
taskstream is free software under the GNU Affero General Public License v3.0. Here is what that means in practice.
LICENSE at the repository root.
What the license gives you
You may run the software for any purpose, study and modify it, and redistribute it — commercially or not — provided you pass on the same freedoms to everyone downstream.
Obligations
- Share the source. If you distribute the software, or a modified version of it, you must make the complete corresponding source available under the AGPL-3.0.
- Network use counts. Running a modified version as a service over a network requires offering the source to the people using that service. This is the clause that separates the AGPL from the GPL.
- Keep the notices. Copyright notices and the license text stay in place, and significant changes must be stated.
- No warranty. The software is provided as is, with no warranty, as the license states.
If you want to use the code under different terms — for example, in a closed product you cannot license as AGPL — you need a separate agreement from the copyright holders.
Where the license lives
| Path | What it is |
|---|---|
LICENSE | The full AGPL-3.0 text, at the repository root. |
Cargo.toml | The workspace manifest; each crate inherits the workspace license field. |
The canonical text is also published by theFree Software Foundation, and the matching identifier is AGPL-3.0.
Third-party code
- Dependencies pulled from crates.io or git keep their own licenses; the AGPL covers this repository's code, not theirs.
- The vendored forks under
patched/(for example the cersei provider and agent forks) retain their upstream licenses. Read the license in each patched crate before reusing it. - The self-hosted font in the web design system is Inter Variable, under the SIL Open Font License.
- The web design system's icons and copy are placeholders written for this repository. It reproduces no third-party wordmark, screenshot, or marketing copy.
Contributions
By contributing you agree that your contribution is licensed under the same terms, so the project can keep offering one consistent license to everyone. There is no separate CLA.
See LICENSE for the complete terms, andContributing for how to propose a change.