dsh-trading

Agent-native trading terminal built on DeepSeek Harness. Crypto, US, CN and HK in one three-column GUI, 19+ hot-swappable connectors, dry-run by default with human approval on every live order. BYOK, no data redistribution.

Ecosystem appFinanceAI ModelsTerminalDataNotificationsTerminal / Shell

Verification

L5 · Ecosystem app

Risk

LowRisk

Health

Active

Trust

Silver

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

Agent-native trading terminal for crypto and global markets with human-in-the-loop order approval.

Multi-market GUI for Crypto, US, CN, HK in three columns
19+ hot-swappable connectors for diverse trading venues
Dry-run mode with human approval before every live order

financeAInotificationAI

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

GitHub repository

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

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

◼ Ecosystem app

At-a-glance → evidence in the cards below

plugin ＼ dsh	dsh 0.2.1-alpha.2	dsh 0.1.7-rc.1	dsh 0.1.7-alpha.2	dsh 0.1.6-alpha.2	dsh 0.1.6-alpha.1
v0.6.3	·	·	·	·	·
v0.6.1	·	·	·	·	·
v0.5.0	·	·	·	·	·
v0.4.1	·	·	·	·	·
v0.2.1	·	·	·	·	·

Install compatibility (by plugin version, dsh versions within)

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

v0.6.3github2026-10-23

https://github.com/zhu1090093659/dsh-trading

Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.

v0.6.1github2026-10-18

https://github.com/zhu1090093659/dsh-trading

Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.

v0.5.0github2026-10-08

https://github.com/zhu1090093659/dsh-trading

Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.

v0.4.1github2026-09-30

https://github.com/zhu1090093659/dsh-trading

Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.

v0.2.1github2026-09-20

https://github.com/zhu1090093659/dsh-trading

Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.

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-trading-2Automated 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.0

scanned versionv0.6.3git2026-10-24

current versionv0.6.3same version

vet verdictclean · git

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-24): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); without one, the static/vet fused tier applies. 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 static/vet.

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

• Repo created: 2026-08-30

• Stars: ★ 275 · Forks: 34

• Health: Active — committed within last 30 days

Source

GitHub: github.com/zhu1090093659/dsh-trading

Plugin notes

What is dsh-trading?

dsh-trading is an ecosystem app maintained by @zhu1090093659, not a DSH plugin package — it cannot be installed via dsh plugin add; desktop / web shells ship through the project's own release channel. It is cataloged on dsh.so as a Finance entry, with a public source repository and automated static security scan.

How do I install dsh-trading?

This is an ecosystem app, not a plugin installable via dsh plugin add: desktop / web shells install or deploy through their own release channel. Its level reads L5 · Ecosystem app; 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/vet fused verdict 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-23

Was this page helpful?