Deadpath

io.github.CloudCorpRecords由 GitHub 账号 CloudCorpRecords 发布v0.1.0更新于 Nov 3, 2026

在整个模块集中查找已导出但从未使用的名称,并提供导入图证明。

AI 翻译由 AI 模型根据下方的原文描述翻译,可能有误。

原文描述

Find exported-but-never-used names across a module set, with import-graph proof.

已验证STDIO仅桌面

概览

Deadpath 的本地 MCP 服务;无需登录;STDIO。

暂无 AI 概览:以下信息来自注册中心条目和服务本身。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Deadpath,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

deadpath

Codebases accumulate exports nobody uses: a helper written for a caller that was later deleted, a constant kept "just in case", a whole module that still ships because something once imported a name from it. deadpath settles the question from evidence. You hand it a module set — each module's path, the names it exports, and the imports it makes — and it works out which exported names are never imported anywhere in the set:

  • Per-module summaries — for every module, its dead export names, its total (de-duplicated) export count, and how many of its exports are used.
  • A flat dead list — every dead export as a {module, name} pair, sorted so it can drive a cleanup list or a CI check directly.
  • Set-wide totals — the total export count, the total dead count, and dead_ratio: the share of the set's exported surface that is dead, rounded to four decimals.

The proof rule is simple. An export is used when some module in the set imports that name from its module — a module importing its own names from itself counts, just like any other import. Entry modules are the one exception: mark a module entry: true and all of its exports count as used, because an entry point's exports are public surface consumed from outside the set. An import with an empty names list is a side-effect import: it runs the target module but uses none of its named exports, so it keeps nothing alive.

Imports form a closed world: every import's from must name one of the supplied modules. That is what makes a dead verdict meaningful — the graph is complete by construction, and an import pointing outside the set is a validation error naming the offending path (for example modules[0].imports[1].from must name a supplied module), not a silent gap in the proof. Malformed input of any kind — a duplicate module path, a bad exports entry, a non-boolean entry — fails the same path-naming way, and no partial report is produced. The computation is pure and local: no network, no configuration, no files read beyond the input you pass in.

CLI

bash
npx @reneturcios/deadpath find --input args.jsonnpx @reneturcios/deadpath --version

args.json contains the full arguments object:

json
{  "modules": [    { "path": "src/main.ts", "exports": ["boot"], "entry": true },    {      "path": "src/util.ts",      "exports": ["fmt", "parse", "legacy"],      "imports": []    },    {      "path": "src/app.ts",      "imports": [{ "from": "src/util.ts", "names": ["fmt", "parse"] }]    }  ]}

exports and imports default to [] per module, names defaults to [] per import, and entry defaults to false. Here legacy is exported by src/util.ts but imported by nobody, so the report is:

json
{  "modules": [    { "path": "src/app.ts", "dead_exports": [], "used_count": 0, "export_count": 0 },    { "path": "src/main.ts", "dead_exports": [], "used_count": 1, "export_count": 1 },    { "path": "src/util.ts", "dead_exports": ["legacy"], "used_count": 2, "export_count": 3 }  ],  "dead_exports": [    { "module": "src/util.ts", "name": "legacy" }  ],  "total_exports": 4,  "total_dead": 1,  "dead_ratio": 0.25}

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

bash
npx -y @reneturcios/deadpath mcp

MCP client config:

json
{  "mcpServers": {    "deadpath": {      "command": "npx",      "args": ["-y", "@reneturcios/deadpath", "mcp"]    }  }}

Tools

  • find_dead_exports — Find exported names that no module imports.

    • modules (array, required, at least one) — modules as {path, exports?, imports?, entry?} objects; path is unique across the set, each import is a {from, names?} object whose from names a supplied module, and entry: true marks a module whose exports all count as used

    Returns {modules, dead_exports, total_exports, total_dead, dead_ratio}.

Docker

bash
docker run -i ghcr.io/cloudcorprecords/deadpathdocker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/deadpath find --input /w/args.json

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # tsx --test test/*.test.ts (pure local, no network)npm run dev     # run the CLI from source

License

MIT — Copyright (c) 2026 Rene Turcios

来源:README.md,提交 689ccdf

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.0最新Nov 3, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分