ISC License, explained
Permissive ISC · 0BSD
ISC is a very short permissive licence, equivalent in practice to MIT: use the code anywhere and keep the notice. 0BSD drops the notice requirement too.
Not legal advice. Read the licence text for the exact terms.
What it allows
- Use, copy, modify and distribute the code for any purpose, commercial included
What it requires
- Keep the copyright notice and permission notice in copies (not required by 0BSD)
When it matters
| Shipping an app (desktop, mobile, on-premises) | Allowed, closed source included. Include the licence text and copyright notice, usually in a third-party notices file or an "About" screen. |
|---|---|
| A hosted service (SaaS) | Allowed. Nothing to publish; the notice requirement applies when you distribute the code, and JavaScript sent to browsers counts, so keep notices in your bundles. |
| Internal use | Allowed, with no conditions to meet while the code stays inside your organisation. |
Its family: permissive
You can use, change and ship the code in any product, including closed-source ones. You must keep the copyright and licence notice (usually in a third-party notices file); Apache-2.0 also asks you to state changes and keep its NOTICE file.
Questions
Is ISC the same as MIT?
Functionally very close. ISC removes language the authors considered unnecessary; the obligations are the same: keep the notice.
Other licences
Related free tools
Dependency licence check
Upload a lockfile and see every dependency's licence. GPL, AGPL, unknown and changed licences are flagged for your kind of project. Free.
SBOM summary generator
Upload a lockfile and get an SBOM summary by email: components, licences, vulnerabilities and AI components. CycloneDX and SPDX files with Pro.
Published ; awaiting review.