dsh-plugin-mall

检测报告

能力清单

• 以 shell 执行命令shell-exec高关注6 处命中
  • src/cli.js:340* closed, with no shell:true or unguarded fallback — when no verified entry
  • src/guard.js:1748if (cmd === undefined) return { command: "pnpm", shell: true, treeKill: true };
  • src/guard.js:1750// is Node's default install layout). Under shell:true Node joins command and
  • src/guard.js:1757return { command: `"${cmd}"`, shell: true, treeKill: true };
  • 看命令字符串是拼出来的还是写死的。拼接用户输入才是真正的风险。
• 可执行外部程序spawns-processes高关注4 处命中
  • src/cli.js:27import { spawn } from "node:child_process";
  • src/guard.js:9import { spawn, spawnSync } from "node:child_process";
  • src/index.js:21import { spawn } from "node:child_process";
  • src/installer.js:9import { spawn, spawnSync } from "node:child_process";
  • 看它调用哪些程序。调用本机已有的工具是常见做法。
• R012 改写用户 profileprofile-tamper高关注4 处命中
  • cli.js, guard.js
  • 看它改的是自己那一段还是别人的。改用户 profile 通常应由用户手动做。
• 写入文件writes-files需留意575 处命中
  • src/cli.js:572rmSync(snapshot.dir, { recursive: true, force: true });
  • src/cli.js:789mkdirSync(dirname(logPath), { recursive: true });
  • src/cli.js:1209try { unlinkSync(planFile); } catch { /* nonce-named residue is inert */ }
  • src/cli.js:1316try { unlinkSync(`${plan.readyFile}.cancel`); } catch { /* best effort */ }
  • 看写入位置。写自己的配置目录是正常的，写系统目录不是。
• 运行时改写自身配置modifies-own-manifest需留意277 处命中
  • src/cli.js:1730writeFileSync(join(p, "package.json"), JSON.stringify({ dependencies: {} }));
  • src/cli.js:1731writeFileSync(join(p, "cordis.patch.yml"), "[]\n");
  • src/cli.js:1781writeFileSync(join(p, "package.json"), JSON.stringify({ dependencies: {} }));
  • src/cli.js:1782writeFileSync(join(p, "cordis.patch.yml"), "[]\n");
  • 运行时改写自身配置会让下次启动的行为和你看过的源码不一致。
• 启动伪终端spawns-pty需留意84 处命中
  • src/cli.js:929const killer = spawn(process.env.ComSpec ?? "cmd.exe", ["/d", "/s", "/c", `taskkill /PID ${pid} /T /F >nul 2>&1`], { she…
  • src/github.js:685dependencies: { schemastery: "^3.18.0", ws: "^8.18.0", clsx: "^2.1.1", "node-pty": "^1.1.0" },
  • src/index.js:1195child = _spawn(process.env.ComSpec ?? "cmd.exe", ["/d", "/s", "/c", `"${line}"`], {
  • src/index.js:4016const child = spawn(process.env.ComSpec ?? "cmd.exe", ["/d", "/s", "/c", '"echo "dsh verbatim check""'], {
  • 伪终端等于给了一个完整 shell。确认这是插件的核心功能。
• 发起网络请求network需留意7 处命中
  • src/github.js:49response = await fetch(url, {
  • src/github.js:216const response = await fetch(`${base}/${clean.replace("/", "%2F")}/latest`, {
  • src/github.js:263const response = await fetch(`${base}/${clean.replace("/", "%2F")}`, {
  • src/github.js:387const response = await fetch(`${base}/${name.replace("/", "%2F")}/${point}`, {
  • 看请求发往哪些域名。发往作者自己的后端是常见做法。
• 可终止进程kills-processes需留意5 处命中
  • src/cli.js:687process.kill(target, 0);
  • src/cli.js:926try { process.kill(pid, "SIGKILL"); } catch { /* already gone */ }
  • src/cli.js:931try { process.kill(pid); } catch { /* already gone */ }
  • src/restart-protocol.js:246process.kill(pid, 0);
  • 看它终止的是自己启动的进程，还是按名字匹配到的任意进程。
• 动态执行代码dynamic-code需留意2 处命中
  • src/index.js:3276const front = new Function("window", snippet)(undefined);
  • src/index.js:3326const front = new Function([
  • 看 eval / new Function 的入参来自哪里。常量字符串和用户输入是两回事。
• 读取文件reads-files一般271 处命中
  • src/cli.js:245if (existsSync(full)) return full;
  • src/cli.js:277if (!existsSync(manifestPath)) return undefined;
  • src/cli.js:280manifest = JSON.parse(readFileSync(manifestPath, "utf8"));
  • src/cli.js:292if (!existsSync(entry)) return undefined;
  • 读文件是绝大多数插件的正常工作方式，本身不构成顾虑。
• 读取环境变量reads-env一般82 处命中
  • src/cli.js:198* merged object such as pnpmGuardEnv()); it defaults to process.env.
  • src/cli.js:211env: env === undefined ? process.env : env,
  • src/cli.js:389for (const [key, value] of Object.entries(process.env)) {
  • src/cli.js:626for (const [key, value] of Object.entries(process.env)) {
  • 环境变量里常混有密钥。看它是否把整个 env 都读走。
• 接触凭据或密钥credentials一般5 处命中
  • src/guard.js:36// invalid YAML. Keeping the tag's identity matters: `!!js process.env.KEY` and
  • src/guard.js:37// the plain string "process.env.KEY" are the same characters but not the same
  • src/guard.js:4001writeFileSync(join(p, "node_modules", "js-host", "cordis.patch.yml"), "- insert:\n - id: js-row\n name: js-host\n config…
  • src/guard.js:4006patchText: "- id: js-row\n config:\n value: process.env.SECRET\n",
  • 看它读取哪些凭据、发往哪里。用于登录自己的服务是正常的。
• 动态加载模块dynamic-import一般4 处命中
  • src/guard.js:1036* Rows the loader would try to mount without a module specifier. `import(undefined)`
  • src/guard.js:3095({ applyEntryPatches } = await import("@deepseek-ai/cordis-plugin-include"));
  • src/guard.js:3098throw new Error(`differential vs applyEntryPatches cannot run: @deepseek-ai/cordis-plugin-include failed to import (${er…
  • src/installer.js:3011const { symlinkSync } = await import("node:fs");
  • 动态导入本身无害，但会让依赖关系难以静态审阅。

这份报告的口径

扫描读的是包里的源码，全程不执行第三方代码。 本次读了 11 个文件，扫描于 2026-10-15。 命中次数只说明源码里出现过这类调用，不说明行为好坏——一个插件读写文件 500 次和 1 次 都会被记为「读取文件」。这是能力清单，不是信任评分，也不是安全结论： 没扫出来的能力可能只是写法没被规则覆盖。

可信度

• 0没有可扣分的项