Skip to main content

License

Orkestra is open-sourced software licensed under the MIT license.

MIT License

Copyright (c) 2023-2024 Lucas Carvalho

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Third-Party Licenses

Orkestra includes several third-party libraries that are licensed under their own terms:

PSR Interfaces

The PSR interfaces are licensed under the MIT license.

Other Dependencies

For a complete list of dependencies and their licenses, please refer to the composer.json file or run:

composer licenses

Using Orkestra in Your Projects

Orkestra is free to use in personal, open-source, and commercial projects. You are free to:

  • Use Orkestra in commercial projects
  • Modify Orkestra to suit your needs
  • Distribute your modifications
  • Include Orkestra in your own open-source or proprietary software

The only requirement is to include the original copyright notice and the license text in any substantial copy of the software.

Contributing to Orkestra

By contributing to Orkestra, you agree that your contributions will be licensed under the same MIT license as the project. This ensures that the entire codebase remains under a consistent license.

Questions?

If you have any questions about the license or how it applies to your specific use case, please reach out to us via GitHub Discussions.