LicenseGuard
Decides whether an open source dependency's license **actually obligates you** — given how your project ships. Generic license scanners answer a different question ("what license is this?") and then warn on everything. LicenseGuard evaluates the license against your distribution model, so the same license produces different verdicts: | How you ship | AGPL-3.0 dependency | |---|---| | SaaS (network-accessible) | **blocked** — §13 network clause | | Internal use only | allowe
LicenseGuard
Decides whether an open source dependency's license **actually obligates you** — given how your project ships. Generic license scanners answer a different question ("what license is this?") and then warn on everything. LicenseGuard evaluates the license against your distribution model, so the same license produces different verdicts: | How you ship | AGPL-3.0 dependency | |---|---| | SaaS (network-accessible) | **blocked** — §13 network clause | | Internal use only | allowed | | Distributed binary / on-prem | **blocked** — inherited GPL distribution terms | | **devDependency** (never in the artifact) | **allowed** | That last row is the point. A build-time linter under AGPL never ships, so it triggers nothing — but tools that warn on it anyway train people to ignore every warning they produce. The same distinctions run through the rest of the license landscape, and they are not interchangeable: - **GPL** obligations attach to *distribution*. Running GPL code as a network service i
Установка
Характеристики
| Тип | MCP-сервер |
| Категория | MCP-серверы |
| Цена | бесплатно |
| Платформа | Командная строка |
| Системы | cli, api |
| Хостинг | cloud |
| Установка | mcp |
| Протоколы | mcp |
| Язык сайта | en |
| Вендор | rcc-aoki |
