DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles，发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目，与 DeepSeek 官方无隶属、授权或背书关系。

DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
P

dsh-provider-passport

Provider Passport

面向自定义 DeepSeek Harness 提供程序的审核优先请求方言预检。

插件会安装到这里；不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:ArmyWas/dsh-provider-passport#56d2e3018e7ab0da79671be7eab89c8a97077068
README兼容性版本
A proposed profile applied and verified through DSH 0.1.2-alpha.4

兼容性与来源证明

Provider Passport 以 dsh-provider-passport 发布，当前版本为 0.1.0-preview.2。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。

DSH 兼容范围
*
运行环境
web
发布来源
github
Registry 更新时间
2026/9/2

版本

0.1.0-preview.2prerelease
2026/9/2
查看其余 1 个版本收起版本
0.1.0-preview.1prerelease
2026/9/1

相关插件

正在加载相关插件…

最新版
0.1.0-preview.2
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
web
许可证
MIT
发布源
github
GitHub
★ 0
周下载
0
最近提交
2026/9/5
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown，粘贴到 README 即可。

这是你的 Plugin？认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 models-usage 分类下经过校验的插件。

Experimental Cot Translation Bundle@deepseek-ai/dsh-experimental-cot-translation-bundle扩展推理的实验性机器翻译Whale Widgetdsh-whale-widgetDSH Web 界面右下角的 DeepSeek 余额小鲸鱼挂件:余额/今日已用/峰谷定价、自定义泡泡点击序列(文本/余额/今日/峰谷/图片/随机语句与并列加权选择)、逐行样式与字体、悬浮快捷编辑、音效与每轮消耗、自定义角色/动图/音效、吸附与翻转自定义Our Free Model@ebony-vinyl/dsh-our-free-modelOur Free Model — 在 dsh 里装上这个插件即可，无需登录、注册或填 API Key，就能使用包括 DeepSeek V4.1 Flash、Kimi K3 在内的前沿模型，桌面端另有 EAC 协付渠道；2.0 起接入 LobsterAI、Qoder、TRAE、Cline、Loomy、Raccoon、MiniMax、ZCode、Gemini 十个账号渠道（原有匿名免费通道保留）（登录、账号池、积分领取、本地 OpenAI 网关与局域网转发、数据看板与运行日志），六页毛玻璃界面统一呈现。Usage@linxin666/dsh-usage用于 dsh Web GUI 的使用统计插件：检测各提供商的余额和编程套餐配额，并实时记录令牌使用情况；侧边栏 Settings 行上方显示紧凑的价格概览卡片

README

DSH Provider Passport

简体中文

Public preview. Independent community project; not affiliated with or endorsed by DeepSeek.

DSH Provider Passport finds request-dialect differences between a custom OpenAI Chat Completions endpoint and DeepSeek Harness before the first real task fails. It runs a bounded, review-first preflight, proposes only the compatibility fields supported by Harness, verifies the change through the real Harness LLM runtime, and keeps rollback available.

A proposed profile applied and verified through DSH 0.1.2-alpha.4

Why this exists

A generic OpenAI-compatible connectivity check can pass while Harness still fails because the endpoint rejects one of these request-shape choices:

  • developer instead of system
  • max_completion_tokens instead of max_tokens
  • store
  • reasoning_effort
  • stream_options.include_usage

Harness already exposes the corresponding compat settings. The missing product layer is a safe way to discover the minimum settings, preview them, apply them to one model, verify the result through Harness, and recover if verification fails.

Install the preview

Requires Node.js 22.19+ and a DeepSeek Harness Web profile.

npx @deepseek-ai/dsh plugin --profile web add dsh-provider-passport@preview
npx @deepseek-ai/dsh web

If dsh is already available on your PATH, omit npx @deepseek-ai/dsh and use dsh.

Open Settings → Plugins, expand Provider compatibility passport, select a custom OpenAI Chat Completions model, review the request budget, and confirm the preflight.

The route must explicitly set api: openai-completions. When api is omitted, Harness may inherit a different wire protocol for each installed-catalog model; the public model metadata does not expose that resolved protocol, so the plugin excludes the route instead of guessing. Routes using Responses, Anthropic Messages, or another protocol remain out of scope.

To remove it:

npx @deepseek-ai/dsh plugin --profile web remove dsh-provider-passport

Safety and privacy contract

  • Nothing runs in the background. Every preflight requires explicit confirmation.
  • At most 10 fixed requests are sent, with at most 1 output token each and a 12-second per-request timeout.
  • No user files, conversations, prompts, sessions, or tool data are used.
  • Credentials and custom headers stay in memory and never enter reports or logs.
  • The selected model receives only the smallest observed compatibility profile; other models are untouched.
  • A route is eligible only when its editable settings explicitly declare api: openai-completions; ambiguous and other-protocol routes are shown as safely skipped.
  • Proposals are restricted to maxTokensField, supportsDeveloperRole, supportsStore, supportsReasoningEffort, and supportsUsageInStreaming. Catalog-withheld fields are never configured.
  • Cancellation never writes settings. A failed Harness verification automatically restores the previous settings.
  • If Harness rejects a proposed field during its atomic settings validation, the plugin reports the refusal and leaves settings unchanged.
  • Copy redacted report removes endpoint, model id, credentials, headers, request text, response bodies, and model output. Nothing is uploaded automatically.

Read the full privacy design before testing a sensitive enterprise endpoint.

Help validate the real-world need

This preview has deterministic and real-Harness runtime coverage. It is public so people can test their own third-party, enterprise, or self-hosted OpenAI-compatible endpoints without sharing credentials.

  1. Run the preflight.
  2. Click Copy redacted report.
  3. Submit a compatibility report.

Please never post an API key, authorization header, full private endpoint, proprietary prompt, or response body. See the tester guide for the evidence standard.

Questions, product ideas, and unclear results belong in GitHub Discussions.

Current evidence

  • 11 automated unit/contract tests cover redaction, protocol gating, offered-field restrictions, minimal proposals, cancellation, settings isolation, and runtime verification.
  • The packaged plugin completes install → probe → apply → real-runtime verify → rollback on DSH 0.1.1-rc.2 (npm default at release time) and 0.1.2-alpha.4 (latest alpha at release time).
  • A deterministic strict gateway reproduces three request-dialect failures that pass a generic compatibility control but fail under the default Harness request shape.
  • The settings-card flow was manually audited in the real DSH Web UI, including cancellation and rollback.

The full product-discovery evidence is in the opportunity report.

Deliberate scope

This project does not replace:

  • generic API, streaming, tool, or structured-output conformance tools such as CompatCanary;
  • model capability discovery;
  • provider health monitoring;
  • routing, fallback, or proxy adapters.

It owns only the last mile between a custom OpenAI Chat Completions endpoint and the request dialect generated by Harness.

This preview does not infer /v1/responses, Anthropic Messages, or vendor-specific routing from a failed Chat Completions request. A blocked result may mean the route speaks another protocol or depends on provider-managed behavior; the plugin reports that boundary and writes nothing. Multi-protocol discovery remains a separate research question so this plugin does not silently become a general conformance suite.

Development

npm test
npm pack --dry-run

For the isolated real-bundle test, set DSH_CLI_JS to a packaged DSH CLI entry and run:

npm run harness-e2e

See CONTRIBUTING.md and SECURITY.md.

Trademark and license

“DeepSeek Harness” is used only to describe compatibility. The project uses the recommended DSH abbreviation and does not imply official endorsement. See the upstream brand guidelines.

MIT © ArmyWas