Security

License and SPDX Finder

Find SPDX identifiers, copyright lines and license headers in pasted text and read what the licenses say in plain words. Not legal advice. Runs in your browser.

Guide: SPDX License Identifiers: Read MIT OR Apache-2.0

Your text stays in your browser. The pattern search runs on your device. Nothing is uploaded, stored or put in the URL. This tool is not legal advice.
Ready. Paste text that may contain a license header, an SPDX line or a copyright line. Nothing is sent or stored.

Result

Read this first.
  • This is not legal advice.
  • It cannot tell whether code was copied from somewhere else, or whether a marker is true.
  • Not finding a marker means nothing about the license of the text.

What it does

Paste a file header, a LICENSE or COPYING file, a package.json or Cargo.toml, or any text that may carry a license marker. The tool lists the markers it finds with their line numbers, shows copyright lines, and gives a short plain-words summary of each license it recognises: whether it is permissive or copyleft and what its main obligations are. The report can be copied as Markdown.

What it checks

  • SPDX-License-Identifier lines in any comment style, including expressions with AND, OR, WITH and parentheses, such as (MIT OR Apache-2.0) or GPL-2.0-only WITH Classpath-exception-2.0. The expression is read with the SPDX rules (WITH binds first, then AND, then OR) and explained in a sentence. A broken expression is reported with the reason.
  • License fields such as "license": "MIT" in package.json, license = "MIT OR Apache-2.0" in Cargo.toml or License: in package metadata.
  • Copyright lines such as Copyright (c) 2021 Name, (C) 2019 Name and SPDX-FileCopyrightText. The holder is shown as written and is not checked.
  • Standard header or full text of MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, 0BSD, GPL-2.0, GPL-3.0, LGPL-2.1, LGPL-3.0, AGPL-3.0, MPL-2.0, EPL-2.0, BSL-1.0, zlib, the Unlicense, CC0 and the Creative Commons Attribution licenses (BY, BY-SA, BY-NC, BY-ND, BY-NC-SA, BY-NC-ND). For BSD texts the tool counts the conditions to tell the 2-clause, 3-clause and advertising-clause forms apart, and for the GNU licenses it reads “this version only” or “or any later version” from the header.
  • Titles, links and mentions such as “The MIT License”, a link to apache.org/licenses or “released under the MIT license”. These are marked as weaker evidence because a name or a link is not the license text.

What it cannot catch

  • This is not legal advice. The summaries say what common license texts say in plain words. They leave out details. Read the license itself, and ask a lawyer when it matters.
  • Copied code. The tool cannot tell whether code was copied from somewhere else, or whether a license marker was added, removed or changed by someone.
  • Absence means nothing. A text with no marker is not necessarily free to use, and a text with a marker may be labeled wrongly.
  • Other licenses. Licenses that are not in the table are shown by name only. An identifier the tool does not know may still be a valid SPDX identifier.
  • Compatibility. The tool does not judge whether several licenses can be combined. It only warns that more than one was found.
  • Modified texts. A license text that was edited, translated or only partly pasted may not be recognised, or may be recognised as a nearby license. Matching is by fixed phrases, so every result is a heuristic.
  • Text up to 500,000 characters is read. At most 200 SPDX lines, 100 copyright lines and 300 other markers are listed.

How to read the results

  • Strong means a standard license text, an SPDX identifier or a license field was found. Weaker means only a name, a title or a link was found.
  • OR means the recipient may choose one of the licenses. AND means every license applies. WITH adds a named exception to a license.
  • A + after an identifier, or -or-later, means the text also allows later versions of that license.
  • Look-alike text, such as a person studying at MIT, the Apache helicopter or ordinary sentences about copyright, is not reported as a license.

Example

The example loads a header with an SPDX line, a copyright line and a GPL notice. The result shows the SPDX expression in words, the GPL header as “or any later version” and the summaries for the licenses involved. Related checks: the AI Output Sanity Check looks for license markers in pasted code as one of its steps, the Dependency Change Reviewer and the Package Existence Checker review packages, and the Secret Scanner looks for keys that should not be shared.

Privacy

This tool runs entirely in your browser. What you paste or open is processed on your device and is not sent to a server. The page does not write your input to local storage, cookies or the URL, and the tool does not send your input anywhere. The text is read as plain text only and is never run or shown as HTML.

Share this tool

Your data is not included in this link.