Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Provides a Claude Code style full-screen interactive terminal UI for DSH, featuring a pixel whale top bar, real-time status, streaming thinking, and progress meters.
- Full-screen interactive terminal UI (TUI)
- Pixel whale top bar and real-time work status line
- Streaming thinking, double-Esc rollback, context progress + TPS meter
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 @deepseek-harness-tui/dsh-tui@0.20.0security scan passed · npm package v0.20.0
Install method: npm · sandbox install failed (L4) · verified on dsh 0.2.1-rc.5
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-13) · 7 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-08 · 7 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-08 · 6 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-11 → 11-11 · 56 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
09-11 → 11-13 · 56 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
Based on 4 requirement(s) across 37 @deepseek-ai/dsh-* packages. raw ranges
^0.1.0-rc.6 || ^0.1.1-rc.1 || 0.1.2-alpha.3 || 0.1.2-alpha.4 || 0.1.2-alpha.5 || 0.1.2-rc.1 || 0.1.3-alpha.2 || 0.1.5-alpha.1 || 0.1.5-alpha.2 || 0.1.5-rc.1 || 0.1.7-rc.1 || 0.1.7-rc.2 || 0.2.0-rc.1 || 0.2.0-rc.2 ×28 0.2.0-rc.2 ×5 0.1.7-rc.1 || 0.1.7-rc.2 || 0.2.0-rc.1 || 0.2.0-rc.2 ×2 0.2.0-rc.1 || 0.2.0-rc.2 ×2
✗ Running dsh 0.2.2-rc.2 is outside the declared range — the official install gate rejects it (incompatible-version).
To force-install, grant an exact-version exemption: dsh plugin allow-version dsh-tui-3@0.15.0 0.2.2-rc.2 (the exemption lives in the local profile; this site does not assume one)
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.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| 0.20.0 | · | · | · | · | · |
| 0.19.0 | · | · | · | · | · |
| 0.18.0 | · | · | · | · | · |
| 0.17.0 | · | · | · | · | · |
| 0.16.1 | · | · | · | · | · |
0.20.0npm2026-11-13
@deepseek-harness-tui/dsh-tui
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.19.0npm2026-11-07
@deepseek-harness-tui/dsh-tui
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.18.0npm2026-11-04
@deepseek-harness-tui/dsh-tui
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.17.0npm2026-10-30
@deepseek-harness-tui/dsh-tui
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.16.1npm2026-10-21
@deepseek-harness-tui/dsh-tui
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-tui-3/?ref=badge)``[](https://www.dsh.so/artifact/dsh-tui-3/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-tui-3/?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 low (authoritative when present) → overall low.
v0.20.0dsh manifest0.20.0npm2026-11-130.20.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
The artifact has changed (audited npm 0.19.0 → current npm 0.20.0): the conclusion is still counted conservatively and has been queued for re-audit; it is replaced once that audit lands.
show 1 audit findings
- lowWindows default disables both sandbox confinement and approval prompts
cordis.patch.yml:179On win32 every session starts with danger-full-access and, via the approval row below (`policy: ... 'win32' ? 'never' : ...`), with no confirmation prompt. Combined with the always-on AGENTS.md injection and skill catalogs, untrusted repository text reaching the model can translate into unconfirmed local command execution on Windows. This is an explicitly documented design choice (no win32 sandbox backend), not hidden behaviour, but it is a real reduction of the safety bar on that platform.
Config-only harvest: cordis patches use !!js expressions that read env vars and loader state, with no network, exec or secret handling; only the documented Windows no-sandbox default lowers the bar.
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-11-13 · activity: Active
• Repo created: 2026-08-13
• Stars: ★ 7,594 · Forks: 361
• Health: Active — committed within last 30 days
Source
GitHub: github.com/ccch1mneyyy/dsh-TUI
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-TUI?
dsh-TUI 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-TUI?
Run dsh plugin --profile web add @deepseek-harness-tui/dsh-tui@0.20.0 in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run yet.
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-13 (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.