dsh-generative-ui

检测报告

能力清单

• 发起网络请求network需留意8 处命中
  • src/client/canvas/read.ts:15const response = await fetch(`${CANVAS_READ_PATH}?cwd=${encodeURIComponent(cwd)}`, { cache: "no-store" });
  • src/client/canvas/read.ts:31const response = await fetch(url, { cache: "no-store" });
  • src/client/canvas/read.ts:48const response = await fetch(url, { cache: "no-store" });
  • src/client/index.ts:152void fetch(`${CARD_ERROR_PATH}?session=${encodeURIComponent(id)}`, {
  • 看请求发往哪些域名。发往作者自己的后端是常见做法。
• 写入文件writes-files需留意5 处命中
  • lib/index.js:1004directories) and \`writeFile(path, content)\` over the workspace. Paths are workspace-relative and
  • src/skill.ts:965directories) and \`writeFile(path, content)\` over the workspace. Paths are workspace-relative and
  • types/fs.d.ts:30export function writeFile(path: string, content: string): Promise<void>;
  • types/standalone/fs.js:15export async function writeFile(...args) {
  • 看写入位置。写自己的配置目录是正常的，写系统目录不是。
• R013 清单可疑manifest-obfuscation需留意1 处命中
  • 安装脚本: prepare
  • 清单被刻意写乱时，加载行为会难以预测。看原文而不是看渲染结果。
• 读取文件reads-files一般22 处命中
  • lib/index.js:888const load = async (p: string) => { try { setRows(await readdir(p)) } finally { setLoading(false) } }
  • lib/index.js:1002\`$dsh/fs\` gives a card \`readFile(path) -> string\`, \`readBytes(path) -> Uint8Array\`, \`readdir(path) -> {name, type…
  • lib/index.js:1742return existsSync(path) ? path : undefined;
  • lib/index.js:1753res.end(await readFile(file));
  • 读文件是绝大多数插件的正常工作方式，本身不构成顾虑。
• 动态加载模块dynamic-import一般9 处命中
  • …lient/canvas/CanvasLauncher.d.ts:6export declare function CanvasLauncher({ ids, onOpen }: CanvasLauncherProps): import("react").JSX.Element;
  • …s/client/canvas/CanvasPanel.d.ts:88export declare function CanvasPanel({ canvases, offerable, cwd, onOpen, onClose, onWidth, onCardError, onCardRendered }:…
  • …lient/canvas/useDismissable.d.ts:13setOpen: import("react").Dispatch<import("react").SetStateAction<boolean>>;
  • …lient/canvas/useDismissable.d.ts:14anchor: import("react").RefObject<HTMLDivElement>;
  • 动态导入本身无害，但会让依赖关系难以静态审阅。
• 接触凭据或密钥credentials一般5 处命中
  • package.json:118"@deepseek-ai/dsh-credentials": "0.2.1-alpha.2",
  • lib/index.js:1307- \`import { streamText } from "$dsh/ai"\` runs a model call from inside the card, on the app's own model and credential…
  • lib/index.js:1330back and costs a round trip. **Give them the fields instead** — current values filled in, secrets masked, the ones
  • src/prompt.ts:100- \`import { streamText } from "$dsh/ai"\` runs a model call from inside the card, on the app's own model and credential…
  • 看它读取哪些凭据、发往哪里。用于登录自己的服务是正常的。
• 文中出现远程脚本地址remote-url-reference一般4 处命中
  • lib/index.js:1231| a formula the reader is trying to READ, not just the number it comes out as | \`katex\` | \`katex.renderToString(tex, …
  • lib/index.js:1239The same doubt covers **default vs named**, and there the answer is cheaper still: \`curl -s https://esm.sh/<package>\` …
  • src/skill.ts:1192| a formula the reader is trying to READ, not just the number it comes out as | \`katex\` | \`katex.renderToString(tex, …
  • src/skill.ts:1200The same doubt covers **default vs named**, and there the answer is cheaper still: \`curl -s https://esm.sh/<package>\` …
  • 只是文本里出现了远程脚本地址，没有看到加载它的调用。多半是文档或注释；若确实可疑，搜一下这个地址在包里的其他出现位置。

这份报告的口径

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

依赖安全公告

已查询这个插件声明的全部依赖，没有匹配到已公开的安全公告。（含 DSH 框架包在内的 @deepseek-ai/* 不作查询——那是运行时自己的问题，不是插件的。）