@liupengyang-1008/dsh-plugin-development

Development-time skill for building DSH (DeepSeek Harness) / Cordis plugins end to end - plugin forms, templates, an API cookbook, catalogued pitfalls, packaging and publishing.

Ecosystem pluginDeveloperNetwork

Verification

L5 · Ecosystem plugin

Ecosystem plugin

Risk

LowRisk

Health

Active

Trust

Silver

Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →

What it doesAI

Development-time skill covering end-to-end DSH/Cordis plugin building: plugin forms, templates, API cookbook, catalogued pitfalls, and publishing.

Explains DSH/Cordis plugin forms and ready-made templates
API cookbook plus catalogued pitfalls to avoid common mistakes
Covers packaging and publishing plugins end to end

developerAI

Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.

Installation

dsh plugin --profile web add github:liupengyang-1008/dsh-plugin-development#v1.7.0

verified v1.7.0

Install method: GitHub · runtime test inconclusive (L5 unknown)

Verification & Compatibility○ Ecosystem plugin

Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.

External credentials (plugin-level): none detected

Declared DSH compatibilityfrom package.json · peerDependencies

package manifest not collected

package manifest not collected — the declared range is unknown.

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)

○ Ecosystem plugin

At-a-glance → evidence in the cards below

plugin ＼ dsh	dsh 0.2.1-rc.2 current	dsh 0.2.1-alpha.4	dsh 0.2.1-alpha.2
v1.7.0	○	·	·
v1.5.1	·	○	·

Install compatibility (by plugin version, dsh versions within)

Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed

v1.7.0github○ 1 ecosystem plugin2026-10-21

https://github.com/liupengyang-1008/dsh-plugin-development

○dsh 0.2.1-rc.2current2026-10-21Ecosystem plugin

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-rc.2
• Plugin artifact: github · https://github.com/liupengyang-1008/dsh-plugin-development#v1.7.0

Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)

L1 static

Passed

L2 static

Passed

L3 static

Passed

L4 sandbox

Passed

L5 runtime

Unknown

Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)

Ecosystem plugin

ID: dsh-plugin-development-6@v1.7.0@dsh0.2.1-rc.2 · profile: l3-fullscan

Issued: 2026-10-21 · expires: 2026-10-28

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-21

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-21

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19

spec github:liupengyang-1008/dsh-plugin-development#v1.7.0 · channel GitHub source · outcome ran · exit 0

check took: 1.8s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19

spec github:liupengyang-1008/dsh-plugin-development#v1.7.0 · channel GitHub source · outcome ran · exit 0

check took: 1.8s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19

spec github:liupengyang-1008/dsh-plugin-development#v1.7.0 · channel GitHub source · outcome ran · exit 0

check took: 1.8s

L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19

spec github:liupengyang-1008/dsh-plugin-development#v1.7.0 · install mode reused L4 scratch

check took: 23ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

Source: DSH runtime · Method: web boot · Captured 2026-10-19

ready line dsh web: http://127.0.0.1:51137/?token=…

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

Source: DSH runtime · Method: HTTP request · Captured 2026-10-19

path / · HTTP 200 · took 23ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE? Unknown

Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-19

verdict not-found · entries 149

phases: active 121 · null 28

not present in web-profile loader inventory

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

v1.5.1github○ 1 ecosystem plugin2026-10-18

https://github.com/liupengyang-1008/dsh-plugin-development

○dsh 0.2.1-alpha.42026-10-18Ecosystem plugin

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.4
• Plugin artifact: github · https://github.com/liupengyang-1008/dsh-plugin-development#v1.5.1

Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)

L1 static

Passed

L2 static

Passed

L3 static

Passed

L4 sandbox

Passed

L5 runtime

Unknown

Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)

Ecosystem plugin

ID: dsh-plugin-development-6@v1.5.1@dsh0.2.1-alpha.4 · profile: l3-fullscan

Issued: 2026-10-18 · expires: 2026-10-25

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-21

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-21

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17

spec github:liupengyang-1008/dsh-plugin-development#v1.5.1 · channel GitHub source · outcome ran · exit 0

check took: 2.7s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17

spec github:liupengyang-1008/dsh-plugin-development#v1.5.1 · channel GitHub source · outcome ran · exit 0

check took: 2.7s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17

spec github:liupengyang-1008/dsh-plugin-development#v1.5.1 · channel GitHub source · outcome ran · exit 0

check took: 2.7s

L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17

spec github:liupengyang-1008/dsh-plugin-development#v1.5.1 · install mode reused L4 scratch

check took: 492ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

Source: DSH runtime · Method: web boot · Captured 2026-10-17

ready line dsh web: http://127.0.0.1:56874/?token=…

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

Source: DSH runtime · Method: HTTP request · Captured 2026-10-17

path / · HTTP 200 · took 492ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE? Unknown

Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-17

verdict not-found · entries 149

phases: active 121 · null 28

not present in web-profile loader inventory

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

