Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
Migrate your Claude Code setup (skills, MCP, hooks, instructions) into DeepSeek Harness with one command.
- One-command migration from Claude Code to DSH
- Transfers skills, MCP servers, hooks, and instructions
- Simplifies moving your entire agent setup
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 dsh-moveinInstall method: npm · runtime verified (L5) · verified on dsh 0.2.2-rc.1
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.
current (registry 2026-11-12) · 10 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-08 · 10 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-08 · 9 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
08-17 → 11-11 · 73 points
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
08-17 → 11-14 · 74 points
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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin ＼ dsh | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| 0.13.8 | ✓ | ✓ | ✓ | ✓ | ✓ |
| 0.13.7 | · | · | · | · | · |
| 0.12.1 | · | · | · | · | · |
| 0.11.1 | · | · | · | · | · |
0.13.8npm✓ 16 runtime-verified2026-11-14
dsh-movein
✓dsh 0.2.2-rc.12026-11-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-11
View checks & evidence
active in loader tree (150 entries)
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-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
View checks & evidence
active in loader tree (150 entries)
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-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
active in loader tree (150 entries)
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-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
active in loader tree (150 entries)
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-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
View checks & evidence
active in loader tree (150 entries)
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-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
active in loader tree (150 entries)
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-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
active in loader tree (150 entries)
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-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
active in loader tree (150 entries)
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-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
active in loader tree (150 entries)
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-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
active in loader tree (150 entries)
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-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
active in loader tree (150 entries)
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-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
active in loader tree (150 entries)
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-13L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
View checks & evidence
active in loader tree (150 entries)
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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
View checks & evidence
active in loader tree (150 entries)
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-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
active in loader tree (151 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-movein@0.13.8
ID: dsh-movein@0.13.8@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.13.7npm✓ 1 runtime-verified2026-09-04
dsh-movein
✓dsh 0.1.2-rc.12026-09-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: npm · dsh-movein@0.13.7
ID: dsh-movein@0.13.7@dsh0.1.2-rc.1 · profile: l5-web-smoke
Issued: 2026-09-04 · expires: 2026-12-03
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.12.1npm2026-09-08
dsh-movein
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.11.1npm2026-08-24
dsh-movein
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
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-movein/?ref=badge)``[](https://www.dsh.so/artifact/dsh-movein/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-movein/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-movein/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-movein/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-movein/?ref=badge-install)`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.13.8dsh manifest0.13.8npm2026-11-140.13.8same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (7)
- criticalshellExec · shell
lib/star.mjs:33exec(githubCli, ['auth', 'status', '--hostname', 'github.com'], { - criticalshellExec · shell
lib/star.mjs:37exec(githubCli, ['api', '--hostname', 'github.com', '--method', 'PUT', 'user/starred/sjh9714/dsh-movein'], { - warningchildProcess · code-exec
lib/opencode-hook-plugin.mjs:146const child = spawn(handler.command, args, { - warningfsWrite · files
lib/star.mjs:79fs.writeFileSync(marker, `${new Date().toISOString()}\t${answer}\n`, { flag: 'wx' }); - warningfsWrite · files
lib/to-opencode.mjs:114fs.writeFileSync(dest, value); - warningfsWrite · files
lib/to-opencode.mjs:130fs.writeFileSync(dest, text); - warningfsWrite · files
lib/to-opencode.mjs:187fs.writeFileSync(file, text.endsWith('\n') ? text : `${text}\n`);
show 3 audit findings
- mediumGenerated OpenCode bridge executes project-scope Claude hook commands with no consent gate
lib/opencode-hook-plugin.mjs:146After `dsh-movein --from claude --to opencode --apply`, the plugin installs this generated file as ~/.config/opencode/plugins/claude-hooks.js. That plugin resolves the project root by walking up to .git and loads .claude/settings.json / .claude/settings.local.json from whatever repository is opened, then runs every PreToolUse/PostToolUse `command` hook through a shell with the full process environment, on each tool call. A cloned untrusted repository can therefore execute arbitrary commands with the developer's credentials, with no per-project trust prompt equivalent to Claude Code's approval
- lowCLI prints model-directed instructions telling the host agent to run a star confirmation command
lib/star.mjs:100When CI/agent environment variables are set or stdout is not a TTY, the plugin emits imperative natural-language instructions into tool output addressed to the host agent rather than to the user. An agent that follows them (instead of relaying them) could invoke `--confirm-star yes` and mutate the user's GitHub account without a genuine human decision; the marker file then suppresses any further prompt, so the action is not re-confirmed.
- lowSuccessful migration triggers a self-star written to the user's GitHub account via gh credentials
lib/star.mjs:37After any successful --apply run the CLI offers to add a public star to the author's repository using the user's authenticated gh session (invoked without a shell, so no argument injection). It is consent-gated and CI-skipped, but it is an external, publicly visible account mutation performed by a migration tool rather than by the user through the web UI.
Both static criticals are false positives (consent-gated gh star; generated bridge code is never executed by this plugin). One medium: the generated OpenCode bridge runs project-scope hook commands without consent.
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-10-05 · activity: Stable
• Repo created: 2026-08-15
• Stars: ★ 18 · Forks: 2
• Health: Stable — committed within 90 days
Source
GitHub: github.com/sjh9714/dsh-movein
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 dsh-movein?
dsh-movein is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.
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 dsh-movein?
Run dsh plugin --profile web add dsh-movein in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated 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, 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-14 (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.