Install verification: Ecosystem app: not installed via dsh plugin add, so the L1-L5 plugin install-verification ladder does not apply; the security scan still runs.Install verification details →
What it doesAI
A multi-device runtime and personal workbench that lets one persistent agent run across many devices on DeepSeek Harness.
- Runs one persistent agent across many devices
- Multi-device capability runtime built on DeepSeek Harness
- Personal workbench for persistent agent workflows
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
Ecosystem apps are not installable via dsh plugin add: desktop / web shells install or deploy through their own release channel (GitHub Releases or the project site).
The level reads L5 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (the L1-L5 ladder does not rate them); the security scan still runs.
Verification & Compatibility◼ Ecosystem app
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
| plugin \ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.2 |
|---|---|---|
| pc-windows | · | · |
| fdcf27 | ◼ | ◼ |
pc-windowsgithub2026-10-18
https://github.com/jiale-li-orion/dsh-meshfin
Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.
fdcf27github◼ 2 ecosystem app2026-10-21
https://github.com/jiale-li-orion/dsh-meshfin
◼dsh 0.2.1-rc.2current2026-10-21Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/jiale-li-orion/dsh-meshfin (version unstated)
ID: dsh-meshfin@fdcf27@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-21 · expires: 2026-10-28
View checks & evidence
↳ carried from earlier record dsh-meshfin@pc-windows@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-meshfin@pc-windows@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-meshfin@pc-windows@dsh0.2.1-rc.2 (l3-fullscan)
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.
◼dsh 0.2.1-alpha.22026-10-14Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/jiale-li-orion/dsh-meshfin (version unstated)
ID: dsh-meshfin@fdcf27@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-14 · expires: 2026-10-21
View checks & evidence
↳ carried from earlier record dsh-meshfin@pc-windows@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-meshfin@pc-windows@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-meshfin@pc-windows@dsh0.2.1-rc.2 (l3-fullscan)
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.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-meshfin/)`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.
Static low, dynamic low — stricter wins → overall low.
v0.1.0-rc.7pc-windowsgit2026-10-21pc-windowssame versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (9)
- criticalmanifest-bare-fs · sandbox
apps/cli/config/agent-presets/minimal/agent.cordis.ymlMutating filesystem tool shares a bare fs-local backend - warningmanifest-fs-unfenced · sandbox
apps/cli/config/agent-presets/code/agent.cordis.ymlMutating filesystem tool has no explicit fs backend in realm - warningmanifest-search-unfenced · sandbox
apps/cli/config/agent-presets/code/agent.cordis.ymlSearch tool reads without an explicit fs mount - warningmanifest-shell-unfenced · sandbox
apps/cli/config/agent-presets/code/agent.cordis.ymlShell tool without a sandbox runner or policy in realm - warningmanifest-fs-unfenced · sandbox
apps/cli/config/agent-presets/cordis/agent.cordis.ymlMutating filesystem tool has no explicit fs backend in realm - warningmanifest-search-unfenced · sandbox
apps/cli/config/agent-presets/cordis/agent.cordis.ymlSearch tool reads without an explicit fs mount - warningmanifest-shell-unfenced · sandbox
apps/cli/config/agent-presets/cordis/agent.cordis.ymlShell tool without a sandbox runner or policy in realm - warningmanifest-shell-unfenced · sandbox
apps/cli/config/agent-presets/minimal/agent.cordis.ymlShell tool without a sandbox runner or policy in realm - warningmanifest-shell-unfenced · sandbox
apps/cli/config/agent-presets/minimal/agent.cordis.ymlShell tool without a sandbox runner or policy in realm
show 1 audit findings
- lowExample ACP composition disables the sandbox for ANY DSH_SNAPSHOT value, including empty/0/false
examples/acp-agent/cordis.yml:30In this example app only, defining DSH_SNAPSHOT at all (even as '' , '0' or 'false') selects danger-full-access, and the matching approval row (line ~45) then resolves to policy 'never', so bash/fs calls run unconfined and unprompted. It affects the examples/ snapshot harness tree that the operator launches deliberately; it is not reachable from the plugin's own code path and cannot be triggered by a remote client.
Harvested files are dsh monorepo bundle YAML, fixtures and type declarations, not plugin runtime code; the flagged !!js config expressions are explained and no reachable flaw was 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-08-20
• Stars: ★ 1 · Forks: 0
• Health: Active — committed within last 30 days
Source
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
