oss-review

Classify open source licenses and assess compliance obligations from dependency lists.

2|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/alexchlou/codex-for-legal --skill oss-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-review
Source: https://github.com/alexchlou/codex-for-legal/tree/main/plugins/ip-legal/skills/oss-review
Command: npx skills add https://github.com/alexchlou/codex-for-legal --skill oss-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs a comprehensive open source license review of dependency lists, individual libraries, or outbound code to identify licensing obligations and potential risks, preventing legal issues.

Core Features & Use Cases

  • License Classification: Reads actual license texts of dependencies to categorize permissions, copyleft strength, and license compatibility.
  • Obligation Assessment: Maps identified licenses to deployment scenarios—SaaS, binary, internal use, or embedded—and details specific compliance requirements.
  • Use Case: A legal team audits third-party dependencies across multiple repositories to confirm license compatibility and prepare compliance reports before open sourcing or redistribution.

Quick Start

Load your dependency manifest, specify the deployment model, and the skill will analyze license obligations and generate a compliance 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 involves analyzing dependency manifests to classify license types and assess obligations. You can map identified licenses to deployment scenarios like SaaS or binary distribution to identify potential legal risks before redistribution.

What is a copyleft license risk assessment for outbound code?

A copyleft risk assessment for outbound code reads license texts to categorize permissions and copyleft strength. This process identifies licensing obligations and compatibility risks before you open source or redistribute your software.

How do I generate an open source compliance report for multiple repositories?

To generate a compliance report, load dependency manifests from your repositories and specify your deployment model. The analysis maps identified licenses to requirements and generates a compliance memo confirming compatibility.

Does the license review process work for SaaS and embedded deployment contexts?

Yes, the license review process works for SaaS and embedded deployment contexts. It maps identified open source licenses to your specific deployment scenario, detailing the exact compliance requirements and obligations for each context.

When do I need an open source legal review of my third-party libraries?

You need an open source legal review of third-party libraries before open sourcing, redistribution, or embedding them. It identifies licensing obligations and potential risks by analyzing actual license texts against your deployment model.