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
G

dsh-git-forge

Git Forge

用于 DeepSeek Harness better-sidebar 的 GitHub/Gitea（及其他代码托管平台）账户，支持项目范围授权和推送策略

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

npx -y @deepseek-ai/dsh plugin --profile web add github:thirsty5034/dsh-git-forge#a3341ec2b28e3fb3b5fc3569012fc39acacc9fb2
README兼容性版本

兼容性与来源证明

Git Forge 以 dsh-git-forge 发布，当前版本为 0.1.5。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。

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

版本

0.1.5stable
2026/9/8

相关插件

正在加载相关插件…

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

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

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

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

认领这个 Plugin →
报告问题

相关插件

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

Client Ui Git Graph@linxin666/dsh-client-ui-git-graph外部 dsh Web GUI 插件：空会话 Git 分支选择器和 Git 图，包含实际的主机端 Git 操作与防护，作为 dsh 配置文件包Ssh@linxin666/dsh-sshdsh Web GUI 的远程 SSH 操作：主机配置存储（~/.dsh/dsh-ssh.json，可从 ~/.ssh/config 导入）、支持跳板主机的持久化 ssh2 连接池、exec / PTY Web 终端 / SFTP 传输 / 本地端口转发隧道 / 集群执行Opsdsh-ops适用于 Windows x64、Linux x64 和 macOS arm64/x64 的原生文件和 PTC 工具；仅限 Windows 的可选 Bash 负载和主机 PowerShell 集成Update@linxin666/dsh-update用于 dsh Web GUI 的自更新插件：探测 npm 上是否有更新的系列版本，并在原地运行所属配置的 pnpm 更新；可通过设置图标旁侧边栏中的触发器启动，并显示发布说明面板

README

dsh-git-forge

English | 简体中文

DeepSeek Harness community plugin: forge accounts + per-project grants + push policy in dsh-better-sidebar.

  • Account library: GitHub / Gitea / GitLab / Gitee / Bitbucket
  • Project grants (projectPathKey = workspace cwd)
  • Push guard: blocks bash git push / git remote add|set-url to non-granted hosts
  • Tokens in $DSH_HOME/git-forge/secrets.json (0600) — never in model context
  • Model tool GitForge (read-only policy)
  • Agent HTTPS git: after sidebar grants, agent bash git fetch/push can use the matching account via a Host-only credential helper (tokens never enter the model; R1 = exactly one granted token account per host)
  • UI aligned with dsh-ssh-tunnel

SSH remotes and system gh auth still use local SSH/gh. HTTPS under DSH agent shells is filled by this plugin’s helper from project grants; the push guard still decides where a project may push.

Requirements

  • DSH web profile with dsh-better-sidebar (≥ 0.12)
  • Node.js 18+

Install

macOS / Linux (Git Bash / WSL on Windows also works):

curl -fsSL https://raw.githubusercontent.com/thirsty5034/dsh-git-forge/main/scripts/install.sh | bash

Windows (PowerShell 5.1+ / pwsh):

irm https://raw.githubusercontent.com/thirsty5034/dsh-git-forge/main/scripts/install.ps1 | iex

Or via DSH CLI directly (GitHub source until the package is on npm):

export DSH_HOME=${DSH_HOME:-$HOME/.dsh}
dsh plugin --profile web add "dsh-git-forge@github:thirsty5034/dsh-git-forge"
dsh --profile web --dump-config | grep git-forge

After install: restart DSH web, then hard-refresh the browser (Cmd/Ctrl+Shift+R).

Options / local link / npm (later) 
# pin ref
curl -fsSL .../install.sh | bash -s main --restart
bash scripts/install.sh --from npm 0.1.1   # after npm publish

# local checkout
dsh plugin --profile web add "dsh-git-forge@link:/path/to/dsh-git-forge"
# or: ./scripts/sync-to-dsh.sh && dsh plugin add "dsh-git-forge@link:$DSH_HOME/local-plugins/dsh-git-forge"

Discoverability

  • GitHub topics: dsh-plugin, deepseek-harness, dsh (required for dsh.so auto-index)
  • Install from GitHub (current): see Install above
  • Store listings may lag crawlers; source of truth is this repository

Data

Under $DSH_HOME/git-forge/:

FilePurpose
accounts.jsonAccount metadata (no tokens)
secrets.jsonTokens (0600)
grants.jsonprojectPathKey → accountIds[] + enforce policy

Sidebar

  1. Project access — accounts for the current project + enforce push
  2. Accounts — CRUD, API token probe
  3. Policy — allowed gitHosts; unbound-project default

Model tool

GitForge action=list_accounts
GitForge action=get_policy
GitForge action=list_project_accounts
GitForge action=check_remote url=git@github.com:org/repo.git

Agent HTTPS and project path

  • Grant key = DSH session workspace (DSH_GIT_FORGE_PROJECT in agent shells), not nested package path
  • Helper resolution: env → exact cwd → walk parents under /workspace
  • R1: auto-fill only with exactly one granted token account for that host
  • Push guard checks inline URLs and bare git push / git push origin (resolves remote URL)

Security

  • Tokens never appear in tool/API results or model context
  • Push policy is enforced in Host tools.guard
  • With no project grants, push is not blocked by default (progressive enablement); helper also supplies no credentials

Development

npm test
npm run check
./scripts/sync-to-dsh.sh   # optional: copy into $DSH_HOME/local-plugins

License

MIT — see LICENSE.