---
title: "Open Source Software Licenses 101: The ISC License"
description: "Explore the history, requirements, and key differences of the ISC License in open source software."
canonical_url: "https://fossa.com/blog/open-source-software-licenses-101-isc-license/"
markdown_url: "https://fossa.com/blog/open-source-software-licenses-101-isc-license.md"
content_type: "blog"
language: "en"
date_published: "2021-04-12"
date_modified: "2025-11-10"
author: "Kristen Miller"
organization: "FOSSA"
---

# Open Source Software Licenses 101: The ISC License

> Explore the history, requirements, and key differences of the ISC License in open source software.

Like the [MIT License](https://fossa.com/blog/open-source-licenses-101-mit-license.md) and the BSD License family, the ISC License is a short, [permissive license](https://fossa.com/blog/all-about-permissive-licenses.md). Created by the [Internet Software Consortium](https://www.isc.org/licenses/) (now the Internet Systems Consortium), the ISC License is basically a “stripped down” version of the MIT and [simplified BSD](https://tldrlegal.com/license/bsd-2-clause-license-%28freebsd)>) licenses, with all extraneous language removed.

The ISC License has an interesting and somewhat controversial history, which is one reason why it’s not used as often as other permissive licenses. In fact, its creator, the ISC, [no longer uses](https://www.isc.org/licenses/) it for their open source software, selecting the [Mozilla Public License 2.0](https://fossa.com/blog/open-source-software-licenses-101-mozilla-public-license-2-0.md) instead.

So, why is this [open source license](https://fossa.com/learn/open-source-licenses.md) less popular than the rest of its permissive license cohort, and why might some projects still choose it? We’ll get into the details below.

## ISC License: Requirements

Functionally, the ISC License is identical to the MIT License. The difference lies in the license language, which is as brief as possible, following the rules of the [Berne Convention](https://en.wikipedia.org/wiki/Berne_Convention). Basically, this convention set the “ground rules” for the protection of authored works.

The ISC License has very few requirements — only two, in fact — and they’re the same as those of the MIT License. When copying or modifying the licensed code, users must include:

- The original copyright notice
- A copy of the license itself

As with the BSD and MIT licenses, the copyright notice is “baked into” the ISC text. At the beginning of the terms, you’ll see the following line: “Copyright (c) 4-digit year, Company or Person's Name.” The author of the software fills out this information before putting the license in the code repository, and in doing so covers both requirements.

## Using the Licensed Code

As a permissive license, the ISC allows for just about any application of the code. Users are free to:

- **Use the code commercially.** A company or individual can create a proprietary work that includes a copy or modification of the ISC-licensed code, then charge money for that software.
- **Modify the code.** A developer may make changes to or rework the original software.
- **Distribute the code.** An individual can share the code, including any updates or alterations, with others, either privately, publicly, or both.

The license clearly states that it does not provide a warranty on the software. Also, contributors (“authors”) disclaim liability for any damages that may arise from the use or sale of the ISC’d code.

## ISC License vs. Other Permissive Licenses

While the ISC License is very similar to other common permissive licenses, there are a few key differences. In this section, we'll compare the ISC with the MIT, BSD, and Apache 2.0 licenses.

  <table className="w-full text-left border-collapse">
    <thead>
      <tr className="border-b border-white/10">
        <th className="py-3 pr-4 text-white font-medium align-top">Feature</th>
        <th className="py-3 pr-4 text-white font-medium align-top">ISC License</th>
        <th className="py-3 pr-4 text-white font-medium align-top">MIT License</th>
        <th className="py-3 pr-4 text-white font-medium align-top">BSD 2-Clause</th>
        <th className="py-3 text-white font-medium align-top">Apache 2.0</th>
      </tr>
    </thead>
    <tbody>
      <tr className="border-b border-white/10">
        <td className="py-3 pr-4 text-white font-medium align-top">Copyright Notice</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Required</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Required</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Required</td>
        <td className="py-3 text-zinc-300 align-top">Required</td>
      </tr>
      <tr className="border-b border-white/10">
        <td className="py-3 pr-4 text-white font-medium align-top">License Text</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Required</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Required</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Required</td>
        <td className="py-3 text-zinc-300 align-top">Required</td>
      </tr>
      <tr className="border-b border-white/10">
        <td className="py-3 pr-4 text-white font-medium align-top">Modification Disclosure</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Not required</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Not required</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Not required</td>
        <td className="py-3 text-zinc-300 align-top">Required (significant changes)</td>
      </tr>
      <tr className="border-b border-white/10">
        <td className="py-3 pr-4 text-white font-medium align-top">Commercial Use</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Allowed</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Allowed</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Allowed</td>
        <td className="py-3 text-zinc-300 align-top">Allowed</td>
      </tr>
      <tr className="border-b border-white/10">
        <td className="py-3 pr-4 text-white font-medium align-top">Modification</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Allowed</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Allowed</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Allowed</td>
        <td className="py-3 text-zinc-300 align-top">Allowed</td>
      </tr>
      <tr className="border-b border-white/10">
        <td className="py-3 pr-4 text-white font-medium align-top">Distribution</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Allowed</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Allowed</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Allowed</td>
        <td className="py-3 text-zinc-300 align-top">Allowed</td>
      </tr>
      <tr className="border-b border-white/10">
        <td className="py-3 pr-4 text-white font-medium align-top">Sublicensing</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Allowed (implicit)</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Allowed (explicit)</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Allowed</td>
        <td className="py-3 text-zinc-300 align-top">Allowed</td>
      </tr>
      <tr>
        <td className="py-3 pr-4 text-white font-medium align-top">Patent Grant</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Not explicit</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Not explicit</td>
        <td className="py-3 pr-4 text-zinc-300 align-top">Not explicit</td>
        <td className="py-3 text-zinc-300 align-top">Explicit</td>
      </tr>
    </tbody>
  </table>

### ISC License vs. the MIT License

For all intents and purposes, these two licenses are the same. The ISC License simply removes language that would be considered extraneous according to the Berne Convention. The MIT License is much more explicit in its wording, stating outright that users have the right to sublicense, modify, copy, and/or distribute the code.

### ISC License vs. the BSD Licenses

The ISC License is considered equivalent to the [Simplified (2-Clause) BSD License](https://tldrlegal.com/license/bsd-2-clause-license-%28freebsd)#fulltext>) but with more concise language. It’s not as permissive as the BSD 0-Clause License (which is essentially a public-domain-equivalent license), nor as strong as the [BSD 3-Clause License](https://fossa.com/blog/open-source-software-licenses-101-bsd-3-clause-license.md), which includes a non-endorsement clause.

### ISC License vs. the Apache License 2.0

The [Apache License 2.0](https://fossa.com/blog/open-source-licenses-101-apache-license-2-0.md) has an additional requirement beyond those of the MIT, Simplified BSD, and ISC licenses. If a user makes any significant changes to the code, they must include a list of those modifications when distributing the software. They do not need to disclose the source code, however, which is why the Apache License 2.0 is still considered permissive.

## History and Controversy of the ISC License

Since the ISC License is basically the same as the MIT and Simplified BSD licenses, why isn’t it used as frequently? After all, it’s even more concise. You’d think that would make it the most popular of the permissive license options.

The answer lies in the wording of the original license. When it was released, the ISC License read: “Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted ...” The use of “and” turned out to be a problem, with some (particularly the University of Washington) interpreting it as a prohibition against distributing the software. To address this issue, the “and” was later changed to “and/or.”

Because of this ambiguity, the highly influential GNU [suggests](https://www.gnu.org/licenses/license-list.html#ISC) that developers select a different license for their open source software. They do state that there’s no reason to avoid software already under this license, but future projects should avoid it. This recommendation has no doubt hurt the ISC License’s usage rates. And, as a result, the license isn’t as recognized or trusted as other permissive options like MIT and Apache 2.0.

Nevertheless, a number of OSS projects do use the ISC license. One example is the [OpenBSD](https://www.openbsd.org/) operating system. Another is [OpenStreetMap](https://www.openstreetmap.org/#map=4/38.01/-95.84), an open source and free-to-use map of the world.

## Frequently Asked Questions About the ISC License

### What is the ISC License?

The ISC License is a short, permissive open source software license created by the Internet Software Consortium (now Internet Systems Consortium). It's functionally identical to the MIT License but uses more concise language, following the Berne Convention rules.

### What are the requirements of the ISC License?

The ISC License has only two requirements: you must include the original copyright notice and a copy of the license itself when you copy or modify the code. The copyright notice is typically included at the beginning of the license text.

### Can I use ISC-licensed code in commercial software?

Yes, the ISC License explicitly allows commercial use. You can create proprietary software that includes ISC-licensed code and charge money for it, as long as you include the copyright notice and license text.

### Do I need to share my modifications to ISC-licensed code?

No, the ISC License does not require you to share your modifications or release them under the same license. You can keep your changes proprietary and private, just like with the MIT License.

### Why isn't the ISC License more popular?

The ISC License has a controversial history due to ambiguous wording in its original version. The GNU project recommends developers avoid using it for new projects, which has hurt its adoption rates. However, there's no reason to avoid software already licensed under ISC.

### Should I use the ISC License for my project?

While the ISC License is functionally equivalent to MIT and BSD, the GNU project recommends using MIT or BSD instead due to the ISC License's historical ambiguity issues. MIT and Apache 2.0 are more widely recognized and trusted in the open source community.

<script type="application/ld+json" dangerouslySetInnerHTML={{__html: JSON.stringify({
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "url": "https://fossa.com/open-source-software-licenses-101-isc-license/",
  "name": "ISC License FAQ",
  "description": "Frequently asked questions about the ISC License, its requirements, how it compares to MIT and BSD licenses, and its controversial history",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is the ISC License?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The ISC License is a short, permissive open source software license created by the Internet Software Consortium (now Internet Systems Consortium). It's functionally identical to the MIT License but uses more concise language, following the Berne Convention rules."
      }
    },
    {
      "@type": "Question",
      "name": "What are the requirements of the ISC License?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The ISC License has only two requirements: you must include the original copyright notice and a copy of the license itself when you copy or modify the code. The copyright notice is typically included at the beginning of the license text."
      }
    },
    {
      "@type": "Question",
      "name": "Can I use ISC-licensed code in commercial software?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, the ISC License explicitly allows commercial use. You can create proprietary software that includes ISC-licensed code and charge money for it, as long as you include the copyright notice and license text."
      }
    },
    {
      "@type": "Question",
      "name": "Do I need to share my modifications to ISC-licensed code?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No, the ISC License does not require you to share your modifications or release them under the same license. You can keep your changes proprietary and private, just like with the MIT License."
      }
    },
    {
      "@type": "Question",
      "name": "Why isn't the ISC License more popular?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The ISC License has a controversial history due to ambiguous wording in its original version. The GNU project recommends developers avoid using it for new projects, which has hurt its adoption rates. However, there's no reason to avoid software already licensed under ISC."
      }
    },
    {
      "@type": "Question",
      "name": "Should I use the ISC License for my project?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "While the ISC License is functionally equivalent to MIT and BSD, the GNU project recommends using MIT or BSD instead due to the ISC License's historical ambiguity issues. MIT and Apache 2.0 are more widely recognized and trusted in the open source community."
      }
    }
  ]
})}} />

