More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Open Source License Check

    1

    One AGPL-3.0 package in node_modules can oblige a closed-source SaaS to offer its own source code to every user, and one CC-BY-NC icon set makes a paid product break its license.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Open Source License Check

    Open Source License Check

    Example session with this skill installed

    Check this project with open-source-license-check.

    • Read your context and instructions
    • Compiled the open source license

    $ python3 scripts/check_licenses.py examples/risky
    BLOCK package-lock.json:32 L01 NETWORK_COPYLEFT_IN_CLOSED_PROJECT
    "license": "AGPL-3.0-only" [node_modules/chartwell-server: network copyleft; project closed: package.json "private": true, no license]
    Why: A runtime dependency uses a network copyleft license (AGPL, SSPL, EUPL, OSL, RPL, CPAL, APSL, Parity, CAL) and this project is closed source. These licenses can require you to offer the source code of the whole program, your code included, to everyone who uses it over a network, not only to people you ship it to. SSPL goes further: offering the program as a service means releasing the code of the whole service around it.
    Safer: Replace it with a permissively licensed package, buy a commercial license if the author sells one, or get a lawyer's sign-off on exactly how you use it. If the project is open source, declare its license so the checker treats it that way.

    BLOCK package-lock.json:48 L02 NONCOMMERCIAL_LICENSE
    BLOCK package-lock.json:62 L03 BUSL_BEFORE_CHANGE_DATE
    REVIEW package-lock.json:27 L12 WEAK_COPYLEFT_DEPENDENCY
    REVIEW package-lock.json:37 L11 COPYLEFT_DEPENDENCY
    REVIEW package-lock.json:57 L13 USE_RESTRICTED_DEPENDENCY
    REVIEW packages/cli/package.json:4 L16 LICENSE_FILE_MISSING
    REVIEW packages/sdk/package.json:2 L15 PROJECT_LICENSE_NOT_DECLARED
    REVIEW packages/ui/package.json:4 L16 LICENSE_FILE_MISSING
    REVIEW packages/ui/package.json:4 L17 INVALID_LICENSE_EXPRESSION
    REVIEW packages/widgets/LICENSE:1 L18 LICENSE_MISMATCH
    REVIEW services/billing/composer.lock:19 L11 COPYLEFT_DEPENDENCY
    REVIEW services/ml/pypackages/3.12/lib/dateparse_legacy-0.2.0.dist-info/METADATA:2 L14 DEPENDENCY_LICENSE_UNKNOWN
    REVIEW services/ml/pypackages/3.12/lib/pdfmine-0.9.2.dist-info/METADATA:8 L12 WEAK_COPYLEFT_DEPENDENCY

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 13 files, 13 with license or manifest content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

    BLOCK package-lock.json

    Connects securely to your tools. The creator never sees your data.

    About this skill

    One AGPL-3.0 package in node_modules can oblige a closed-source SaaS to offer its own source code to every user, and one CC-BY-NC icon set makes a paid product break its license. This skill finds those and nine other license problems in your project and its dependencies before you ship, and tells you what to check for each one.

    Your agent runs a scanner on your project folder. It first reads the project's own license (package.json, pyproject.toml, composer.json, Cargo.toml and the LICENSE file text) and works out whether the project is closed source (UNLICENSED, proprietary, no license) or open source ("private": true alone only means "do not publish to npm"), then reads every installed dependency: node_modules (npm, pnpm, Yarn, Bun), *.dist-info/METADATA in a virtualenv, Composer's vendor folder, or package-lock.json and composer.lock when nothing is installed. It understands SPDX expressions (for "A OR B" you may pick the more permissive one; "A AND B" means both apply; GPL linking exceptions count as weak copyleft), npm's old license objects and SEE LICENSE IN, Python License-Expression, License and classifiers, and dev-only dependencies. It never runs npm, pip or composer, and never uses the network. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. It is not legal advice.

    What it checks

    BLOCK (closed-source projects)

    • L01: AGPL, SSPL, EUPL, OSL and other network copyleft runtime dependencies
    • L02: non-commercial licenses (CC-BY-NC, PolyForm Noncommercial, Commons Clause)
    • L03: Business Source License (BUSL-1.1) packages before their Change Date

    REVIEW

    • L11: GPL dependencies, and network copyleft in open-source projects or dev tools
    • L12: LGPL, MPL, EPL and other weak copyleft runtime dependencies in closed-source projects
    • L13: Elastic-2.0, PolyForm Small Business, JSON and other use-restricted licenses
    • L14: dependencies with no license, a custom license or an unrecognized one
    • L15: a publishable package that declares no license
    • L16: an open-source license declared with no LICENSE file
    • L17: a project license that is not a valid SPDX expression ("Apache 2.0", "GPLv3")
    • L18: a LICENSE file or second manifest that disagrees with the declared license

    What's included

    • The scanner (Python 3.9+, standard library only), with the SPDX license list built in
    • A rules guide with the reason and safer approach for each rule
    • A risky and a safe example project (npm lockfile, Python packages and Composer), and the real report the scanner produces on the risky one

    Limits It reads license metadata as written: license headers in source files, how a dependency is used (bundled, linked, separate program), compatibility between two open-source licenses, Rust, Go, Java, .NET and Ruby dependencies, and Yarn Plug'n'Play caches are not checked. Whether the project is closed source is inferred from its manifests. It is not legal advice, and NOT FLAGGED is not a guarantee.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.

    Static check of license metadata, not legal advice. Dependencies must be installed or locked to be checked; Rust, Go, Java, .NET and Ruby dependencies are not covered. NOT FLAGGED is not a guarantee.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Software
    Python

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. Inside node_modules, virtualenvs and vendor it reads only package manifests (package.json, METADATA, installed.json, composer.json), plus a package's own LICENSE file when its license points to it or is BUSL. The example projects use made-up packages and companies. Nothing is run.

    Listed5 days ago
    Updated4 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. It reports licence facts it reads from your manifests and lock files so you can review them. It is not legal advice.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    New in Code Quality & Review