Classify license families and map obligations by deployment model.
npx skills add https://github.com/yachela/claude-for-legal-ar --skill oss-review-yachela
Please help me install this Agent Skill. Skill: oss-review Source: https://github.com/yachela/claude-for-legal-ar/tree/main/ip-legal/skills/oss-review Command: npx skills add https://github.com/yachela/claude-for-legal-ar --skill oss-review-yachela
oss-review helps legal and engineering teams reduce shipping risk by determining what open source licenses are present and what obligations those licenses trigger under your software’s deployment model, especially for copyleft and non-OSI source-available licenses.
Run oss-review on your dependency manifest by providing the package file path or repo path when prompted by the argument-hint.
High-intent search queries and answers about installing and using this skill.
Open source license compliance checking for a dependency list involves classifying license families from actual license text and mapping obligations by deployment model. This process flags unknown and non-OSI licenses, recommending whether to comply, replace, remove, or seek commercial licensing.
Copyleft risk in an SBOM review distinguishes weak copyleft, which typically affects only linked libraries, from strong copyleft, which requires derivative works to be released under the same license. This distinction maps to specific obligations based on your software delivery model.
Outbound license compatibility checks verify your chosen outbound license is compatible with every embedded dependency license. This preparation ensures required attribution files are present and confirms whether dependencies can be included across SaaS, distributed binary, internal-only, or embedded deployments.
Using a non-OSI source-available library in a SaaS deployment requires classifying the actual license text to identify obligations and restrictions. This assessment flags licenses posing as open source and recommends whether to comply, replace, or seek review for commercial licensing.
Automated legal review workflows for unknown license packages are limited by the need to classify actual license text rather than relying solely on manifest metadata. They flag unknown packages for review but cannot finalize comply or replace decisions without human legal assessment.
oscardlfrAnalyze CycloneDX JSON SBOMs for dependencies, licenses, and deprecated components.
abnejLLCGuide US export compliance for ITAR and EAR classifications and licensing.
spallempatiEnforce dependency version pinning and block builds with CVSS 7.0+ vulnerabilities.
AisleiAvilaAudit project dependencies for vulnerabilities, licensing issues, and supply-chain risks.
