Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.3 · 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
Remote control DeepSeek Harness via QQ: run commands, take screenshots, view files, and chat.
- Remote command execution, screenshot capture, file access via QQ
- Configure allowedUsers whitelist for security
- Requires NapCat or other OneBot 11 bridge
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:ASAKAFENG/dsh-qq-remote#v1.0.0Install method: GitHub · runtime verified (L5) · 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.
8 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-15 · 8 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
10-01 → 11-15 · 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
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
Based on 1 requirement(s) across 2 @deepseek-ai/dsh-* packages. raw ranges
>=0.0.1-rc <2 ×2
✓ Running dsh 0.2.2-rc.5 is within the declared range — install is not blocked by version.
Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| 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 |
|---|---|---|---|---|---|
| v1.0.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
v1.0.0github✓ 17 runtime-verified2026-11-15
https://github.com/ASAKAFENG/dsh-qq-remote
✓dsh 0.2.2-rc.32026-11-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-15 · expires: 2026-11-22
View checks & evidence
active in loader tree (206 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.2-rc.12026-11-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
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: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@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-28L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-28 · expires: 2026-11-04
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-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-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.2.1-alpha.42026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@dsh0.2.1-alpha.4 · 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.22026-10-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-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.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-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.
✓dsh 0.1.7-alpha.22026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@dsh0.1.7-alpha.2 · 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: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
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: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@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-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
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-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-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.1.3-alpha.12026-09-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
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.
✓dsh 0.1.2-rc.12026-09-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
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.
✓prehistory2026-10-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/ASAKAFENG/dsh-qq-remote#v1.0.0
ID: dsh-qq-remote@v1.0.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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.
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-qq-remote/?ref=badge)``[](https://www.dsh.so/artifact/dsh-qq-remote/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-qq-remote/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-qq-remote/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-qq-remote/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-qq-remote/?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 high (authoritative when present) → overall high.
v1.0.0dsh manifestv1.0.0git2026-11-19v1.0.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (10)
- warningfsWrite · files
chat.js:38fs.writeFileSync(chatPath(name), JSON.stringify(state.chats.get(name) ?? [])); - warningfsWrite · files
chat.js:91fs.writeFileSync(p, JSON.stringify(overlay, null, 2)); - warningfsWrite · files
lib/chat.js:38fs.writeFileSync(chatPath(name), JSON.stringify(state.chats.get(name) ?? [])); - warningfsWrite · files
lib/chat.js:91fs.writeFileSync(p, JSON.stringify(overlay, null, 2)); - warningchildProcess · code-exec
lib/util.js:146const monitor = spawn("busctl", ["--user", "monitor"], { stdio: ["ignore", "pipe", "ignore"] }); - warningchildProcess · code-exec
lib/util.js:172const call = spawn("gdbus", [ - warningchildProcess · code-exec
lib/util.js:201child = spawn(bin, args, { cwd, stdio: ["ignore", "pipe", "pipe"] }); - warningchildProcess · code-exec
util.js:146const monitor = spawn("busctl", ["--user", "monitor"], { stdio: ["ignore", "pipe", "ignore"] }); - warningchildProcess · code-exec
util.js:172const call = spawn("gdbus", [ - warningchildProcess · code-exec
util.js:201child = spawn(bin, args, { cwd, stdio: ["ignore", "pipe", "pipe"] });
show 4 audit findings
- highDefault-open QQ whitelist combined with /exec enabled by default allows host command execution
index.js:49The plugin's documented capability is remote shell execution on the host (/exec) and injecting tasks into the local agent, while the shipped default whitelist is empty, which the plugin's own comment defines as 'allow everyone'. A stranger who merely knows the bot's QQ number and sends a message is therefore accepted as controller with no further user action, yielding arbitrary command execution under the DSH process account (mitigated only by whatever check exists in the non-harvested lib/commands.js).
- mediumOneBot access token is written to logs in clear text
lib/onebot.js:19The token (declared with .role('secret') in the schema) is appended to the WebSocket URL and that full URL is passed to log.info, so the credential lands in DSH logs / journald, where it can be read by other local users, log shippers or anyone with log access. Reconnect attempts repeat the leak on every retry.
- mediumUnvalidated session title used as chat memory filename (path traversal)
chat.js:69The /chat <name> path is validated with CHAT_NAME_RE, but the name derived from a session title/agent id is not: chatReply() feeds chatNameFor() straight into loadChat/saveChat, i.e. path.join(CHAT_DIR, name + '.json'). A controller (any QQ user by default) who sets a session title containing '../' makes the plugin read and overwrite an arbitrary '*.json' file writable by the DSH user — e.g. CHAT_DIR + '../../../../.dsh/qq-remote' resolves to ~/.dsh/qq-remote.json (which is re-read as the config overlay) or the profile's package.json, with content shaped by the chat history.
- lowConfig-driven screenshotCommand is executed through /bin/bash -c (local config only)
util.js:109A shell string is executed with no sanitisation, so whoever can set config.screenshotCommand gets code execution. Because that value comes from the schema config or the local ~/.dsh/qq-remote.json overlay (both writable only by the DSH account), no privilege boundary is crossed and no remote input reaches it — the QQ message path only triggers /screenshot, it does not supply the command. Reported as hardening only, and as an amplifier if the config file ever becomes remotely writable (see the chat-filename traversal above).
Empty QQ whitelist default plus /exec enabled lets any QQ user drive the host; token is logged in clear text and chat filenames accept unvalidated session titles.
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-16 · activity: Inactive
• Repo created: 2026-08-15
• Stars: ★ 1 · 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 dsh-qq-remote?
dsh-qq-remote 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-qq-remote?
Run dsh plugin --profile web add github:ASAKAFENG/dsh-qq-remote#v1.0.0 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-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.
