{
  "id": "software-license",
  "title": "Software License",
  "lang": "en",
  "source_lang": "en",
  "summary": "A software license defines permissions and conditions for using, copying, modifying, or distributing software, shaping its legal status and commercial or collaborative development.",
  "category": "society",
  "subcategory": "law",
  "type": "concept",
  "aliases": [
    "Software licence",
    "Computer software license"
  ],
  "generated_at": "2026-11-03",
  "model": "pro/gpt-6.1-sol",
  "url": "https://aiwiki.page/en/software-license/",
  "translations": {
    "zh-Hans": {
      "url": "https://aiwiki.page/zh/software-license/",
      "json": "https://aiwiki.page/zh/software-license.json"
    }
  },
  "sections": [
    {
      "heading": "",
      "text": "A software license is a grant of permission to exercise specified rights in a computer program, usually subject to conditions. It may authorize installation and execution, copying, modification, redistribution, or some combination of these activities. Licenses range from individually negotiated commercial agreements to standardized public permissions accompanying software distributed worldwide. They are a central form of intellectual property licensing because obtaining a copy of a program does not ordinarily transfer ownership of the intellectual property embodied in it.\n\nSoftware licensing operates principally through copyright and contract law, sometimes alongside patent, confidentiality, and trademark rules. Its practical significance extends beyond payment: license terms determine whether a program can be studied, incorporated into another product, offered as an online service, transferred to another user, or maintained independently of its original supplier. Commercial software may be openly licensed, while software supplied without charge may impose extensive restrictions.\n\nA license must be distinguished from the software itself, the mechanism used to deliver it, and any associated support or service agreement. One product can contain components governed by many licenses, and the same program can be offered under different licenses to different recipients. The resulting legal arrangements influence software markets, collaborative development, procurement, and the operation of digital infrastructure."
    },
    {
      "heading": "Historical development",
      "text": "Early software distribution did not follow a single licensing model. During the 1950s and 1960s, computer manufacturers frequently supplied programs as part of broader hardware and service arrangements. Universities, research laboratories, and user groups also exchanged code, although access and reuse depended on institutional practices and particular agreements. Source availability in this period did not necessarily imply an unrestricted legal permission to redistribute or commercialize the software.\n\nThe emergence of a distinct software industry made licensing more economically significant. IBM announced the unbundling of many software and service charges from hardware prices in 1969, an important development in the market for separately priced software. During the following decades, suppliers increasingly treated programs as products whose copying and deployment required separately defined permissions. Distribution on physical media made it possible to sell standardized packages on a large scale, while the ease of copying created incentives for contractual restrictions and technical controls.\n\nCopyright protection became a more explicit foundation for these arrangements. In the United States, the Computer Software Copyright Act of 1980 amended federal copyright law, including provisions concerning computer programs and certain copying or adaptation by owners of copies. Internationally, Article 10 of the Agreement on Trade-Related Aspects of Intellectual Property Rights, concluded in 1994, requires protection of computer programs as literary works, whether expressed in source or object code. These developments strengthened the legal framework within which software permissions could be granted or withheld.\n\nAlternative licensing institutions developed alongside proprietary software. Richard Stallman announced the GNU Project in 1983, and the Free Software Foundation was established in 1985. The first version of the GNU General Public License appeared in 1989, followed by version 2 in 1991 and version 3 in 2007. Berkeley Software Distribution licenses and other permissive licenses provided different approaches to redistribution and modification. These licenses used copyright not simply to restrict copying but to authorize broad reuse under stated conditions.\n\nThe establishment of the Open Source Initiative in 1998 helped institutionalize a further vocabulary and approval process for publicly reusable software. Meanwhile, internet distribution, subscription software, mobile application stores, and hosted computing changed how permissions were delivered and priced. These developments did not eliminate earlier license forms: contemporary systems commonly combine decades-old components, recently published libraries, proprietary applications, and separately governed online services."
    },
    {
      "heading": "Legal foundations and the scope of permission",
      "text": "Copyright generally protects a program’s original expression rather than its abstract ideas, functionality, or underlying algorithms. Protection can apply to source code and compiled code, although the boundary between protected expression and unprotected elements differs among jurisdictions and factual settings. A software license typically authorizes acts that would otherwise fall within a rights holder’s exclusive rights, such as reproduction or distribution. It does not automatically confer ownership of the copyright itself.\n\nThe distinction between permission and contractual obligation is important. A public license may grant permissions to anyone satisfying its conditions, whereas a negotiated agreement may create extensive reciprocal duties concerning payment, confidentiality, support, and audits. Whether a particular provision operates as a condition limiting copyright permission or as a contractual promise can affect the available claim and remedy. A payment dispute, for example, does not invariably constitute intellectual property infringement merely because it arises within a software transaction.\n\nLicenses also exist alongside statutory permissions and limitations. In the United States, 17 U.S.C. § 117 permits certain copying and adaptation by the owner of a copy of a computer program, subject to its requirements. Fair use can also matter in particular disputes. Within the European Union, Directive 2009/24/EC addresses the legal protection of computer programs and includes provisions on necessary use, backup copies, observation and testing, and limited decompilation for interoperability. The extent to which contractual terms can alter statutory positions is jurisdiction-specific.\n\nOther intellectual property rights can require separate treatment. A copyright license does not necessarily include a patent license covering a technique implemented by the program. Access to proprietary source code may also be subject to trade secret obligations. Permission to redistribute code does not automatically grant unrestricted use of a project’s trademarks, logos, or certification marks. Consequently, a distributor may be able to redistribute a modified program while being required to distinguish its branding from that of the original project.\n\nThe absence of an express license is not equivalent to unrestricted permission. Publishing code in an accessible repository normally does not place it in the public domain. Conversely, software genuinely outside copyright protection may still be associated with patent rights, contractual commitments, or separately protected assets. Documentation, fonts, images, datasets, and other materials bundled with a program can have distinct legal status, so a single product-level label does not always describe every element of a distribution."
    },
    {
      "heading": "Proprietary licenses and commercial entitlement models",
      "text": "Proprietary software licenses reserve substantial control to the rights holder. They commonly authorize use of executable code while restricting modification, redistribution, sublicensing, or access to source code. Proprietary does not mean that a program must be sold for money: freeware, evaluation versions, and limited personal-use editions can remain proprietary. Nor does the availability of source code alone make a license open; source may be supplied only for inspection, integration, or use under confidentiality obligations.\n\nAn end-user license agreement, often abbreviated EULA, defines permissions and restrictions for the ultimate user. Enterprise transactions may instead use a master agreement supplemented by order forms, product terms, and service schedules. These documents can specify the licensed entity, authorized affiliates, geographic scope, permitted environments, and treatment of contractors. Development tools may distinguish development, testing, and production use, while database or server products may impose different rules on passive backup systems and disaster-recovery installations.\n\nCommercial entitlements are measured in several ways. A named-user license attaches permission to an identified person; a concurrent-user license limits simultaneous use. Other models count devices, processors, processor cores, server instances, transactions, or units of consumption. A perpetual license generally grants an enduring right to use a specified product or version under its terms, rather than a guarantee of indefinite updates or support. A subscription normally provides permission for a defined period, sometimes bundled with maintenance or hosted services.\n\nTechnical deployment can complicate these measurements. A virtual machine is not necessarily treated like a physical server, and moving workloads between hosts may affect processor-based counts. Containers and automated scaling can create many short-lived instances without a corresponding increase in human users. Some enterprise licenses address indirect access, in which people or external systems interact with licensed software through another application. Whether that access requires additional entitlements depends on the agreement’s definitions, not simply on whether a person directly opens the licensed program.\n\nPayment and permission are also distinct from enforcement technology. Product keys, activation servers, hardware dongles, and account checks can limit access, but they do not by themselves express the full legal scope of a license. Digital rights management may prevent an activity that is legally permitted, or fail to prevent one that is prohibited. Commercial agreements therefore often address activation failures, license-server outages, transfer procedures, and continued operation after maintenance ends. Source-code escrow is another arrangement: a third party holds source materials for release upon defined events, without necessarily granting unrestricted rights to use them."
    },
    {
      "heading": "Free and open-source licensing",
      "text": "Free software and open-source software describe overlapping categories of software whose licenses grant broad freedoms to use, inspect, modify, and redistribute code. The Free Software Foundation emphasizes users’ freedoms, while the Open Source Initiative evaluates licenses against the Open Source Definition. These approaches differ in their institutional histories and explanations, but many widely used licenses satisfy both. “Free” in this context concerns freedom rather than a required price of zero.\n\nOpen-source licensing does not prohibit commercial activity. Recipients can generally sell copies, provide paid support, build products around the software, or charge for hosting, subject to the applicable conditions. A license restricting use to research, forbidding commercial use, or excluding particular industries does not meet the Open Source Definition. Similarly, software made available only for viewing is not necessarily open source: the rights to modify and redistribute are essential parts of the category.\n\nPermissive licenses impose relatively limited conditions on reuse. The MIT License, for example, permits a broad range of activities while requiring preservation of its copyright and permission notice in copies or substantial portions of the software. Common BSD licenses likewise require specified notices and disclaimers; the three-clause BSD license also restricts use of contributors’ names to endorse derived products without permission. Such licenses generally allow incorporation into proprietary products without requiring disclosure of the product’s source code.\n\nThe Apache License version 2.0, published in 2004, is another prominent permissive license, but it contains more detailed provisions. It includes an express patent license from contributors for certain patent claims implicated by their contributions, together with patent-litigation termination provisions. Its redistribution requirements address license copies, notices of changes, attribution, and preservation of relevant material in a NOTICE file when one exists. These details make “permissive” a family resemblance rather than a statement that all such licenses are interchangeable.\n\nMost standard open-source licenses also contain warranty disclaimers and limitations of liability, subject to applicable law. Broad permission to reuse code is therefore separate from an assurance that it works, is secure, or is suitable for a particular purpose. A supplier can offer commercial warranties or indemnities alongside open-source software, but those promises arise from an additional undertaking. Likewise, Creative Commons licenses are widely used for documentation and cultural materials, but their standard licenses are generally not recommended by Creative Commons for software, whose licensing often requires software-specific treatment of source code and patents."
    },
    {
      "heading": "Copyleft, source disclosure, and reciprocity",
      "text": "Copyleft is a licensing technique that allows copying, modification, and redistribution while requiring specified downstream distributions to preserve defined freedoms. Its mechanism depends on copyright: permission to distribute protected material is conditioned on compliance with reciprocal terms. Copyleft is therefore not an abandonment of copyright and does not mean that software has no owner. Its principal purpose is to prevent recipients from receiving covered software under terms that remove the freedoms the license grants.\n\nThe GNU General Public License is the best-known strong copyleft license. When covered software is conveyed in object-code form, its terms require corresponding source to be provided through one of the permitted mechanisms. Corresponding source is more specific than a selection of files: depending on the license version and circumstances, it includes source needed to generate, install, run, or modify the covered work, with defined exclusions. GPL version 3 also contains installation-information requirements for certain object-code distributions in “User Products,” subject to the license’s conditions and exceptions.\n\nRunning a GPL-covered program privately does not by itself require publication of modifications. Internal use within an organization is different from distributing copies to separate legal persons, although organizational structure and arrangements with contractors can complicate that distinction. Nor does merely placing independent programs on the same storage medium necessarily bring every program under the GPL. The relevant analysis concerns the scope of the covered work and the legal and technical relationship between components, not their physical proximity alone.\n\nWeaker or more limited forms of copyleft use different boundaries. The GNU Lesser General Public License permits specified combinations with non-LGPL applications while protecting the covered library and preserving particular user rights; its requirements depend on the version and method of combination. The Mozilla Public License 2.0 generally applies source-disclosure obligations at the covered-file level, allowing larger works to contain differently licensed files. Describing either license only as “less restrictive than GPL” obscures the concrete obligations governing modifications, notices, and redistribution.\n\nThe GNU Affero General Public License version 3 addresses a further situation: interaction with modified software over a network. Its additional provision requires a modified version supporting remote network interaction to offer interacting users an opportunity to receive its corresponding source. Ordinary GPL licensing does not impose an equivalent general network-interaction requirement. Even under strong copyleft, however, source obligations attach to the covered software and relevant combinations; they do not automatically require disclosure of unrelated business records, user data, or every program operated by the same organization."
    },
    {
      "heading": "Compatibility, combined works, and multiple licensing",
      "text": "License compatibility concerns whether software under different licenses can be combined and distributed while satisfying all applicable terms. It is not the same as technical compatibility: two libraries may function together perfectly but carry conflicting legal requirements. Conversely, software under different licenses may be distributed together lawfully when the licenses’ conditions can coexist. The first task is to determine which acts occur—copying, modification, linking, distribution, or network operation—and which license provisions those acts engage.\n\nPermissive code can often be incorporated into a copyleft-covered work, provided its notices and other conditions are preserved. This does not erase the original license from the incorporated code; rather, the distribution must meet the relevant obligations for each part and for the combined work. Compatibility can be directional. Apache License 2.0 code can generally be included in a GPL version 3 combination, but the same combination is not generally compatible with GPL version 2-only terms because of differences in their conditions.\n\nLicense versions therefore matter. “GPL version 2 only” and “GPL version 2 or any later version” give different permissions: the latter allows recipients to select a later GPL version, while the former does not. Exceptions also matter. A copyright holder may supplement a copyleft license with a linking exception or another defined permission that allows a combination otherwise restricted. These exceptions must be read as grants covering specified circumstances, not as general cancellations of the underlying license.\n\nThe legal boundary of a derivative work is particularly significant for combined software. Static linking, dynamic linking, plug-in interfaces, interprocess communication, and network protocols produce different technical relationships, but no single technical label settles every copyright question across jurisdictions. Some licenses explicitly address particular forms of combination; others rely more heavily on copyright concepts. Claims that all dynamic linking is exempt from copyleft, or that any communication between programs extends copyleft to both, are consequently too broad.\n\nDual licensing offers the same software under alternative sets of terms. A rights holder might provide a copyleft option and a proprietary option for recipients who want different redistribution rights. This model requires authority to grant both alternatives. Projects receiving contributions from many people may rely on contributor agreements, copyright assignments, or permissions already sufficient for the proposed licensing. A contributor license agreement can grant broader relicensing powers, while a Developer Certificate of Origin generally records a contributor’s certification of authority to submit the contribution under the indicated project terms; these mechanisms are not equivalent."
    },
    {
      "heading": "Hosted services, source-available models, and digital distribution",
      "text": "Software as a service changes the object of many software transactions. A customer may use an application through a browser or application programming interface without receiving a copy of the server program. The principal agreement then concerns access to a service, although downloadable clients, software development kits, and locally installed agents may have separate licenses. Service terms commonly address uptime, account restrictions, data handling, suspension, and export of customer information rather than only rights to copy code.\n\nThis architecture matters because many license obligations are triggered by distribution or conveyance of software copies. Operating a modified GPL-covered application on a server does not, solely because users interact with it remotely, create the same source-disclosure requirement as conveying covered executable copies. The AGPL’s network provision addresses a defined part of this situation. Other licenses expressly regulate offering software functionality to third parties, but a service restriction can prevent a license from qualifying as open source.\n\nSource-available software makes source code accessible while reserving rights that free and open-source licenses would grant. Restrictions may concern production use, competitive hosting, particular commercial activities, or redistribution. The Business Source License is an example of a framework in which initial restrictions give way on a specified change date to a designated license, subject to the applicable text and parameters. This differs from software that is open source immediately and remains available under an established open-source grant.\n\nTerminology can obscure these distinctions. “Community edition,” “developer edition,” and “shared source” are product or program descriptions rather than reliable legal categories. An “open core” business model typically combines an open-source core with separately licensed proprietary features, but the boundary varies by product. A product can also change the license of future releases while earlier releases remain available under their original terms. A newly announced licensing policy does not simply replace permissions already validly granted for old versions.\n\nApplication stores add another contractual layer. Developers may face distribution agreements, platform rules, signing requirements, and payment conditions in addition to the licenses governing their own code and dependencies. Restrictions imposed through a store can conflict with licenses that prohibit additional restrictions on recipients. Hosted services also raise data privacy questions that software licenses alone do not resolve: authorization to run an application is separate from the legal basis for processing personal data, allocating controller and processor responsibilities, or transferring information across borders."
    },
    {
      "heading": "Contract formation, enforcement, and statutory limits",
      "text": "The enforceability of software terms depends partly on how they are presented and accepted. A negotiated agreement usually supplies a relatively clear record, but mass-market distribution often relies on a standard-form contract. “Shrinkwrap” terms accompany packaged software, “clickwrap” requires an affirmative action such as selecting an acceptance box, and “browsewrap” purports to bind a user through use of a website or service. Courts examine notice, assent, and the surrounding transaction rather than treating these labels as conclusive.\n\nIn the United States, ProCD, Inc. v. Zeidenberg in 1996 upheld shrinkwrap terms in the circumstances before the Seventh Circuit. In Specht v. Netscape Communications Corp. in 2002, the Second Circuit found that terms insufficiently brought to users’ attention did not form the asserted agreement. These decisions illustrate the importance of interface design and notice, but neither establishes that all software terms are enforceable or unenforceable. Applicable consumer protection rules, mandatory statutory rights, and doctrines controlling unfair terms remain relevant.\n\nOpen-source license conditions can also be legally enforceable. In Jacobsen v. Katzer in 2008, the Federal Circuit held that conditions in the Artistic License could support copyright remedies, rejecting the idea that the absence of a monetary license fee made the conditions legally insignificant. The case highlighted the economic value of attribution and reciprocal participation. In MDY Industries, LLC v. Blizzard Entertainment, Inc. in 2010, the Ninth Circuit distinguished contractual covenants from license conditions linked to copyright rights, illustrating why not every breach supports an infringement claim.\n\nTransfer and resale create further jurisdictional differences. In UsedSoft GmbH v. Oracle International Corp. in 2012, the Court of Justice of the European Union held that the distribution right could be exhausted for certain downloaded software supplied with an unlimited-duration right of use in exchange for a fee corresponding to the copy’s economic value. The ruling imposed important qualifications, including that the original acquirer must render its own copy unusable upon resale. It did not establish an unrestricted right to divide licenses or resell every subscription or digital service.\n\nConsequences of noncompliance depend on the claim and governing law. They can include termination, damages, or an injunction, but licenses differ in notice and cure provisions. GPL version 3, for example, provides specified routes to reinstatement following cessation of a violation. Warranty disclaimers and liability limits may also be constrained by mandatory law. Cross-border transactions add private international law questions about governing law, forum, and enforcement; a contractual choice-of-law clause does not necessarily displace every mandatory rule applicable to the transaction."
    },
    {
      "heading": "License compliance and software supply chains",
      "text": "Modern applications often depend on hundreds or thousands of components obtained directly or through other dependencies. License compliance therefore concerns a software supply chain, not merely the agreement for the final application. A supplier may have rights to distribute its own code but lack required permissions or source materials for an included component. Generated code, copied snippets, vendored libraries, container images, and build tools can introduce additional obligations, although the legal significance of each depends on how it is used and distributed.\n\nA central compliance task is establishing provenance: identifying a component’s origin, version, applicable license, and modifications. Repository metadata and package-manager labels are useful evidence but can be incomplete or inaccurate. A top-level license file may not cover embedded third-party files, and a package may include code under multiple licenses. Automated scanners can detect known license texts and similarities, but their results require interpretation, especially where a license is absent, a file carries an exception, or the project has changed licensing between releases.\n\nA software bill of materials, or SBOM, records information about software components and their relationships. It can support licensing analysis as well as cybersecurity work, but it is not itself proof of legal compliance. SPDX, developed through a Linux Foundation project, supplies a specification for exchanging software information and a standardized license list. SPDX 2.2.1 was published as ISO/IEC 5962:2021. Its license-expression syntax distinguishes, for example, alternatives using OR, combined obligations using AND, and specified exceptions using WITH.\n\nPractical compliance outputs vary by license. They may include copyright notices, license texts, attribution files, source archives, written source offers, or build and installation materials. Delivery methods matter: a source offer valid under one GPL provision is not interchangeable with every other source-distribution method. When binaries are passed through distributors or incorporated into devices, responsibilities can extend beyond the original developer. ISO/IEC 5230:2020, based on the OpenChain specification, describes requirements for an open-source license compliance program rather than certifying that every individual component is legally unproblematic.\n\nLicense records also affect acquisitions, outsourcing, and long-term maintenance. A purchaser of a software business may need to distinguish owned code from licensed dependencies and identify whether contributor permissions support the intended distribution model. Supplier termination or discontinued activation infrastructure can expose differences between possession of software and a durable ability to operate it. For artificial intelligence systems, code, model weights, training datasets, and hosted interfaces may each carry separate terms; calling an entire system “open” does not establish that the same permissions apply to all these layers."
    }
  ],
  "links": [
    "intellectual-property-licensing",
    "copyright",
    "contract-law",
    "united-states",
    "trips-agreement",
    "gnu-general-public-license",
    "algorithm",
    "intellectual-property-infringement",
    "fair-use",
    "european-union",
    "patent",
    "trade-secret",
    "trademark",
    "public-domain",
    "free-software",
    "open-source-software",
    "mit-license",
    "apache-license",
    "creative-commons",
    "copyleft",
    "software-as-a-service",
    "application-programming-interface",
    "data-privacy",
    "personal-data",
    "standard-form-contract",
    "consumer-protection",
    "court-of-justice-of-the-european-union",
    "damages",
    "injunction",
    "private-international-law",
    "cybersecurity",
    "artificial-intelligence"
  ],
  "sources": [],
  "license": "https://creativecommons.org/licenses/by/4.0/"
}