📦
Bunty

License

Bunty Framework is open source and free to use

MIT License

Bunty Framework is licensed under the MIT License, one of the most permissive and widely-used open source licenses.

✅
Commercial Use
🔄
Modify & Distribute
🛡️
Private Use

Full License Text

MIT License
Copyright (c) 2025 Bunty Framework Contributors
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.

What This Means

✅ You Can

  • • Use Bunty Framework in commercial projects
  • • Modify the source code
  • • Distribute your modified versions
  • • Use it privately without sharing changes
  • • Sell products that include Bunty Framework

⚠️ You Must

  • • Include the original license notice
  • • Include the copyright notice
  • • Not hold us liable for damages

Note: You don't need to open source your code or share your modifications.

Third Party Licenses

Bunty Framework includes or depends on several third-party libraries. Each has its own license:

Bun Runtime MIT License
TypeScript Apache 2.0 License
Various npm packages Various licenses

For a complete list of dependencies and their licenses, check the package.json file in our repository.

Have Questions?

If you have questions about licensing or need clarification, feel free to reach out to us.

GitHub Discussions → Email Us →