Only the latest 3 published versions are shown; source-snapshot (commit hash) groups, unstated groups and older versions are omitted — the full archive stays in the data layer (snapshot/unstated groups appear only when a plugin has no published version).

Author badges

Embed the official badges in your README to showcase security & install-test status:

Security Report

Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.

dsh-plugin-development-6Automated review · daily

Static low, dynamic low — stricter wins → overall low.

static low→dynamic low→overall low

0 critical·0 high1 medium-risk findings hidden

lowoverall · low

1static scan · vet primaryvet AST static analysis (npm artifact or git source)

Version binding

plugin version—

scanned versionv1.7.0git2026-10-21

current versionv1.7.0same version

vet verdictclean · git

Vet is an AST static scan (npm artifact or git source).

show static findings (5)

warningnetIp · networkscripts/dsh-sync.sh:90
export https_proxy=http://127.0.0.1:7890
warningnetIp · networkscripts/dsh-sync.sh:91
export http_proxy=http://127.0.0.1:7890
warningcurlDownload · networkscripts/dsh-sync.sh:139
if ! curl -fL --connect-timeout 20 --max-time 600 -o "$TAR" "$TARBALL_URL"; then
warningmanifest-shell-unfenced · sandboxassets/minimal-bundle/cordis.patch.yml
Shell tool without a sandbox runner or policy in realm
warningmanifest-shell-unfenced · sandboxassets/minimal-bundle/cordis.patch.yml
Shell tool without a sandbox runner or policy in realm

2dynamic auditmodel reads redacted source context · never executes plugin code

highest gradelow

merged intooverall low

audited at2026-10-19

findings0 critical·0 high0 medium / 2 low hidden

show 2 audit findings

lowExample bundle template runs an npx-fetched package by bare placeholder name and forwards an API key to itassets/minimal-bundle/cordis.patch.yml:19
This is a copy-paste template for @deepseek-ai/dsh-mcp-client: `command: npx`, `- -y`, `- my-mcp-server@1.2.3`. The package name is an unscoped placeholder that an attacker could register on the public registry, and line 27 (`MY_API_KEY: !!js process.env.MY_API_KEY ?? ''`) forwards the developer's key into that downloaded subprocess, which runs with DSH-equivalent privileges. Exploitation needs the developer to copy the template, keep the placeholder name and restart DSH; the file itself returns an empty string when the env var is unset and its comments explicitly warn against floating version
lowSync helper fetches and extracts a remote tarball from a user-supplied --repo/--mirror URLscripts/dsh-sync.sh
FETCH_URL is built from user-supplied `--repo`/`--mirror` (or defaults to the official GitHub repo) and is used both for `git ls-remote`/`git clone` and for the tarball mode, where the downloaded archive is written to vendor/dsh-master.tar.gz and extracted with `tar -xzf` into the skill's vendor/ directory. A hostile mirror URL therefore yields attacker-controlled files inside the installed skill directory (no code is executed and no `pnpm/npm install` runs). The operation is developer-initiated and gated by an interactive confirmation (unless --yes), plus a gzip test and a >=1000-file sanity

No runtime-loaded code: all 12 files are docs, example templates and developer-run helper scripts; only two low-risk hardening items found.

Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.

Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.

Activity

Last commit 2026-10-18 · activity: Active

• Repo created: 2026-09-11

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/liupengyang-1008/dsh-plugin-development

Plugin notes

What is @liupengyang-1008/dsh-plugin-development?

@liupengyang-1008/dsh-plugin-development is an ecosystem plugin maintained by @liupengyang-1008: it installs via dsh plugin add but declares no dsh.bundle and mounts nothing — installing it adds no plugin capability; use the source repository directly. It is cataloged on dsh.so as a Developer entry, with a public source repository and automated static security scan.

How do I install @liupengyang-1008/dsh-plugin-development?

This is an ecosystem plugin: it installs via dsh plugin add but declares no dsh.bundle and mounts nothing — installing one adds no plugin capability; use the source repository directly. Its level reads L5 · Ecosystem plugin; the security scan still runs.

How does the security scan relate to a manual audit?

Both layers are automated, not a manual audit: the static scan is heuristic analysis of the repository source (it can produce false positives and miss context), and the dynamic security audit has a model read the harvested source context with secret files stripped and content redacted inline — plugin code is never executed. The dynamic audit only covers plugins static-flagged at warn or above, and its conclusion can only raise the combined verdict, never exempt it. Neither layer is a manual security audit or an endorsement; before using a plugin, review the repository and installed permissions, and combine both with the verification level (L4/L5) and health signals.

"DeepSeek Harness (dsh) is an open-source agent harness developed by DeepSeek AI. It uses an architecture where everything is a plugin, and is powered by Cordis."
— DeepSeek Harness README

Sources: GitHub repository · DeepSeek Harness README · security scan data · Maintained by dsh.so · Last updated 2026-10-18

@liupengyang-1008/dsh-plugin-development

What it doesAI

Installation

Verification & Compatibility○ Ecosystem plugin

Author badges

Security Report

Activity

Source

Author README