Skip to main content
Glama

LicenseGuard

用于判断所依赖的 OSS 许可证是否会对你的分发模式产生法律义务的工具。

生产环境: https://license-guard.rcc-aoki.workers.dev

有何不同

现有的许可证合规产品被分为两类:“判定深入但必须商谈(FOSSA / Black Duck)”或“自助式但判定较浅(Snyk)”,而两者的交汇处没有产品存在。

差异化的核心在于判定层。即使是相同的许可证,结论也会因上下文而完全相反。

使用方式

AGPL-3.0 的后果

作为 SaaS 对外提供

有披露义务

仅用于内部系统

无义务

向客户交付、分发

有披露义务

devDependency(不包含在交付物中)

无义务

最后一行是关键。现有工具大多不区分 dev 与 runtime 就发出警告,导致狼来了效应而被忽视。

Related MCP server: gridwork-license

供智能体使用

需要这个产品的时候,不是在浏览器里搜索时,而是在添加依赖时。因此首要的部署位置不是搜索结果,而是智能体的工具。

claude mcp add licenseguard --transport http https://license-guard.rcc-aoki.workers.dev/mcp

无状态的 Streamable HTTP,无需认证。提供的工具:

工具

用途

check_dependency_license

在添加一个依赖之前调用

check_manifest_licenses

审计整个清单文件

explain_license

说明许可证本身在所有分发模式下要求什么

JSON API 也返回相同的判定结果。

curl "https://license-guard.rcc-aoki.workers.dev/api/pkg/pypi/pyload-ng?model=saas"
# => {"license":"AGPL-3.0-only","verdict":"blocked", ...}

面向智能体的入口已汇总在 /llms.txt。

当前阶段

Phase 0(支付意愿验证) — 已发布 MCP 服务器和免费 Web 工具。由于主战场不是搜索而是智能体的工作流,因此验证指标不是 CTA 点击率,而是 MCP 的接入数和持续调用次数。GitHub App(Phase 1)将在看到验证结果后再着手。

支持的生态系统: npm / PyPI / Go modules / crates.io(Rust)

格式

传递依赖

外部查询

package-lock.json

○

不需要(包含许可证)

pnpm-lock.yaml / yarn.lock

○

需要(借助共享缓存递减)

go.sum

○

需要

Cargo.lock / poetry.lock / uv.lock

○

需要

package.json / requirements.txt / go.mod / Cargo.toml

✗ 仅直接依赖

需要

传入锁文件即可判定到传递依赖(package-lock.json / pnpm-lock.yaml / yarn.lock)。 其中 package-lock.json 包含许可证,因此完全不需要外部查询。 锁文件 因包含许可证而完全不需要外部查询,实际安装的版本信息 可以直接使用。有问题的许可证比起直接添加的依赖,更多是作为依赖的依赖 混入的,因此这里才是实质上的重点。

curl -X POST https://license-guard.rcc-aoki.workers.dev/api/scan   -H 'content-type: application/json'   -d "$(jq -Rs '{content: ., distributionModel: "saas"}' package-lock.json)"

开发

npm install
npm test          # 全テスト
npm run typecheck
npm run smoke     # 実レジストリへの疎通確認
npm run e2e       # 本番に対する E2E 6種
                  #   ui          Playwright で実ブラウザ
                  #   a11y        アクセシビリティ
                  #   mcp         公式 MCP SDK クライアント
                  #   load        並列実行時の一貫性
                  #   adversarial 敵対的入力・境界値
                  #   correctness 既知の正解との突き合わせ
                  #   operational 経路間の一致・HTTP・キャッシュ
npm run dev       # http://localhost:8787

即使单元测试全部通过,也有不用真实数据跑一遍就发现不了的缺陷。 smoke 和 e2e 针对与生产环境相当的外部依赖执行,因此发布前务必全部通过。

部署:

npm run db:migrate
npm run deploy

文档

所依赖的 OSS

鉴于本产品自身所处理对象的性质,所有依赖都限定为 MIT / Apache-2.0 系。自有 SaaS 不会产生披露义务。

角色

OSS

许可证

SPDX 表达式解析

spdx-expression-parse

MIT

Web 框架

hono

MIT

Go 的许可证数据

ClearlyDefined API

Apache-2.0

免责声明

本工具所展示的是基于公开的许可证条款和依赖清单的信息,并非法律建议。使用本工具不构成律师与委托人关系。判定基于清单中声明的许可证信息,并不涵盖所有义务或违规。

Available Tools

3 tools
check_dependency_licenseCheck one dependency for license obligationsAInspect

Determine whether adding or keeping a single open source dependency creates a legal obligation, given how this project ships. Call this BEFORE adding a new dependency to a project, and when auditing an existing one. A permissive result means no source-disclosure duty; a blocked result means the license obligates you and the dependency should be replaced or the shipping model reconsidered.

Inputs: name (required), ecosystem (required), distribution_model (required), scope, +1 more. Returns: license, verdict, rationale, reference, +1 more

check_manifest_licensesCheck a whole manifestAInspect

Scan an entire dependency manifest and report every dependency whose license creates an obligation for this shipping model. Use when reviewing a project as a whole, preparing for due diligence, or after a large dependency change. Pass a package-lock.json when one exists: problematic licenses usually arrive as transitive dependencies rather than ones you added directly, and only a lockfile reveals those.

Inputs: content (required), distribution_model (required).

explain_licenseExplain what a license requiresAInspect

Given an SPDX license identifier or expression, explain what it requires across every shipping model at once. Use when the question is about the license itself rather than a specific package — for example when comparing AGPL-3.0 against GPL-3.0 for a hosted service, or deciding what a project may safely depend on.

Inputs: license (required), linkage.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: explain_license focuses on understanding a license itself, check_dependency_license evaluates a single dependency in context, and check_manifest_licenses scans an entire manifest. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    All tool names follow a consistent verb_noun pattern (explain_license, check_dependency_license, check_manifest_licenses). The only minor deviation is that two tools start with 'check' while the third uses 'explain', but this is justified by the different action types.

    Tool Count4/5

    With only 3 tools, the server is slightly on the lean side, but each tool covers a distinct and essential aspect of license management (understanding, single-dependency check, full-manifest scan). The count is appropriate for a focused utility server.

    Completeness4/5

    The tool surface covers the core workflows: understanding licenses, checking individual dependencies, and scanning entire manifests. A minor gap is the lack of a tool to handle bulk license explanations or compare multiple licenses directly, but the existing tools cover the primary use cases well.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers