buberlo/dsh-jev

Name: buberlo/dsh-jev
Author: buberlo

Plugin插件 ⭐ 24 MIT Approval & Security审批与安全 Models & Routing模型与路由

This repository stays available under the MIT licence. If any of these ideas are useful to you, please take them — in jevcore or anywhere else:

catalog descriptioncatalog 简介 / catalog description：Jev-powered decision layer for DeepSeek Harness

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

dsh-jev is a native plugin built exclusively for DeepSeek Harness (DSH) that connects the TypeSafe Jev decision layer to DSH’s agent execution pipeline. The repository ships two published npm packages: the harness-independent @buberlo/jev-core for general reusable decision logic that can be embedded into games, search tools, or MCP routers, and the DSH-specific @buberlo/dsh-jev plugin bundle that integrates directly with DSH’s Cordis extension system. It can be installed directly via the DSH CLI with dsh plugin add, or cloned from GitHub for local development, testing, and custom modification before running the built-in examples.

This plugin is intended for developers who want to add deterministic decision gates to their DSH agent workflows without relying on LLM planning for every small choice. Jev makes narrow, gated decisions at key points in the DSH agent loop: it filters irrelevant tools before the step starts, checks if a proposed tool call is safe to run, routes requests to matching models, and injects bounded skill hints when needed. To try it out locally, after cloning the repo and running pnpm install and pnpm build, you can run four different examples to see core functionality in action, including a full end-to-end demo of the DSH plugin integration.

dsh-jev is released under the permissive MIT license, and only version 0.1.0 of both packages is currently published to the npm registry, while the 0.1.2 workspace version has updates that are not yet publicly available. All core features work fully offline with default mock settings, no API key is required to run tests, examples, or the default plugin, and there is zero overhead when running in the default shadow mode. By default, the plugin does not send any repository data, logs, or session transcripts anywhere, and an API key is only required if you explicitly enable the live TypeSafe Jev API for production use.

dsh-jev 是专为 DeepSeek Harness (DSH) 开发的原生插件，用于将 TypeSafe Jev 决策层绑定到 DSH 的代理执行流程中。项目包含独立的通用核心决策包 @buberlo/jev-core ，以及专为 DSH 适配的插件包 @buberlo/dsh-jev，可在 DSH 代理流程的多个不同的关键节点生成小而快的确定性决策，具体包括工具相关性过滤、工具调用安全检查、任务匹配模型路由选择等核心能力。

面向需要为 DSH 代理增加确定性决策门限的开发者，默认使用离线模拟模式，不会改变原有 DSH 的行为，可通过内置示例快速体验核心功能。用户克隆仓库后可通过 pnpm 命令构建并运行不同示例，分别查看动态工具选择、预执行安全评估、DSH 真实管道挂载等效果，也可通过 npm 直接安装到已有的 DSH 环境中。

项目采用 MIT 许可证开源，依赖 pnpm 包管理器和 TypeScript 环境，当前仅在 npm 发布 0.1.0 版本，工作区版本 0.1.2 尚未发布到注册表。默认无网络请求，不需要 API 密钥即可离线运行所有示例和测试，若启用在线 API 则需要用户主动配置密钥，默认不会自动发送仓库、日志或会话数据。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-jev（buberlo/dsh-jev）
仓库：https://github.com/buberlo/dsh-jev
本站详情页：https://www.yhbd.top/plugins/buberlo-dsh-jev/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 24 · 最近提交 2026-09-23 · 主语言 TypeScript · 未检测到 DSH 插件清单

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【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 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 1 warning1 项注意

24 stars - an early-stage project星标 24，属于早期项目
No DSH plugin manifest detected - it may only carry the dsh-plugin topic, so the install method must be confirmed on the spot未检测到 DSH 插件清单：可能只是打了 dsh-plugin 话题，安装方式要现场确认

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 @buberlo/dsh-jev@0.1.4

把 buberlo/dsh-jev 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

20.8 KB · 缓存于 2026-10-03 22:09:28 · 20.8 KB

dsh-jev

[!WARNING] Development of dsh-jev has been discontinued (October 2026). There will be no further releases of @buberlo/dsh-jev or @buberlo/jev-core; 0.1.4 is the last version. The code was only ever tested against DeepSeek Harness 0.1.6-alpha.x (verified on 0.1.6-alpha.2) and may not work with newer DSH releases. Issues and pull requests will no longer be worked on.

For Jev in DeepSeek Harness or any MCP host, please use jevcore by PerryLink. It is maintained, more widely used, offline by default, and Apache-2.0 licensed: jevcore (harness-independent core), jevcore-dsh (DSH plugin) and jevcore-mcp (MCP stdio server).

Ideas others are welcome to adopt

This repository stays available under the MIT licence. If any of these ideas are useful to you, please take them — in jevcore or anywhere else:

Monotone permission narrowing. Jev may only restrict, never widen: tool selection intersects with existing restrictions, and call assessments compose as deny > hold > ask > allow after calling next(), so later policies are never skipped. Errors, timeouts and stale snapshots fail closed (ask/hold, never allow). See docs/policy.md.
Shadow mode and an offline mock as the default. provider: mock + mode: shadow logs decisions without changing behaviour, so operators can observe before enforcing.
Measured benchmarks and regression sets. Versioned evaluation fixtures, an on-prem support assessment regression set, and with/without-Jev benchmarks (e.g. a protected audit trail blocked in 10/10 runs) with method and limits documented in docs/benchmark.md and docs/evaluation.md.

Thank you

Thanks to everyone who tried dsh-jev, reported problems, or contributed — in particular @Daltonganger and @autox-my for their pull requests — and to PerryLink for building and maintaining jevcore.

The original README follows for reference.

The Jev decision layer for DeepSeek Harness (DSH).

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 buberlo/dsh-jev 的 README.md。在 GitHub 查看原文 →