oss-review

Classify dependency licenses and map obligations to deployment modes.

183|37|Updated May 15, 2026
One-click install
npx skills add https://github.com/zhou210712/claude-for-legal-ZH --skill oss-review-zhou210712
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-review
Source: https://github.com/zhou210712/claude-for-legal-ZH/tree/main/ip-legal/skills/oss-review
Command: npx skills add https://github.com/zhou210712/claude-for-legal-ZH --skill oss-review-zhou210712

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the risk of accidentally violating open-source license obligations when you review dependencies, assess a single library, or prepare code for public release.

Core Features & Use Cases

  • Dependency & release scope review: Classifies licenses across a dependency list, a single repository, or code you plan to publish publicly.
  • Deploy-mode obligation mapping: Translates license duties into practical actions based on whether you run SaaS, distribute binaries, use internally, or embed in devices.
  • Copyleft and unknown-license guardrails: Flags strong copyleft and license-unknown cases for attorney review, and checks compatibility for outbound code licensing.

Example use case: you are about to ship a product that includes multiple transitive dependencies, and you need a per-package compliance memo (what obligations trigger, the severity, and the next action) before launch.

Quick Start

Run oss-review on your dependency file to get a license-by-package compliance memo and release actions for the chosen deployment mode.

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 dependencies before a public release?

Open-source license compliance review classifies dependencies across your list or repository, mapping obligations to your deployment mode to produce a per-package memo with triggered duties, severity, and next actions before shipping.

What happens when a dependency has a strong copyleft or unknown license during an SBOM review?

During an SBOM review, strong copyleft and unknown licenses are flagged as guardrails for attorney approval, while non-OSI licenses are categorized as needing further review before proceeding.

Can I map open-source license obligations to different deployment modes like SaaS or embedded devices?

Yes, license compliance review translates license duties into practical actions based on whether you run SaaS, distribute binaries, use internally, or embed in devices, tailoring obligations to your deployment mode.

Does open-source license review work for outbound code I plan to publish publicly?

Yes, license compliance review applies to outbound code you plan to publish or distribute publicly, checking compatibility for outbound code licensing and mapping obligations for your release.

What's the best way to review transitive dependencies for license violations before product launch?

The best way to review transitive dependencies is running a compliance review that reads actual license texts, classifies each package, and produces an approval-oriented memo detailing obligations and severity for launch readiness.

Why does my license compliance review require loading a team practice profile?

Loading a team practice profile is required because it provides the organizational context and policy thresholds needed to classify dependencies and map license obligations to your deployment mode.