DeepSeekDSH
Independent community guideNot affiliated with DeepSeek.Official source snapshot

dknowc-dsh

Trusted office suite for government/enterprise work by Beijing Caizhi Technology (深知可信智能): three skills — trusted consulting (policy/regulation Q&A with citation markers + provenance HTML), trusted search (authoritative policy/standard retrieval with traceable HTML + clean Markdown), and official-document writing (draft/rewrite/Word/red-head delivery); all interfaces go through the dknowc trusted workbench MCP (Bearer auth), products land in the session workspace, one-time key setup persists for later sessions; ships on npm as dknowc-dsh.

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

Review info: an independent structural review record is available for install structure, README, lifecycle scripts and runtime-artifact evidence. This is not a full code security audit.

Community signals

Category

Skills

GitHub stars

1

npm downloads

Discovery registry added

2026-08-18

Review information

Scanner status

auto-resolved

Review mode

automatic

Last checked

2026-09-17T07:42:05.108Z

Build approval required

No

Lifecycle scripts

No

Runtime artifacts committed

Yes

Documented profiles

web

Review reasons
  • readme-alias-is-unverified-but-exact-current-repository-install-is-self-contained

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 →