@Han-1413141/dsh-pnpm-build-control

DSH 插件：在添加插件页面统一开关所有配置的 pnpm 构建脚本审批，首次关闭显示风险确认。

PluginDeveloperSecurityGitHub integration

Verification

L4 · Install tested

Failed

Risk

LowRisk

Health

Active

Trust

Silver

Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.2 · last checked 10-20Install verification details →

What it doesAI

Adds a build-script approval toggle in DSH's Add Plugin dialog to switch pnpm allowBuilds on or off for all configs at once.

One toggle under the package name field in the Add Plugin dialog
Off = all DSH configs let every dependency run build scripts
Expand to inspect desktop, web, tui and other configs' real state

developerAIgithubAI

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:Han-1413141/dsh-pnpm-build-control#v0.1.4

verified v0.1.4

Install method: GitHub · sandbox install ok, web smoke failed (L5)

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 · peerDependencies

author declared no dsh version requirement

○ The author declares no dsh version requirement — install is not blocked by version.

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.2 current	dsh 0.2.1-alpha.4	dsh 0.2.1-alpha.2
v0.1.4	✗	✗	✗

Install compatibility (by plugin version, dsh versions within)

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

v0.1.4github3 failed2026-10-20

https://github.com/Han-1413141/dsh-pnpm-build-control

✗dsh 0.2.1-rc.2current2026-10-20L5 · failed

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-rc.2
• Plugin artifact: github · https://github.com/Han-1413141/dsh-pnpm-build-control#v0.1.4

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-pnpm-build-control@v0.1.4@dsh0.2.1-rc.2 · profile: l4-sandbox

Issued: 2026-10-20 · expires: 2026-10-27

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

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

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

spec github:Han-1413141/dsh-pnpm-build-control#v0.1.4 · channel GitHub source · outcome ran · exit 0

check took: 11.3s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

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

spec github:Han-1413141/dsh-pnpm-build-control#v0.1.4 · channel GitHub source · outcome ran · exit 0

check took: 11.3s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

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

spec github:Han-1413141/dsh-pnpm-build-control#v0.1.4 · channel GitHub source · outcome ran · exit 0

check took: 11.3s

L5 · Run tested✕ Failed

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

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

spec github:Han-1413141/dsh-pnpm-build-control#v0.1.4 · 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.

✗dsh 0.2.1-alpha.42026-10-18L5 · failed

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.4
• Plugin artifact: github · https://github.com/Han-1413141/dsh-pnpm-build-control#v0.1.4

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-pnpm-build-control@v0.1.4@dsh0.2.1-alpha.4 · profile: l4-sandbox

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

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

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 github:Han-1413141/dsh-pnpm-build-control#v0.1.4 · channel GitHub source · outcome ran · exit 0

check took: 7.0s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

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

spec github:Han-1413141/dsh-pnpm-build-control#v0.1.4 · channel GitHub source · outcome ran · exit 0

check took: 7.0s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

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

spec github:Han-1413141/dsh-pnpm-build-control#v0.1.4 · channel GitHub source · outcome ran · exit 0

check took: 7.0s

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 github:Han-1413141/dsh-pnpm-build-control#v0.1.4 · 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.

✗dsh 0.2.1-alpha.22026-10-14L5 · failed

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.2
• Plugin artifact: github · https://github.com/Han-1413141/dsh-pnpm-build-control#v0.1.4

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-pnpm-build-control@v0.1.4@dsh0.2.1-alpha.2 · profile: l4-sandbox

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

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

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

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

spec github:Han-1413141/dsh-pnpm-build-control#v0.1.4 · channel GitHub source · outcome ran · exit 0

check took: 9.2s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

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

spec github:Han-1413141/dsh-pnpm-build-control#v0.1.4 · channel GitHub source · outcome ran · exit 0

check took: 9.2s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

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

spec github:Han-1413141/dsh-pnpm-build-control#v0.1.4 · channel GitHub source · outcome ran · exit 0

check took: 9.2s

L5 · Run tested✕ Failed

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

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

spec github:Han-1413141/dsh-pnpm-build-control#v0.1.4 · 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.

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-pnpm-build-controlAutomated review · daily

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

static low→dynamic no conclusion→overall low

0 critical·0 high

lowoverall · low

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

Version binding

plugin versionv0.1.4dsh manifest

scanned versionv0.1.4git2026-10-21

current versionv0.1.4same version

vet verdictclean · git

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

show static findings (1)

warningnetIp · networkscripts/preview.mjs:39
server.listen(0,'127.0.0.1',()=>console.log(JSON.stringify({url:`http://127.0.0.1:${server.address().port}`,home})));

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

not in the dynamic queue (queue only covers plugins static-flagged at warn or above) — this does not mean the dynamic audit found it safe.

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

• Repo created: 2026-09-30

• Stars: ★ 1 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/Han-1413141/dsh-pnpm-build-control

Plugin notes

What is the @Han-1413141/dsh-pnpm-build-control DeepSeek Harness plugin?

@Han-1413141/dsh-pnpm-build-control is a DeepSeek Harness plugin maintained by @Han-1413141. It is cataloged on dsh.so as a Developer plugin for GitHub integration 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 @Han-1413141/dsh-pnpm-build-control?

Run dsh plugin --profile web add github:Han-1413141/dsh-pnpm-build-control#v0.1.4 in a DeepSeek Harness (dsh) environment. This exact command has been verified by a real install inside an isolated windows-acl sandbox (L4).

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

@Han-1413141/dsh-pnpm-build-control

What it doesAI

Installation

Verification & Compatibility

Author badges

Security Report

Activity

Source

Author README