revisor-licencias-oss

Classify open-source software licenses and determine copyleft strength from dependency inventories.

35|19|Updated May 15, 2026

Search Tags:#license compatibility #software governance #sbom #compliance checklist #oss licensing #copyleft risk #saaS compliance

Ready to run

npx skills add https://github.com/betobetico/claude-para-abogados --skill revisor-licencias-oss

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: revisor-licencias-oss
Source: https://github.com/betobetico/claude-para-abogados/tree/main/propiedad-intelectual/skills/oss
Command: npx skills add https://github.com/betobetico/claude-para-abogados --skill revisor-licencias-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you classify open-source software licenses and identify compliance risks based on how your company plans to distribute or operate the resulting product.

Core Features & Use Cases

OSS license inventory and classification: Takes an input dependency list or SBOM and assigns each component a license and a copyleft strength category (permissive, weak copyleft, strong copyleft, or unknown).
Compatibility and incompatibility detection: Flags common license conflict patterns (e.g., patent-clause incompatibilities and “-only” variants) and highlights areas needing verification.
Distribution-model risk mapping: Evaluates how your intended model (SaaS/cloud, binary distribution, libraries/SDK, internal use) changes which licenses pose the highest risk.

Quick Start

Use the revisor-licencias-oss skill to analyze the provided dependencies and generate a license risk report for a SaaS distribution model.

Frequently Asked Questions about revisor-licencias-oss

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check OSS license compatibility for my project dependencies?▼

To check OSS license compatibility, provide a dependency inventory or SBOM to classify each component's copyleft strength and flag common conflict patterns like patent-clause incompatibilities. This process categorizes licenses as permissive, weak copyleft, strong copyleft, or unknown to map distribution risks.

What copyleft risks apply when distributing open-source software as a SaaS product?▼

SaaS distribution changes which copyleft risks apply by evaluating your intended cloud delivery model against the dependency licenses. Mapping your SaaS scenario against strong copyleft or unknown licenses identifies which components pose the highest compliance risk before you ship.

How do I generate an open-source license compliance report from an SBOM?▼

Generating an open-source compliance report from an SBOM requires mapping each dependency to its license and classifying its copyleft strength. The analysis detects common incompatibilities based on your distribution model and outputs a structured report with recommended compliance actions.

Can I use a manual dependency list instead of an SBOM for license risk detection?▼

You can use a manual dependency list instead of an SBOM for license risk detection. The analysis applies to both SBOMs and manual lists, requiring each dependency to be mapped to its license or marked as unknown and high risk for accurate compatibility evaluation.

What are the limitations of automated open-source license classification?▼

A key limitation is that dependencies with unmapped licenses are automatically marked as unknown and treated as high risk. Additionally, while it detects common incompatibilities like patent-clause conflicts, it highlights these areas as requiring manual verification before final compliance approval.

Does revisor-licencias-oss detect GPL incompatibilities with binary distribution models?▼

Yes, revisor-licencias-oss detects license incompatibilities for binary distribution by evaluating your intended distribution model. It flags strong copyleft licenses and common conflict patterns like "-only" variants, producing a structured report with recommended compliance actions for your specific scenario.