revisor-licencias-oss

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.

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.

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.

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.

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.

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.