oss-review

Name: oss-review
Availability: InStock
Author: gtgspot

Classify open-source licenses and map obligations to deployment models.

Updated May 28, 2026

Search Tags:#dependencies #compliance #license #open-source #oss #legal-review

Ready to run

npx skills add https://github.com/gtgspot/clegal --skill oss-review-gtgspot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oss-review
Source: https://github.com/gtgspot/clegal/tree/main/ip-legal/skills/oss-review
Command: npx skills add https://github.com/gtgspot/clegal --skill oss-review-gtgspot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open source license compliance for a dependency list, a single library, or outbound code, to determine license families, obligations, and whether a library can ship.

Core Features & Use Cases

Classifies dependencies by license family (permissive, weak copyleft, strong copyleft, public domain, non-OSI, unknown) after validating actual license texts.
Maps license obligations to deployment models (SaaS, distributed binary, internal, embedded) and flags licenses requiring attorney review or replacement.
Outputs a structured memo with per-package guidance and escalation routes suitable for legal and engineering teams.

Quick Start

Provide the project manifest or repository path to analyze; I will classify licenses, surface deployment obligations, and prepare a readiness memo.

Frequently Asked Questions about oss-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check open-source license compliance for my project dependencies?▼

Open-source license compliance is checked by identifying and classifying licenses in a dependency list or codebase to surface obligations. This process validates actual license texts, maps requirements to deployment models, and outputs a structured readiness memo.

What is the difference between weak copyleft and strong copyleft open-source licenses?▼

Copyleft open-source licenses are classified as weak or strong based on their obligation levels. Strong copyleft requires derivative works to open-source under the same license, while weak copyleft applies obligations to the original library but not necessarily the entire outbound codebase.

Can I analyze a package.json or requirements.txt file to see if a library can ship?▼

Yes, you can analyze manifests like package.json, requirements.txt, and go.mod to determine if a library can ship. The analysis reads actual license texts, flags libraries requiring replacement or attorney review, and prepares per-package guidance for engineering and legal teams.

Does open-source license obligations vary between SaaS and distributed binary deployments?▼

Open-source license obligations vary significantly between SaaS, distributed binary, internal, and embedded deployment models. The compliance review maps specific license requirements to your exact deployment method, flagging obligations like attribution or source code disclosure.

How do I do an open-source legal review for outbound code I am open-sourcing?▼

An open-source legal review for outbound code identifies and classifies all included dependencies to determine if the code can ship. It validates actual license texts, maps obligations, and outputs a structured memo with clear remediation and escalation guidance.