DeepSeekDSH
Independent community guideNot affiliated with DeepSeek.Official source snapshot

source-code-mgmt

Code management panel for the DSH web UI that handles everyday Git in five steps: ① env check auto-detects git/gh/ssh and one-click installs missing tools (gh mirror download sources speed up installs, Windows included) with check-update; ② SSH ed25519 key generation / connection tests plus one-click 443 config to bypass blocked port 22, with the Gitee personal token configured here; ③ repo status, side-by-side diffs, stage/commit, branch switching, history with revert/cherry-pick, one-click repo creation and push, auto-ignoring >100MB files; ④ lists all repos of your account for one-click clone; ⑤ five-step npm publish wizard. GitHub / Gitee dual-platform, with the UI switching between 中文 and English live.

Independent editorial review: DeepSeekDSHSource checked: 0.1.5-rc.2 · 2026-09-11
On this page
Third-party

Review info: no independent structural review record is currently matched.

Community signals

Category

Git & Code Review

GitHub stars

0

npm downloads

Discovery registry added

2026-08-30

Review information

Scanner status

No review data

Review mode

No review data

Last checked

No review data

Build approval required

No review data

Lifecycle scripts

No review data

Runtime artifacts committed

No review data

Documented profiles

No review data

Why this site does not provide the install command

A third-party DSH plugin is executable local code. Even when structural review evidence exists, registry data, stars and metadata cannot prove the code is non-malicious. Read the current author repository and perform your own review in a disposable environment.

Install and usage source

This site links to the author's source, npm page and community registry instead of redistributing commands. A plugin may add Web UI, Settings, agent tools or background capabilities; follow the author README for the actual entry point.

Minimum checks before install

  1. Confirm package.json, the bundle patch and README belong to the same author repository.
  2. Inspect preinstall/install/postinstall/prepare, child_process, shell, filesystem, network calls and credential access.
  3. First install into a disposable profile/workspace without production credentials or an important repository.
  4. If pnpm asks for allowBuilds/build approval, treat it as permission to execute third-party code during installation; do not approve mechanically.
  5. For reproducibility, pin an exact npm version or Git commit yourself instead of depending on main/latest.
Third-party does not mean unsafe, and review is not a security certification

“Third-party” only means the plugin is not an official DeepSeek plugin. Structural checks improve transparency but cannot prove business logic is non-malicious or fully audit dependencies, future updates or runtime behavior.

Sources

THIRD-PARTY PLUGINSSearch the live registry
Community Plugin Explorer →