030611/dsh-telemetry-redactor
DeepSeek Harness 会话遥测的故障关闭导出副本编辑
Project Overview项目介绍
This is a native DSH plugin built exclusively for DeepSeek Harness, designed to redact sensitive credential data from outbound telemetry copies before they reach the configured backend. It does not alter the canonical session logs stored locally on the DSH instance. It mounts onto the official session-telemetry/record waterfall hook, preserves the composition of existing deployment rules, and returns a new recursively redacted telemetry record. The official DSH telemetry coordinator creates a deep copy of canonical session events before invoking this plugin, so only the outbound copy is modified, not the original stored log.
This plugin is intended for DSH deployments that prioritize privacy and security for their session telemetry. It redacts values under high-risk key names like authorization, password, and apiKey, as well as recognizes authorization values embedded inside strings and common credential formats such as sk- prefixed keys, GitHub tokens, and JWTs. It avoids incorrectly redacting ordinary fields that contain the string "token" but are not sensitive, such as inputTokens and tokenCount. It acts as a safety filter, and does not guarantee that it will catch every possible unknown secret format.
To install the plugin, run the DSH CLI command dsh plugin --profile <your-profile> add dsh-telemetry-redactor, then dump your configuration to confirm the plugin loaded correctly. The only configurable option is the replacement string that redacted secrets are swapped for, which defaults to [REDACTED]; the redaction rules are fixed and cannot be disabled via configuration. The plugin is released under the open source MIT license, and has several known limitations including that it cannot detect unknown secret formats that do not match the supported patterns.
这是DeepSeek Harness的原生插件,专门用于在遥测数据发送到配置的后端之前,去除其中符合匹配规则的敏感凭证信息,且不会修改存储在本地的规范会话日志。它会挂载到官方的session-telemetry/record工作流,保留其他现有部署规则的组合性,最终返回经过递归脱敏处理的新记录。官方遥测协调器会先深度复制规范会话事件,因此插件仅修改出站副本,不改动本地存储的原始会话日志。
它面向对会话遥测有隐私安全需求的DSH部署者,支持红配对应高风险键名的值,比如authorization、password、token这类敏感字段,也能识别嵌入字符串中的Bearer和Basic授权值,以及sk-开头的密钥、GitHub令牌、JWT这类常见凭证格式。它不会误脱敏诸如inputTokens这类包含token字样但本身不敏感的常规字段,仅作为安全过滤存在,不保证能拦截所有未知格式的秘密。
你可以通过DSH的CLI命令dsh plugin --profile <profile名> add dsh-telemetry-redactor将它安装到指定配置文件,安装完成后可转储配置确认插件是否成功加载。它仅提供一个可配置项,即替换敏感值的占位文本,默认是[REDACTED],红配匹配规则固定无法通过配置禁用。本插件采用MIT许可开源,存在已知限制,比如无法识别没有匹配特征的未知秘密格式。
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】,检查通过再动手。
插件:dsh-telemetry-redactor(030611/dsh-telemetry-redactor)
仓库:https://github.com/030611/dsh-telemetry-redactor
本站详情页:https://www.yhbd.top/plugins/030611-dsh-telemetry-redactor/
本站登记:类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 2 · 最近提交 2026-08-14 · 主语言 TypeScript
按下面顺序执行,每步先把结论告诉我,再进入下一步:
【1 兼容性检查】
① 我这边:DSH 版本、Node 版本、操作系统、当前 profile(web / desktop)。
② 读它的 README、package.json、插件 manifest,列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对,结论只写「满足 / 不满足 / 未知」三种;不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突:命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。
【2 安全性检查】
① 仓库可信度:和上面「本站登记」是否一致;star / fork 数、创建时间、最近提交,是否归档或长期停更。
② 安装脚本:逐行看 package.json 的 preinstall / install / postinstall,以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名,立刻停下来告诉我,不要继续装。
③ 依赖:列出新增依赖,标出无人维护、或与知名包拼写近似的可疑包(typosquatting)。
④ 权限与副作用:它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限(filesystem / network / shell / clipboard 等),以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限,或权限明显超出功能所需,先停下来问我。
【3 安装】
上面两步没有「不满足」和「高危项」时才执行;用官方推荐方式安装,不要自行提权。
【4 汇报】
用表格输出:检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜,也不要替我决定。
Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH:它会先核对兼容性与安全性(逐条给「满足 / 不满足 / 未知」),确认没问题再安装,有高危项会停下来问你。框内可滚动,复制到的是完整提示词;安装命令不一定准确,发给 DSH 更稳。
- Only 2 stars - very few users, little community feedback星标只有 2,几乎没人在用,遇到问题缺少社区反馈
DSH walks through these 9 checksDSH 会逐条核对这 9 项
Compatibility兼容性
- DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
- External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时(Electron / Python / Docker 等)是否齐备
- Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突:命令名、skill / tool 重名、端口占用、重复 MCP 注册
Security安全性
- Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致,是否归档或长期停更
- Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
- curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
- Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
- Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需(filesystem / network / shell / clipboard)
- Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限,以及卸载与回滚方式
Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照,不能替代安全审计。
Or use CLI install (for developers)或使用命令行安装(适合开发者)
CLI Install命令行安装
dsh plugin --profile web add dsh-telemetry-redactor
把 030611/dsh-telemetry-redactor 加入你的 DSH 配置(web profile)即可启用。
READMEREADME
DSH Telemetry Redactor
English | 中文

Redact supported credential patterns from outbound telemetry copies before configured backends receive them—without rewriting canonical session logs.
dsh plugin --profile web add dsh-telemetry-redactor
Community-maintained and not an official DeepSeek project. Related trust-layer plugins: Verification Receipt, Evidence Audit, and Context Provenance.
dsh-telemetry-redactor is a minimal DeepSeek Harness Profile Bundle that redacts sensitive values from session telemetry before a backend receives them. It mounts on the official session-telemetry/record waterfall, calls next() so other deployment rules still compose, and returns a new recursively redacted record.
The official telemetry coordinator deep-copies canonical session events before this waterfall and contains thrown rules per record. Therefore this plugin changes only the outbound copy: it never rewrites the canonical session log. In this document, fail-closed means only that this coordinator withholds one failing export copy and continues the agent loop. It is not a claim that every telemetry path or listener order is impossible to bypass.
What it redacts
- Values under high-risk key names such as
authorization,cookie,credential,password,secret,token,apiKey,access_token,clientSecret, andprivateKey; recognized credential patterns in key names are replaced too. - Bearer and Basic authorization values embedded in strings.
- Common credential forms including
sk-..., GitHub tokens, Slack tokens, JWT-like triples, andtoken=.../api_key: ...assignments.
Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要,完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →
wenbin-wb/dsh-bridge
PerryLink/dsh-permission-rules
MichengAI/dsh-archive-manager
eri64/dsh-claude-ux
lsz-asd/dsh-plugin-session-delete
10086ggqq/dsh_theme_terraria
king-bcolor/dsh-multi-tenant-projects