> For the complete documentation index, see [llms.txt](https://docs.rujira.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rujira.network/developers/getting-started/licenses.md).

# Licenses

## License Overview

Rujira is an open-source software project, licensed under the MIT License. This license allows developers to freely use, modify, and distribute the software while providing certain protections to the authors and contributors.

Below are the details of the license and how it applies to the Rujira project.

***

## MIT License

The Rujira project is licensed under the MIT License, a permissive open-source license. Here's what the MIT License allows:

* **Free Usage**: You can use Rujira for any purpose, whether personal, academic, or commercial.
* **Modification**: You're free to modify the source code to fit your needs.
* **Distribution**: You may distribute the original or modified versions of Rujira.
* **Private Use**: You are allowed to use Rujira without publicly disclosing your modifications.

However, the MIT License also includes certain responsibilities:

* **Attribution**: You must include the original copyright notice and license in any significant portion of the software.
* **No Liability**: The software is provided "as is," without warranty of any kind. The authors and contributors are not liable for any damages arising from its use.

For more details, check the [full text of the MIT License](https://opensource.org/license/MIT).

***

## Open-Source Standards (OSS)

Rujira follows open-source standards to promote transparency, collaboration, and community-driven development. By using the MIT License, we align with OSS best practices, which include:

* **Accessibility**: The source code is freely available for anyone to inspect, contribute to, and improve.
* **Collaboration**: Contributions from developers are welcome, subject to the project's contribution guidelines.
* **Security**: Regular updates and community feedback ensure security vulnerabilities are addressed promptly.

We encourage developers to contribute back to the Rujira project and help enhance its features and stability.

***

## How to Contribute

We invite developers to collaborate on the Rujira project by:

1. Forking the repository.
2. Submitting pull requests for improvements.
3. Reporting bugs or security issues.
4. Participating in discussions and feature planning.

All contributions are governed by the MIT License and must adhere to the project's **Code of Conduct**.

***

By using Rujira, you agree to the terms of the MIT License and understand your rights and responsibilities under this open-source software model.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rujira.network/developers/getting-started/licenses.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.