@SouthernSibyl/dsh-gotofile

DSH plugin: lists the files a conversation turn produced or changed as plain text, and reveals a file in the OS file manager on double-click.

PluginProductivityFile

Verification

L5 · Run tested

Verified

Risk

LowRisk

Health

Active

Trust

Gold

Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked 10-20Install verification details →

What it does

DSH plugin: lists the files a conversation turn produced or changed as plain text, and reveals a file in the OS file manager on double-click.

Installation

dsh plugin --profile web add dsh-gotofile

verified 1.0.4

Install method: npm · runtime verified (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
1.0.5	·	·
1.0.4	✓	·
1.0.2	·	✗

Install compatibility (by plugin version, dsh versions within)

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

1.0.5npm2026-10-21

dsh-gotofile

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

1.0.4npm✓ 1 runtime-verified2026-10-20

dsh-gotofile

✓dsh 0.2.1-rc.2current2026-10-20L5 · runtime verified

Environment & artifact

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

Passed

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

L5 · runtime verified · valid for dsh 0.2.1-rc.2

ID: dsh-gotofile@1.0.4@dsh0.2.1-rc.2 · profile: l4-sandbox

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

View checks & evidence

L1 · Found✓ Passed

↳ carried from earlier record dsh-gotofile@1.0.5@dsh0.2.1-rc.2 (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-gotofile@1.0.5@dsh0.2.1-rc.2 (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-gotofile@1.0.5@dsh0.2.1-rc.2 (l3-fullscan)

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

spec dsh-gotofile · channel npm package · outcome ran · exit 0

check took: 2.5s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

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

spec dsh-gotofile · channel npm package · outcome ran · exit 0

check took: 2.5s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

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

spec dsh-gotofile · channel npm package · outcome ran · exit 0

check took: 2.5s

L5 · Run tested✓ Passed

active in loader tree (150 entries)

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

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

spec dsh-gotofile · install mode reused L4 scratch

check took: 177ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

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

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

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

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

path / · HTTP 200 · took 177ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE✓ Passed

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

verdict active · entries 150

match: include:goto-file · dsh-gotofile · phase active

phases: active 122 · null 28

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

1.0.2npm1 failed2026-10-18

dsh-gotofile

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

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.4
• Plugin artifact: npm · dsh-gotofile@1.0.2

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-gotofile@1.0.2@dsh0.2.1-alpha.4 · profile: l4-sandbox

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

View checks & evidence

L1 · Found✓ Passed

↳ carried from earlier record dsh-gotofile@1.0.5@dsh0.2.1-rc.2 (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-gotofile@1.0.5@dsh0.2.1-rc.2 (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-gotofile@1.0.5@dsh0.2.1-rc.2 (l3-fullscan)

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

spec dsh-gotofile · channel npm package · outcome ran · exit 0

check took: 3.0s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

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

spec dsh-gotofile · channel npm package · outcome ran · exit 0

check took: 3.0s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

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

spec dsh-gotofile · channel npm package · outcome ran · exit 0

check took: 3.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 dsh-gotofile · 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.

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-gotofileAutomated 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 versionv1.0.5dsh manifest

scanned version1.0.5npm2026-10-21

current version1.0.5same version

vet verdictclean · npm

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

show static findings (1)

warningshellExec · shelllib/index.js:947
execFile(command, cleanArgs, { timeout: 10000 }, (error) => {

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

• Repo created: 2026-10-16

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/SouthernSibyl/dsh-gotofile

Plugin notes

What is the @SouthernSibyl/dsh-gotofile DeepSeek Harness plugin?

@SouthernSibyl/dsh-gotofile is a DeepSeek Harness plugin maintained by @SouthernSibyl. It is cataloged on dsh.so as a Productivity plugin for File 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 @SouthernSibyl/dsh-gotofile?

Run dsh plugin --profile web add dsh-gotofile in a DeepSeek Harness (dsh) environment. This exact command has been verified by a real install inside an isolated windows-acl sandbox (L4) plus web smoke testing (L5).

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

@SouthernSibyl/dsh-gotofile

What it does

Installation

Verification & Compatibility

Author badges

Security Report

Activity

Source

Author README