SiteWarming/Comply
AI-powered open source license compliance scanner. Analyzes how dependencies are actually used — not just what license they have — to determine if obligations trigger for your distribution model. Multi-agent AI pipeline, MCP server for Claude Code integration, and structured output for AI assistants. Zero API keys needed for local use.
Platform-specific configuration:
{
"mcpServers": {
"Comply": {
"command": "npx",
"args": [
"-y",
"Comply"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
AI-powered open source license compliance agent.
Comply scans your codebase, resolves licenses for every dependency, evaluates compliance against your policy, and uses AI to analyze *how* flagged packages are actually used — because "GPL detected" isn't the same as "GPL obligations triggered."
Existing tools (FOSSA, Snyk, WhiteSource) flag licenses but don't reason about context. They'll tell you "GPL detected in 14 packages" with zero context about whether your specific usage actually triggers copyleft obligations. The answer depends on your distribution model, how the code is linked, and whether you're shipping a product or running a service. Those tools don't make that distinction.
Comply does. It reads your actual source code to determine whether the way you use a package triggers its license terms. GPL in a SaaS product that's never distributed? Usually fine. GPL in a CLI tool shipped to customers? That's a real problem. AGPL in anything network-facing? Red alert. Comply makes those distinctions automatically.
# Scan the current directory
npx comply-oss scan .
# Or install globally
npm install -g comply-oss
comply scan /path/to/your/repo --verbosecomply scan [path]Core audit command. Scans a repository and produces a full compliance report.
comply scan . # Basic scan
comply scan . --verboLoading reviews...