Permissive · keep the notices
ISC, in plain English.
TL;DR
You can use, change, self-host and distribute it, with or without charging money. Keep the original copyright and permission notice with copies. You don’t have to publish your changes. The authors don’t provide a warranty.
Source: Open Source Initiative · ISC license text ↗What can I do with it?
- Self-host it for yourself
- Yes.
- Use it for your business
- Yes.
- Change the code
- Yes.
- Keep your changes private
- Yes.
- Share or sell copies
- Yes. Keep the copyright and permission notice.
What do I need to do?
- Include the copyright and permission notice in copies.
- The software comes without a warranty from its authors.
ISC gives broad reuse permission with notice requirements, much like MIT.
A real-world example
You customise an ISC tool for work. You can keep your changes private; copies you distribute must retain its copyright and permission notice.
The code license and the hosting bill are separate.
A license tells you what you can do with the code. It doesn’t make Cloudflare, domains, email delivery or other services free. Check the project’s hosting notes as well.
This is a general explanation. The repository’s exact license, version, exceptions and package-specific terms govern. Other packages, dependencies and images can have different licenses.
Read the complete license terms ↗