dsh-pua

DSH PUA — 为 DeepSeek Harness 提供 PUA 任务推进、角色风味、验收循环和运行状态卡片 · PUA task persistence, personas, verification loops, and live status cards for DeepSeek Harness

PluginAI ModelsKnowledgeAutomationStorageMemory

Verification

L3 · Install spec

Failed

Risk

LowRisk

Health

Active

Trust

Silver

Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.3 · last checked 10-26Install verification details →

What it doesAI

Prompt-engineering add-on for DeepSeek Harness that keeps agents persistent, applies personas, and loops in verification before finishing.

Keeps the agent persistent on a task instead of giving up early
Applies personas to steer agent behaviour
Runs verification loops before the agent calls work done

aiAImemoryAI

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 @michengai/dsh-pua@1.0.5

security scan passed · npm package v1.0.5

Install method: npm · sandbox install failed (L4)

Verification & Compatibility

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 · peerDependenciesdeclared in 0.3.27

supports any of: dsh 0.1.2-rc.1 or dsh 0.1.5-rc.1 or dsh 0.1.5-rc.2 or dsh 0.1.5-rc.3 or dsh 0.1.7-rc.1 or dsh 0.1.7-rc.2 or dsh 0.2.0-rc.1 or dsh 0.2.0-rc.2 or dsh 0.2.1-alpha.2

Based on 1 requirement(s) across 16 @deepseek-ai/dsh-* packages.

raw ranges

0.1.2-rc.1 || 0.1.5-rc.1 || 0.1.5-rc.2 || 0.1.5-rc.3 || 0.1.7-rc.1 || 0.1.7-rc.2 || 0.2.0-rc.1 || 0.2.0-rc.2 || 0.2.1-alpha.2 ×16

✗ Running dsh 0.2.1-rc.3 is outside the declared range — the official install gate rejects it (incompatible-version).

To force-install, grant an exact-version exemption: dsh plugin allow-version dsh-pua@0.3.27 0.2.1-rc.3 (the exemption lives in the local profile; this site does not assume one)

Whether it actually runs is a separate question → see the measured matrix below (L1–L5).

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

At-a-glance → evidence in the cards below

plugin ＼ dsh	dsh 0.2.1-rc.3	dsh 0.2.1-rc.2	dsh 0.2.1-alpha.4	dsh 0.2.1-alpha.2	dsh 0.2.0-rc.1
1.0.3	·	·	·	·	·
1.0.1	·	✗	·	·	·
0.3.28	·	·	✓	·	·
0.3.27	·	·	·	·	·
0.3.26	·	·	·	·	·

Install compatibility (by plugin version, dsh versions within)

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

1.0.3npm2026-10-26

@michengai/dsh-pua

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

1.0.1npm1 failed2026-10-18

@michengai/dsh-pua

✗dsh 0.2.1-rc.22026-10-18L5 · failed

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-rc.2
• Plugin artifact: npm · @michengai/dsh-pua@1.0.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

Failed

Sandbox install failed

L5 · failed

ID: dsh-pua@1.0.1@dsh0.2.1-rc.2 · profile: l4-sandbox

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

View checks & evidence

L1 · Found✓ Passed

↳ carried from earlier record dsh-pua@1.0.3@dsh0.2.1-rc.3 (l3-fullscan)

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

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

L2 · Structured✓ Passed

↳ carried from earlier record dsh-pua@1.0.3@dsh0.2.1-rc.3 (l3-fullscan)

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

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

L3 · Install spec✓ Passed

↳ carried from earlier record dsh-pua@1.0.3@dsh0.2.1-rc.3 (l3-fullscan)

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

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

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

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-18

spec @michengai/dsh-pua · channel npm package · outcome ran · exit 0

check took: 9.1s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

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

spec @michengai/dsh-pua · channel npm package · outcome ran · exit 0

check took: 9.1s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

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

spec @michengai/dsh-pua · channel npm package · outcome ran · exit 0

check took: 9.1s

L5 · Run tested✕ Failed

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

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

