oss-review

Classify dependency licenses and generate attorney-routable compliance memos.

100|16|Updated May 13, 2026
One-click install
npx skills add https://github.com/ZekaiSuni/claude-for-legal-turkish --skill oss-review-zekaisuni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-review
Source: https://github.com/ZekaiSuni/claude-for-legal-turkish/tree/main/ip-legal/skills/oss-review
Command: npx skills add https://github.com/ZekaiSuni/claude-for-legal-turkish --skill oss-review-zekaisuni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps legal and engineering teams assess open source license compliance risk for third-party dependencies so they can confidently decide whether a component can be used, replaced, or must be escalated.

Core Features & Use Cases

  • License classification with deployment-aware obligations: Classifies packages into permissive, weak copyleft, strong copyleft, public domain, non-OSI, or unknown, then maps obligations to your deployment model (SaaS, distributed binary, internal only, or embedded).
  • Policy-driven first-pass memo for attorneys: Produces a lawyer-actionable memo that flags license-unknown and non-OSI licenses and routes strong-copyleft/unknown findings for attorney review.
  • Outbound open-sourcing compatibility check: When reviewing outbound code, validates that the chosen outbound license is compatible with every embedded dependency and that required notices/license texts are present.

Quick Start

Run the oss-review scan for a dependency manifest by pointing it at your package file or by giving the repo path you want analyzed.

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 software dependencies before shipping?

To check open source license compliance before shipping, scan your dependency manifest or SBOM to classify packages by license type and map their obligations to your specific deployment model. This process identifies which copyleft or non-OSI licenses impose source-disclosure requirements.

What is deployment-aware open source license review and when do I need it?

Deployment-aware open source license review evaluates third-party dependencies against your specific release type, such as SaaS, distributed binary, or embedded firmware. You need it to determine which copyleft or unknown licenses trigger shipping or source-disclosure obligations.

How do I audit an SBOM for copyleft licenses and source disclosure obligations?

Auditing an SBOM for copyleft licenses involves validating actual license texts and classifying each dependency into categories like permissive, weak copyleft, or non-OSI. This classification flags packages that require source disclosure or attorney review before deployment.

Can I verify if my chosen outbound open source license is compatible with embedded dependencies?

Yes, you can verify outbound open source license compatibility by scanning your outbound code to ensure the chosen license aligns with every embedded dependency. The review validates that required notices and license texts are present for distribution.

Does open source license review work for SaaS, distributed binaries, and embedded deployment models?

Open source license review works across SaaS, distributed binary, internal-only, and embedded deployment models. It maps the obligations of permissive, weak copyleft, and strong copyleft licenses to your specific deployment context to determine shipping constraints.

How do I generate an attorney-routable compliance memo for unknown OSS licenses?

Generating an attorney-routable compliance memo involves scanning your dependencies to flag license-unknown and non-OSI packages. The resulting policy-driven memo routes strong-copyleft and unknown findings directly to attorneys for clearance review.