oss-review

Classify dependency licenses and map copyleft obligations to deployment models.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

oss-review helps you identify open source license compliance risks in a dependency set so you can avoid shipping code that triggers copyleft obligations or uses non-OSI “open source” licenses.

Core Features & Use Cases

  • License classification by dependency: Categorizes packages into permissive, weak copyleft, strong copyleft, public domain, non-OSI source-available, or unknown and flags uncertain items for review.
  • Deployment-model obligation mapping: Translates license obligations into the specific delivery model (SaaS, distributed binaries, internal only, or embedded/firmware) to show what actually triggers.
  • Outbound code compatibility check: When reviewing code you plan to open-source, verifies the proposed outbound license is compatible with embedded dependencies and highlights required bundling/attribution.
  • Attorney-ready memo output: Produces a structured memo with top-of-memo flags, per-package severity blocks, and approval routing notes.

Quick Start

Ask oss-review to scan your project's dependency manifest by running: /ip-legal:oss-review ~/code/my-project/package.json

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 a software dependency manifest?

Open source license compliance scanning categorizes dependencies into permissive, copyleft, and non-OSI classifications, mapping obligations to your deployment model to flag clearance risks before shipping binaries or SaaS.

What is copyleft analysis and when do I need it for outbound code?

Copyleft analysis for outbound code verifies whether your proposed open-source license is compatible with embedded dependencies. You need it when preparing to open-source a repository to ensure required attribution and bundling obligations are met.

How do I generate an attorney-ready memo from an SBOM review?

Generating an attorney-ready memo from an SBOM review involves mapping dependency licenses to your delivery model and structuring the findings with top-of-memo flags, per-package severity blocks, and escalation triggers for unknown licenses.

Does license obligation mapping change between SaaS and distributed binaries?

License obligation mapping translates open source requirements into specific delivery models like SaaS, distributed binaries, or embedded firmware. The obligations that trigger compliance actions vary significantly depending on whether the software is distributed or hosted.

How do I handle unknown or non-OSI source-available licenses in my dependencies?

Handling unknown or non-OSI source-available licenses requires flagging uncertain packages for review and escalating them in the compliance memo. The scan categorizes these dependencies separately to trigger approval routing notes.