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 →
Data as of (UTC)
What it doesAI
An expert agent team that forges DeepSeek Harness (dsh) plugins from scratch all the way to a releasable version.
- Expert agent team dedicated to dsh plugin development
- Covers the full path from zero to release-ready plugin
- Built for the DeepSeek Harness (dsh) plugin ecosystem
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.
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); the npm pair from every snapshot.
9 samples (roughly every 7 days), 5 of them reconstructed (hollow dots); sampled points, not a daily series
09-21 → 11-03 · 9 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
09-28 → 11-03 · 8 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:MYCF711/dsh-plugin-forge#v0.2.0Install method: GitHub · 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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.2-rc.1 current | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| v0.2.0 | ○ | ○ | ○ | ○ | ○ |
v0.2.0github○ 11 ecosystem plugin2026-11-05
https://github.com/MYCF711/dsh-plugin-forge
○dsh 0.2.2-rc.1current2026-11-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/MYCF711/dsh-plugin-forge#v0.2.0
ID: dsh-plugin-forge-6@v0.2.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
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.
○dsh 0.2.1-rc.52026-10-31Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/MYCF711/dsh-plugin-forge#v0.2.0
ID: dsh-plugin-forge-6@v0.2.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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.
○dsh 0.2.1-rc.32026-10-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/MYCF711/dsh-plugin-forge#v0.2.0
ID: dsh-plugin-forge-6@v0.2.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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.
○dsh 0.2.1-rc.22026-10-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/MYCF711/dsh-plugin-forge#v0.2.0
ID: dsh-plugin-forge-6@v0.2.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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.
○dsh 0.2.1-alpha.42026-10-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/MYCF711/dsh-plugin-forge#v0.2.0
ID: dsh-plugin-forge-6@v0.2.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-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.
○dsh 0.2.1-alpha.22026-10-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/MYCF711/dsh-plugin-forge#v0.2.0
ID: dsh-plugin-forge-6@v0.2.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
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.
○dsh 0.2.0-rc.22026-10-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/MYCF711/dsh-plugin-forge#v0.2.0
ID: dsh-plugin-forge-6@v0.2.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
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.
○dsh 0.2.0-rc.12026-09-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/MYCF711/dsh-plugin-forge#v0.2.0
ID: dsh-plugin-forge-6@v0.2.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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.
○dsh 0.1.7-rc.22026-09-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/MYCF711/dsh-plugin-forge#v0.2.0
ID: dsh-plugin-forge-6@v0.2.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-27 · expires: 2026-10-04
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.
○dsh 0.1.6-alpha.22026-09-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/MYCF711/dsh-plugin-forge#v0.2.0
ID: dsh-plugin-forge-6@v0.2.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
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.
○prehistory2026-10-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/MYCF711/dsh-plugin-forge#v0.2.0
ID: dsh-plugin-forge-6@v0.2.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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.
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-plugin-forge-6/?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.2.0v0.2.0git2026-11-05v0.2.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (10)
- warningnetIp · network
scripts/make-forge-presets.mjs:19Isolation — this instance uses DSH_HOME=D:/dsh-1 and serves http://127.0.0.1:43130. The user's everyday deployment is the DSH Desktop harnes - warningmanifest-fs-unfenced · sandbox
presets/forge-captain/agent.cordis.ymlMutating filesystem tool has no explicit fs backend in realm - warningmanifest-search-unfenced · sandbox
presets/forge-captain/agent.cordis.ymlSearch tool reads without an explicit fs mount - warningmanifest-shell-unfenced · sandbox
presets/forge-captain/agent.cordis.ymlShell tool without a sandbox runner or policy in realm - warningmanifest-fs-unfenced · sandbox
presets/forge-releaser/agent.cordis.ymlMutating filesystem tool has no explicit fs backend in realm - warningmanifest-search-unfenced · sandbox
presets/forge-releaser/agent.cordis.ymlSearch tool reads without an explicit fs mount - warningmanifest-shell-unfenced · sandbox
presets/forge-releaser/agent.cordis.ymlShell tool without a sandbox runner or policy in realm - warningmanifest-fs-unfenced · sandbox
presets/forge-reviewer/agent.cordis.ymlMutating filesystem tool has no explicit fs backend in realm - warningmanifest-search-unfenced · sandbox
presets/forge-reviewer/agent.cordis.ymlSearch tool reads without an explicit fs mount - warningmanifest-shell-unfenced · sandbox
presets/forge-reviewer/agent.cordis.ymlShell tool without a sandbox runner or policy in realm
show 3 audit findings
- mediumInjected system prompt tells the agent to install an unpinned third-party GitHub package
lib/index.js:30Whenever ctx.get('agent-teams') is falsy (the normal case, since @nanmicoder/dsh-agent-teams is not declared in dependencies/peerDependencies), this string is placed into the model's system prompt. It instructs the model to run `dsh plugin add github:NanmiCoder/dsh-agent-teams`, a mutable, unpinned third-party git ref that is added to the profile's package.json and executed after a process restart — i.e. code from an external repository can be pulled into the harness on the model's initiative rather than by an explicit user decision.
- lowPreset generator hardcodes machine-specific absolute paths into generated personas
scripts/make-forge-presets.mjs:7The generator (manually run, not shipped in package.json 'files') can only run on the author's machine, and the COMMON block it writes embeds 'DSH_HOME=D:/dsh-1', 'http://127.0.0.1:43130' and 'C:/Users/Administrator/AppData/Roaming/dsh-desktop/harness' into every generated preset persona. Those paths then travel into any deployment where the presets are installed, leaking the author's local layout and giving other instances wrong isolation guidance. No capability escalation — purely hardcoded configuration.
- lowInstall script overwrites skills/presets under a user-supplied DSH_HOME and appends to AGENTS.md
scripts/install-assets.mjs:22The only validation of the target root is existence. The script then cpSync-overwrites existing skills/presets directories and appends the bundled AGENTS.md section to the harness's global agent instructions. Mitigations are present (a .bak-<date> copy before each overwrite, marker-bounded idempotent append, never deletes), and it must be invoked manually, so this is a hardening gap rather than an exploitable path; the .bak name is date-granular and can collide on repeated same-day runs.
Runtime entry lib/index.js only injects a system-prompt section, but that text steers the agent to install an unpinned third-party GitHub package; build/install scripts hardcode machine paths.
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-09-20 · activity: Stable
• Repo created: 2026-09-20
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 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 @MYCF711/dsh-plugin-forge?
@MYCF711/dsh-plugin-forge 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.
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 @MYCF711/dsh-plugin-forge?
Run dsh plugin --profile web add github:MYCF711/dsh-plugin-forge#v0.2.0 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.
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-05 (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.