spec @michengai/dsh-pua · install mode reused L4 scratch

check took: 0ms

Web boot readyL5.2_WEB_BOOT_READY✕ Failed

plugin tree failed to load

HTTP endpoint servedL5.3_HTTP_SERVED✕ Failed

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

0.3.28npm✓ 1 runtime-verified2026-10-15

@michengai/dsh-pua

✓dsh 0.2.1-alpha.42026-10-15L5 · runtime verified

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.4
• Plugin artifact: npm · @michengai/dsh-pua@0.3.28

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

Passed

Install + runtime smoke verified in the dsh sandbox — installs and runs

L5 · runtime verified · valid for dsh 0.2.1-alpha.4

ID: dsh-pua@0.3.28@dsh0.2.1-alpha.4 · profile: l4-sandbox

Issued: 2026-10-15 · expires: 2026-10-22

View checks & evidence

L1 · Found✓ Passed

↳ carried from earlier record dsh-pua@1.0.3@dsh0.2.1-rc.3 (l3-fullscan)

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

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

L2 · Structured✓ Passed

↳ carried from earlier record dsh-pua@1.0.3@dsh0.2.1-rc.3 (l3-fullscan)

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

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

L3 · Install spec✓ Passed

↳ carried from earlier record dsh-pua@1.0.3@dsh0.2.1-rc.3 (l3-fullscan)

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

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

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

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-15

spec @michengai/dsh-pua · channel npm package · outcome ran · exit 0

check took: 8.9s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

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

spec @michengai/dsh-pua · channel npm package · outcome ran · exit 0

check took: 8.9s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

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

spec @michengai/dsh-pua · channel npm package · outcome ran · exit 0

check took: 8.9s

L5 · Run tested✓ Passed

active in loader tree (151 entries)

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

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

spec @michengai/dsh-pua · install mode reused L4 scratch

check took: 1.9s

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

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

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

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

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

path / · HTTP 200 · took 1.9s

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE✓ Passed

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

verdict active · entries 151

match: include:michengai-pua-remote · @michengai/dsh-pua/remote · phase active

match: include:michengai-pua · @michengai/dsh-pua · phase active

phases: active 123 · null 28

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

0.3.27npm2026-10-14

@michengai/dsh-pua

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

0.3.26npm2026-10-13

@michengai/dsh-pua

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

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-puaAutomated review · daily

Static low; dynamic no conclusion (static stands) → overall low.

static low→dynamic no conclusion→overall low

vet findings0 critical·0 high

lowoverall · low

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

Version binding

plugin versionv1.0.5dsh manifest

scanned version1.0.5npm2026-10-28

current version1.0.5same version

vet verdictclean · npm

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

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

not in the dynamic queue (the queue only covers plugins whose static tier is medium or above — medium/high/critical; since 2026-10-24 entries rated low are not audited even when dsh-only rules logged warnings) — this does not mean the dynamic audit found it safe.

Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to the static scan tier.

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-27 · activity: Active

• Repo created: 2026-09-12

• Stars: ★ 44 · Forks: 7

• Health: Active — committed within last 30 days

Source

GitHub: github.com/MichengAI/dsh-pua

Plugin notes

What is the dsh-pua DeepSeek Harness plugin?

dsh-pua is a DeepSeek Harness plugin maintained by @MichengAI. It is cataloged on dsh.so as a AI Models plugin for Memory tasks, with a public GitHub source, declared install command, and automated static scan results; plugins static-flagged at warn or above also carry a model-driven dynamic security audit record.

How do I install dsh-pua?

Run dsh plugin --profile web add @michengai/dsh-pua@1.0.5 in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run yet.

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; when it reaches a conclusion that conclusion is authoritative for the combined verdict — it may raise or lower it — and the static scan verdict (vet primary, dsh backstop) applies only when there is none. Exemptions stay manual: the audit never writes the suppression list. 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-27

dsh-pua

What it doesAI

Installation

Verification & Compatibility

Author badges

Security Report

Activity

Source

Author README