The original repository has been deleted or made private. This page is an archival snapshot from indexing time; the install command may no longer work.

dsh-terminal avatar

dsh-terminal

A responsive, tabbed Ghostty terminal for the DeepSeek Harness Web UI

PluginTerminalBrowserTerminal / ShellWeb search
Verification
L3 · Install spec
stale
Risk
Out of scope
Health
Inactive
Trust
Silver

Install verification: sandbox install failed (L4) · tested on dsh 0.1.1-rc.2 · last checked Install verification details →

Data as of (UTC)

What it doesAI

A responsive, tabbed Ghostty terminal panel for DeepSeek Harness Web UI, using WASM and node-pty.

  • VS Code style tabbed terminal
  • Renders via Ghostty WebAssembly
  • Connects to local PTY via node-pty
terminalAI

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:mattismegevand/dsh-terminal

Install method: GitHub · sandbox install failed (L4) · verified on dsh 0.1.1-rc.2

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

Declared DSH compatibilityfrom package.json · peerDependencies
only the declared range >=0.0.1-rc.1

Based on 1 requirement(s) across 1 @deepseek-ai/dsh-* packages.

raw ranges>=0.0.1-rc.1 ×1

✓ Running dsh 0.2.2-rc.3 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).

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
At-a-glance → evidence in the cards below
plugin \ dshdsh 0.1.1-rc.2
f6300e✗
0b9ad7·
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
f6300elocal1 failed2026-08-23
✗dsh 0.1.1-rc.22026-08-23L4 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.1-rc.2
  • • Plugin artifact: artifact unstated (historical)
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Failed
L5 runtime
Not tested
Sandbox install failed
L4 · failed

ID: dsh-terminal-4@f6300e@dsh0.1.1-rc.2 · profile: l4-sandbox

Issued: 2026-08-23 · expires: 2026-08-30

View checks & evidence
L1 · Found✓ Passed
GitHub repo accessible✓ Passed
Source: local cache · Method: repo probe · Captured 2026-08-24
L2 · Structured✓ Passed

plugin layer (dsh.bundle.patch declared)

Manifest parseable✓ Passed
Source: local cache · Method: manifest parse · Captured 2026-08-24
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-08-24
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-08-24
L4 · Install tested✕ Failed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-08-23
spec github:mattismegevand/dsh-terminal · channel GitHub source · outcome ran · exit 1
check took: 4.0s
Install succeeded✕ Failed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-08-23
spec github:mattismegevand/dsh-terminal · channel GitHub source · outcome ran · exit 1
check took: 4.0s
Installed artifact confirmed? Unknown
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-08-23
spec github:mattismegevand/dsh-terminal · channel GitHub source · outcome ran · exit 1
check took: 4.0s
L5 · Run tested– Not tested

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.

0b9ad7github2026-08-24

https://github.com/mattismegevand/dsh-terminal

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

Author badges

Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/dsh-terminal-4.svg)](https://www.dsh.so/artifact/dsh-terminal-4/?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.

dsh-terminal-4Automated review · daily

Static low; dynamic no conclusion (static stands) → overall low.

static low→dynamic no conclusion→overall low
vet findings0 critical·0 high
lowoverall · low
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin versionv0.1.0-rc.1dsh manifest
scanned version0.1.0-rc.1git2026-08-24
current version0.1.0-rc.1same version
vet verdictclean · npm

Vet is an AST static scan (npm artifact or git source).

show static findings (2)
  • criticalchildProcess · code-execsrc/index.ts:2

    import { execFile } from 'node:child_process'

  • warningshellExec · shellsrc/index.ts:216

    execFile('/usr/sbin/lsof', ['-a', '-d', 'cwd', '-p', String(pid), '-Fn'], {

2model reads redacted source context · never executes plugin code

no dynamic conclusion (source harvest or model call failed) — no conclusion is not a pass; the overall rating falls back to the static tier.

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-18

• Stars: ★ 1 · Forks: 0

• Health: Inactive — no commit in 90+ days

Source

GitHub: github.com/mattismegevand/dsh-terminal

Frequently asked questions

What is dsh-terminal?

dsh-terminal 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-terminal?

Run dsh plugin --profile web add github:mattismegevand/dsh-terminal 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-10-22 (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.

Was this page helpful?