oss-review

Name: oss-review
Availability: InStock
Author: polliticalsolutions

Classifies license families and maps compliance obligations to a deployment model, returning a structured legal memo.

Updated Dec 4, 2025

Search Tags:#license compliance #sbom #copyleft #legal memo #outbound licensing #oss review #non-osi

Ready to run

npx skills add https://github.com/PolliticalSolutions/political-portal --skill oss-review-polliticalsolutions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oss-review
Source: https://github.com/PolliticalSolutions/political-portal/tree/main/.claude/skills/ip-legal/oss-review
Command: npx skills add https://github.com/PolliticalSolutions/political-portal --skill oss-review-polliticalsolutions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you determine what open source (and non-OSI) licenses exist in a dependency tree and what legal obligations they create for how your software will be deployed, reducing the risk of shipping something that must be replaced, removed, or escalated to attorneys.

Core Features & Use Cases

Classifies dependencies by license family (permissive, weak copyleft, strong copyleft, public domain, non-OSI/source-available, unknown) with license-unknown and non-OSI clearly flagged for review.
Maps obligations to your deployment model (SaaS, distributed binary, internal-only, embedded/firmware) so the same dependency set can produce different outcomes depending on delivery.
Produces a lawyer-ready memo summarizing a bottom line, per-package severity, jurisdiction notes, and (when reviewing outbound code) compatibility checks for the chosen outbound license.

Quick Start

Run the oss-review skill on a dependency manifest such as package.json to generate a deployment-aware 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 before shipping software?▼

Open source license compliance is checked by analyzing your dependency list or SBOM to classify licenses and identify copyleft obligations. The review maps these obligations to your deployment model, producing a structured legal memo with per-package severity and escalation flags.

What is a copyleft license risk and how does it affect software distribution?▼

Copyleft license risk affects software distribution by requiring you to open source derived code under the same license. Strong copyleft dependencies limit how you deploy and ship binaries, often requiring legal review before you can safely distribute your software to end users.

Does license compliance differ between SaaS and distributed binary deployments?▼

License compliance differs between SaaS and distributed binary deployments because the same dependency set triggers different legal obligations. SaaS models may avoid copyleft triggers that distributed binaries or embedded firmware cannot, requiring deployment-aware mapping for an accurate compliance assessment.

How do I prepare outbound code for open-sourcing with compatibility checks?▼

Preparing outbound code for open-sourcing requires reviewing your dependency tree to check license compatibility against your chosen outbound license. This identifies conflicting obligations or strong copyleft requirements, producing a lawyer-ready memo with jurisdiction notes and escalation flags.

What happens when an SBOM contains non-OSI or unknown licenses?▼

When an SBOM contains non-OSI or unknown licenses, the compliance review clearly flags them for manual review. These dependencies require escalation to legal counsel because their source-available terms or unclassified obligations cannot be automatically approved for your deployment model.