
Packcompare
io.github.CloudCorpRecords由 GitHub 账号 CloudCorpRecords 发布v0.1.0更新于 Nov 3, 2026
比较软件包的两个版本:文件、依赖项、大小和导出。
AI 翻译由 AI 模型根据下方的原文描述翻译,可能有误。
原文描述
Diff two versions of a package: files, dependencies, size, and exports.
概览
Packcompare 的本地 MCP 服务;无需登录;STDIO。
暂无 AI 概览:以下信息来自注册中心条目和服务本身。
安装
在 SourceWeft 中
- 打开 控制台中的 Packcompare,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
packcompare
A package can change a lot between two versions without any single change looking dramatic: a file quietly grows, a dependency is swapped, an export path disappears. packcompare puts both snapshots side by side and reports the whole move at once, so a release review starts from the diff instead of from a hunch.
You supply two snapshots of the same package — a before
and an after. Each one is a plain description, not a real
package on disk: a version string, a files list of
{path, size} entries, a dependencies map of name to
version string, and an exports list of strings.
The file report splits into three sorted lists: paths only
in after were added, paths only in before were removed,
and paths present in both with different sizes are changed,
each carrying size_before and size_after. File paths must
be unique within a snapshot, and sizes may be zero — an
empty file is still a file. Dependencies get the same
treatment, sorted by name: added and removed entries carry
the version from the side they exist on, and a name present
in both with a different version string is changed, reported
as {name, from, to}.
Exports are compared as sets, so mentioning the same export
twice in one snapshot changes nothing. The headline numbers
are the summed file sizes of each snapshot, their difference
size_delta (which is negative when the package shrank),
and the file counts on each side.
Breaking is deliberately narrow and pinned: a change is
breaking exactly when at least one export was removed, and
breaking_reasons spells each one out as
removed export: <name> in the removed list's sorted order.
Added files, resized files, and dependency bumps — however
large — never make a change breaking on their own.
Malformed input is a validation error naming the offending
path, with the snapshot named in the path: a duplicate file
path is reported as before.files[1].path is a duplicate,
for example. No partial diff is produced. Unknown extra
fields are ignored. The computation is pure and local: no
network, no configuration, and no real package is read.
CLI
args.json contains the full arguments object:
The result is printed as JSON:
Exit codes: 0 on success, 1 on a runtime error (including
an unreadable or invalid input file, or invalid input), 2
on a usage error.
MCP server
MCP client config:
Tools
-
compare_packages— Diff two versions of a package.before(object, required) — the earlier package snapshot:{version, files, dependencies, exports}, whereversionis a non-empty string,filesis a list of{path, size}entries with unique non-empty paths and integer sizes of at least 0,dependenciesis a map of dependency name to non-empty version string, andexportsis a list of non-empty stringsafter(object, required) — the later package snapshot, with the same shape asbefore
Returns
{version_before, version_after, files, dependencies, exports, size_before, size_after, size_delta, file_count_before, file_count_after, breaking, breaking_reasons}.
Docker
Development
License
MIT — Copyright (c) 2026 Rene Turcios
来源:README.md,提交 dbbbf86
工具
0版本历史
1- v0.1.0最新Nov 3, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分