@sakikoTGW/dsh-plugin-resolver-dshgo

dsh-plugin-resolver 的 dsh-go 手机 harness 适配版：原生卡片、镜像/GitHub 代理回退、deep 校验；含两轮消融数据与 6 条问题记录

Ecosystem pluginDeveloperDataGitHub integration

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 does

dsh-plugin-resolver 的 dsh-go 手机 harness 适配版：原生卡片、镜像/GitHub 代理回退、deep 校验；含两轮消融数据与 6 条问题记录

Installation

dsh plugin --profile web add dsh-plugin-resolver-dshgo

Install method: npm · 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.3 current
v0.1.3-go.1	○

Install compatibility (by plugin version, dsh versions within)

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

v0.1.3-go.1github○ 1 ecosystem plugin2026-10-28

https://github.com/sakikoTGW/dsh-plugin-resolver-dshgo

○dsh 0.2.1-rc.3current2026-10-28Ecosystem plugin

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-rc.3
• Plugin artifact: github · https://github.com/sakikoTGW/dsh-plugin-resolver-dshgo#v0.1.3-go.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

Not tested

Install test ran: the package installs but declares no dsh.bundle and mounts no capability — an ecosystem plugin, not a usable dsh plugin (shown as L5 · ecosystem plugin)

Ecosystem plugin

ID: dsh-plugin-resolver-dshgo@v0.1.3-go.1@dsh0.2.1-rc.3 · profile: l4-sandbox

Issued: 2026-10-28 · expires: 2026-11-04

View checks & evidence

L1 · Found✓ Passed

↳ carried from earlier record dsh-plugin-resolver-dshgo@v0.1.3-go.1@dsh0.2.1-rc.3 (l4-sandbox)

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-plugin-resolver-dshgo@v0.1.3-go.1@dsh0.2.1-rc.3 (l4-sandbox)

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-plugin-resolver-dshgo@v0.1.3-go.1@dsh0.2.1-rc.3 (l4-sandbox)

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

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

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

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

spec github:sakikoTGW/dsh-plugin-resolver-dshgo#v0.1.3-go.1 · channel GitHub source · outcome ran · exit 0

check took: 15.1s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

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

spec github:sakikoTGW/dsh-plugin-resolver-dshgo#v0.1.3-go.1 · channel GitHub source · outcome ran · exit 0

check took: 15.1s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

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

spec github:sakikoTGW/dsh-plugin-resolver-dshgo#v0.1.3-go.1 · channel GitHub source · outcome ran · exit 0

check took: 15.1s

L5 · Run tested– Not tested

This level was not executed in this scan.

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-resolver-dshgoAutomated 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 versionv0.1.3-go.1dsh manifest

scanned version0.1.3-go.1npm2026-10-28

current version0.1.3-go.1same version

vet verdictclean · npm

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

show static findings (1)

warningchildProcess · code-execlogic/util.js:172
const child = spawn(file, argv, {

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-10-27

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/sakikoTGW/dsh-plugin-resolver-dshgo

Plugin notes

What is @sakikoTGW/dsh-plugin-resolver-dshgo?

@sakikoTGW/dsh-plugin-resolver-dshgo is an ecosystem plugin maintained by @sakikoTGW: 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 @sakikoTGW/dsh-plugin-resolver-dshgo?

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

@sakikoTGW/dsh-plugin-resolver-dshgo

What it does

Installation

Verification & Compatibility○ Ecosystem plugin

Author badges

Security Report

Activity

Source

Author README