Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Streams every command the AI assistant runs plus its full stdout/stderr to the DSH WebUI as a live floating console, with per-command log files.
- Live floating console showing command, argv, cwd and session
- Split stdout/stderr with correct ANSI colors and CR overwrite
- Spill-file fallback recovers full output and saves per-command logs
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.
8 samples (roughly every 7 days), 4 of them reconstructed (hollow dots); sampled points, not a daily series
09-17 → 11-01 · 8 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
09-23 → 11-01 · 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
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:akvi0921/dsh-console-tapInstall method: GitHub · runtime verified (L5)
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.1-rc.5 current | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| 82c448 | ✓ | ✓ | ✓ | ✓ | ✓ |
82c448github✓ 10 runtime-verified2026-10-31
https://github.com/akvi0921/dsh-console-tap
✓dsh 0.2.1-rc.5current2026-10-31L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/akvi0921/dsh-console-tap (version unstated)
ID: dsh-console-tap@82c448@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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: github · https://github.com/akvi0921/dsh-console-tap (version unstated)
ID: dsh-console-tap@82c448@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: github · https://github.com/akvi0921/dsh-console-tap (version unstated)
ID: dsh-console-tap@82c448@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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/akvi0921/dsh-console-tap (version unstated)
ID: dsh-console-tap@82c448@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/akvi0921/dsh-console-tap (version unstated)
ID: dsh-console-tap@82c448@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-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.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/akvi0921/dsh-console-tap (version unstated)
ID: dsh-console-tap@82c448@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-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/akvi0921/dsh-console-tap (version unstated)
ID: dsh-console-tap@82c448@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-23not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/akvi0921/dsh-console-tap (version unstated)
ID: dsh-console-tap@82c448@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-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/akvi0921/dsh-console-tap (version unstated)
ID: dsh-console-tap@82c448@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: github · https://github.com/akvi0921/dsh-console-tap (version unstated)
ID: dsh-console-tap@82c448@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.
✓prehistory2026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/akvi0921/dsh-console-tap (version unstated)
ID: dsh-console-tap@82c448@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
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.
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-console-tap/?ref=badge)``[](https://www.dsh.so/artifact/dsh-console-tap/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-console-tap/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-console-tap/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-console-tap/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-console-tap/?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.
v1.0.0dsh manifest1.0.0git2026-11-011.0.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningnetIp · network
install.sh:214say " [dry-run] 检查文件/软链/组合行 + 探测 http://127.0.0.1:$PORT/api/console/status" - warningnetIp · network
install.sh:220code="$(curl -s -o /dev/null -w '%{http_code}' -m 6 "http://127.0.0.1:$PORT/api/console/status" 2>/dev/null || echo 000)" - warningnetIp · network
install.sh:233say " ③ 排查用:curl -s http://127.0.0.1:$PORT/api/console/status | head -40" - warningcurlDownload · network
install.sh:88if curl -fsSL --connect-timeout 8 -m 120 "$tarurl" -o "$TMP_DIR/src.tar.gz" 2>/dev/null; then - warningcurlDownload · network
install.sh:220code="$(curl -s -o /dev/null -w '%{http_code}' -m 6 "http://127.0.0.1:$PORT/api/console/status" 2>/dev/null || echo 000)" - warningnetIp · network
tools/probe.mjs:27const ws = new WebSocket(url, { headers: { Origin: `http://127.0.0.1:${port}` } });
show 5 audit findings
- mediumInstaller fetches plugin code from unofficial GitHub proxies without any integrity check
install.sh:61If github.com is unreachable (or CT_MIRROR is set), fetch_sources falls back to ghfast.top / gh-proxy.com / ghproxy.net: the git clone or the curl tarball (lines 82-90) is authenticated only by TLS to the proxy, with no pinned commit and no hash/signature check before lib/host.js is copied into the profile, where the harness imports it with full Node privileges. A malicious or compromised mirror can substitute arbitrary host-side code.
- mediumEvery command's stdout/stderr is persisted by default to default-permission logs with no enforced size cap
lib/host.js:378All captured output (tokens, env dumps, build secrets printed by commands) is appended to ~/.dsh/console-logs/*.log. openSync is called without a mode and the directory is created with mkdirSync defaults, so files are typically 0644 / dir 0755 — readable by other local users on shared hosts. Additionally deliver() (line 606, writeSync) never checks cfg.fileLogBytes, so the advertised 64 MiB per-stream cap (line 159, also documented in cordis.patch.yml) is not enforced and a chatty command can grow the file until the disk fills.
- lowWS/status endpoints are guarded only by loopback Host/Origin checks, so any local process can read all captured output
lib/host.js:677isTrustedRequest only verifies the Host header is 127.0.0.1/localhost/::1, rejects sec-fetch-site: cross-site and requires Origin to match Host (lines 810-823). That blocks remote and browser cross-origin access, but any local process or other local user's shell can open /api/console with a forged Host header and receive every command's argv plus all stdout/stderr, with no authentication.
- lowinstall.sh/uninstall.sh re-parse constructed command strings with eval
install.sh:48Commands such as run "mkdir -p '$d' && ln -sfn '$PLUGIN_DIR' '$d/$LINK_NAME'" interpolate --profile/DSH_HOME/--source values into a string that eval re-parses; a path containing a single quote or $( ) breaks out and executes arbitrary shell. Reachable only through the user's own arguments/environment (self-inflicted), and the same pattern exists in uninstall.sh line 28, but the installer is meant to be copy-pasted from the README.
- lowImport-time patching of Cordis Context.prototype and unowned route-table deletion bypass the plugin lifecycle
lib/host.js:959The module mutates the framework's Context.prototype (extend/isolate/intercept) as an import side effect to steal a root ctx, and tryHotUpgrade rebinds a running instance's prototype methods (line 72); this runs outside the declared inject/apply lifecycle. reclaimOwnRoutes (lines 132-148) deletes whatever is registered at '/api/console' and '/api/console/status' without verifying ownership, so a co-installed plugin using those paths silently loses its routes.
Installer bootstraps code from unofficial GitHub proxies without hash verification, and the host half logs all command output to default-permission files with no enforced cap.
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-17 · activity: Stable
• Repo created: 2026-09-17
• 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 dsh-console-tap?
dsh-console-tap 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-console-tap?
Run dsh plugin --profile web add github:akvi0921/dsh-console-tap 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-01 (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.