## Related resources

- [Analyzing 5 Major OSS License Compliance Lawsuits](https://fossa.com/blog/analyzing-5-major-oss-license-compliance-lawsuits.md): Learn about five lawsuits that have helped shape global enforcement of open source software licenses.
- [May 2025 FOSSA Product Updates](https://fossa.com/blog/may-2025-product-updates.md): Learn about several recent FOSSA product updates, including container scanning and CycloneDX report improvements.
- [Annotate Dependencies with Context: Introducing Package Labels in FOSSA](https://fossa.com/blog/annotate-dependencies-context-introducing-package-labels.md): Introducing FOSSA Package Labels - a powerful way to annotate packages with contextual metadata, enabling more efficient and insightful reporting and filtering.
- [License Compliance, SBOM, and Vulnerability Management for Smaller Teams: FOSSA Business Tier](https://fossa.com/blog/fossa-business-tier.md): FOSSA introduces a new business tier tailored for smaller teams, offering flexible pricing and comprehensive features for SBOM, vulnerability management, and license compliance.
- [Fall 2024 Software Licensing Roundup](https://fossa.com/blog/fall-2024-software-licensing-roundup.md): Explore the significant licensing stories of fall 2024, including Elastics return to open source, the new fair source licensing model, and the PearAI controversy.

## Source

Canonical page: https://fossa.com/blog/open-source-software-licenses-101-isc-license/