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. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.Install verification details →
Data as of (UTC)
What it doesAI
Set of dsh plugins ported from eco-agent including permission gate, SM3 audit chain, and memory tree.
- Permission gate for access control
- SM3 audit chain for tamper-evident logs
- Memory tree for structured memory
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:xiejianjun000/eco-dsh-pluginsInstall method: GitHub · runtime test inconclusive (L5 unknown) · verified on dsh 0.2.2-rc.3
Trends
Four lines, four questions: total stars, stars gained this week, cumulative downloads, downloads this week. The GitHub pair comes from real-read sampling — a rotating daily shard, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
9 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-14 · 9 points
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
09-28 → 11-14 · 7 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
Only 0 points (< 3): no chart yet
no data yet
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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.2-rc.3 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| d07518 | ○ | · | · | · | · |
| 406279 | · | ✗ | ✗ | ✗ | ✗ |
d07518github○ 1 ecosystem plugin2026-11-16
https://github.com/xiejianjun000/eco-dsh-plugins
○dsh 0.2.2-rc.32026-11-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins#d075186a7a4978be7f6fe113d0f92f31980663d2
ID: eco-dsh-plugins@d075186a7a4978be7f6fe113d0f92f31980663d2@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
406279github○ 2 ecosystem plugin17 failed2026-11-14
https://github.com/xiejianjun000/eco-dsh-plugins
✗dsh 0.2.2-rc.12026-11-05Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-rc.52026-10-31Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-rc.32026-10-26Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-rc.22026-10-19Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
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-16Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
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-11Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.0-rc.22026-10-09Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.0-rc.12026-09-30Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.7-rc.22026-09-26Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.7-rc.12026-09-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
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.1.6-alpha.22026-09-20Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.6-alpha.12026-09-16Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.5-rc.22026-09-11Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.3-alpha.22026-09-08Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.3-alpha.12026-09-07Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.2-rc.12026-09-05Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins#406279
ID: eco-dsh-plugins@406279@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.2-alpha.12026-09-06Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dsh0.1.2-alpha.1 · profile: l3-fullscan
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.1-rc.22026-08-28Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.1-rc.2
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins#406279
ID: eco-dsh-plugins@406279@dsh0.1.1-rc.2 · profile: l3-fullscan
Issued: 2026-08-28 · expires: 2026-09-04
View checks & evidence
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.
✗prehistory2026-10-05Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/xiejianjun000/eco-dsh-plugins (version unstated)
ID: eco-dsh-plugins@406279@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Author badges
Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/eco-dsh-plugins/?ref=badge)`dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.
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 medium (authoritative when present) → overall medium.
v0.1.0dsh manifest0.1.0git2026-11-190.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticaldestructiveRm · destructive
scripts/runtime-verify.mjs:132const rL3Deny = await call('shell_exec', { command: 'rm -rf /tmp/x' }) - criticaldestructiveRm · destructive
scripts/runtime-verify.mjs:147const rRmDeny = await call('shell_exec', { command: 'rm -rf /tmp/x' })
show 3 audit findings
- mediumDefault L3 whitelist prefix-matches whole commands, so `git …` / `pip install …` inherit the allow decision with arbitrary arguments
packages/eco-permission-gate/src/index.ts:88The default whitelist is merged on every L3 (EXEC) decision, and matching is a raw string prefix on the model-supplied command. `git ` matches any git invocation (e.g. `git -c alias.x='!sh -c ...' x`, which makes git run an arbitrary shell command) and `pip install ` matches installation of any package from any index (build/setup hooks execute code). In mode='deny' or nonInteractive='ask' — exactly when the gate is supposed to block unapproved execution — these commands return next() and are executed without approval, so the gate's core protection is bypassed by attacker-influenced command tex
- mediumAllow rules that short-circuit the risk ladder match parameter globs against the raw command string, so `ls*` also allows `ls; <arbitrary command>`
packages/eco-permission-gate/src/index.ts:176Documented pattern `{ match: { tools: ['shell_exec'], params: { command: 'ls*' } }, action: 'allow' }` returns next() before the L1-L4 ladder, and '*'-globs are unanchored prefixes/suffixes on the unparsed shell string. Any command that merely begins with the allowed token (`ls; curl … | sh`, `ls && rm -rf …`) is therefore approved without user interaction, even in deny/nonInteractive deployments — the repo's own CI asserts this bypass ('参数 glob ls* allow 放行(绕过 L3)').
- lowPermission gate declares ecoAudit in `inject` although the linkage is written as optional, so the gate is not applied when only the gate is installed
packages/eco-permission-gate/src/index.ts:58cordis holds back a plugin whose declared dependencies are unavailable, so a deployment that enables eco-permission-gate without eco-audit-chain (or with it renamed/failed) gets no pre-execute gate at all while believing tool calls are risk-gated — a silent fail-open of the security control. The bundled patch always ships all three, so this only bites partial/custom installs.
No RCE, obfuscation or exfiltration in the runtime plugins; the residual risk is the permission gate's prefix/glob matching on raw command strings, which command chaining can bypass.
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-08-18 · activity: Inactive
• Repo created: 2026-08-18
• Stars: ★ 0 · Forks: 0
• Health: Inactive — no commit in 90+ 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).
Frequently asked questions
What is eco-dsh-plugins?
eco-dsh-plugins is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
Is dsh.so or this plugin page official?
dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.
How do I install eco-dsh-plugins?
Run dsh plugin --profile web add github:xiejianjun000/eco-dsh-plugins in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
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, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.
How fresh is the data on this page?
The data on this page is as of 2026-11-19 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.
