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
Adds restart and logout power control buttons to the DSH conversation header, matching official styling.
- Restart session button
- Logout session button
- Matches official DSH layout
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:kgwdonkey/dsh-header-controlsInstall method: GitHub · runtime verified (L5)
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.
9 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-16 · 9 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-05 → 11-16 · 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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| d315fb | · | · | · | · | · |
| a06118 | ✓ | ○ | · | · | · |
| 36d498 | · | ✓ | ✓ | ✓ | ✓ |
d315fbgithub2026-08-24
https://github.com/kgwdonkey/dsh-header-controls
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
a06118github✓ 1 runtime-verified2026-11-16
https://github.com/kgwdonkey/dsh-header-controls
✓dsh 0.2.2-rc.3current2026-11-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/kgwdonkey/dsh-header-controls#a0611843c4366a5e2a1d0d624f511d12d3402fb9
ID: dsh-header-controls@a0611843c4366a5e2a1d0d624f511d12d3402fb9@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
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-12not tested
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/kgwdonkey/dsh-header-controls#a0611843c4366a5e2a1d0d624f511d12d3402fb9
ID: dsh-header-controls@a0611843c4366a5e2a1d0d624f511d12d3402fb9@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-12 · expires: 2026-11-19
View checks & evidence
inventory probe failed (rpc-error) — inconclusive, not a plugin verdict (reinterpreted 2026-11-17)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
36d498github✓ 16 runtime-verified◐ 1 testing2026-11-14
https://github.com/kgwdonkey/dsh-header-controls
✓dsh 0.2.2-rc.12026-11-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-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.
✓dsh 0.2.1-rc.52026-10-31L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@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/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@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-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@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/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@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/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@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.2.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@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: github · https://github.com/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@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/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@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.7-alpha.22026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@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/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-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.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/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@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/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@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/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@dsh0.1.3-alpha.1 · profile: l4-sandbox
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-05not tested
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/kgwdonkey/dsh-header-controls#36d498
ID: dsh-header-controls@36d498@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.2-alpha.12026-09-06not tested
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: github · https://github.com/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@dsh0.1.2-alpha.1 · profile: l3-fullscan
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◐dsh 0.1.1-rc.22026-08-28L4 · testing (install passed, runtime untested)
- • Node.js: v24.14.0
- • DSH: 0.1.1-rc.2
- • Plugin artifact: github · https://github.com/kgwdonkey/dsh-header-controls#36d498
ID: dsh-header-controls@36d498@dsh0.1.1-rc.2 · profile: l3-fullscan
Issued: 2026-08-28 · expires: 2026-09-04
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.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/kgwdonkey/dsh-header-controls (version unstated)
ID: dsh-header-controls@36d498@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.
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-header-controls/?ref=badge)``[](https://www.dsh.so/artifact/dsh-header-controls/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-header-controls/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-header-controls/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-header-controls/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-header-controls/?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.1.8dsh manifest0.1.8git2026-11-170.1.8same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (11)
- criticalshellExec · shell
lib/relaunch-helper.cjs:59const out = execSync(`netstat -ano`, { encoding: 'utf8', windowsHide: true }) - criticalshellExec · shell
lib/relaunch-helper.cjs:116try { execSync(`taskkill /F /T /PID ${pid}`, { windowsHide: true, stdio: 'ignore' }); log(`taskkill ${pid} ok`) } catch (e) { log(`taskkill - warningchildProcess · code-exec
lib/index.js:33const child = spawn(process.execPath, [helper, '6', 'no-browser'], { detached: true, stdio: 'ignore' }) - warningchildProcess · code-exec
lib/relaunch-helper.cjs:88spawn('cmd.exe', ['/c', 'start', '', url], { windowsHide: true, detached: true, stdio: 'ignore' }).unref() - warningchildProcess · code-exec
lib/relaunch-helper.cjs:127const fb = spawn('cmd.exe', ['/c', 'dsh', 'web', '--no-open', '--host', cfg.host], { - warningchildProcess · code-exec
lib/relaunch-helper.cjs:147const child = spawn(cfg.node, [bin, '--profile', cfg.profile, '--no-open', '--host', cfg.host], { - warningnetIp · network
lib/relaunch-helper.cjs:138if (up && openAfter) openBrowser(accessUrl(`http://127.0.0.1:${cfg.port}`)) - warningnetIp · network
lib/relaunch-helper.cjs:162if (up && openAfter) openBrowser(accessUrl(`http://127.0.0.1:${cfg.port}`)) - warningfsWrite · files
lib/relaunch-helper.cjs:23fs.appendFileSync(path.join(launcherDir, 'relaunch-helper.log'), `${new Date().toISOString()} ${msg}\n`, 'utf8') - warningfsWrite · files
lib/relaunch-helper.cjs:134try { fs.writeFileSync(path.join(launcherDir, 'dsh-server.pid'), String(fb.pid), 'ascii') } catch {} - warningfsWrite · files
lib/relaunch-helper.cjs:157try { fs.writeFileSync(path.join(launcherDir, 'dsh-server.pid'), String(child.pid), 'ascii') } catch {}
show 2 audit findings
- lowPrivileged restart/exit routes rely only on socket remoteAddress, with no Host/origin check
lib/index.js:50Authorization for a destructive action (kill/restart of the whole dsh process) rests on the socket peer address. The required custom header does force a CORS preflight, which blocks cross-site form CSRF, and the comment in relaunch-helper.cjs states the dsh web layer needs a per-instance ?token=, which would also stop DNS-rebinding fetches; however if the host web server ever adds permissive CORS or is fronted by a localhost reverse proxy, a web page could reach these routes and terminate the app. The guard fails closed (undefined remoteAddress -> 403).
- lowRelaunch helper spawns binaries and force-kills a PID taken from an unvalidated local JSON config
lib/relaunch-helper.cjs:147%LOCALAPPDATA%\DeepSeekHarness\launcher.config.json supplies node, bin, cwd, port and host, which drive spawn(cfg.node, [bin, ...]) and execSync('taskkill /F /T /PID ' + pid) where pid is whatever process listens on cfg.port. A tampered config gives code execution as this user on the next click of 重启 and can force-terminate an unrelated process that happens to own the configured port. The precondition (write access to the user's own profile / same-privilege writer) means no privilege boundary is crossed, and the PID itself is numeric (Number(m[1])) so it is not injectable.
Restart/exit buttons are loopback+CSRF-header guarded; the exec/taskkill heuristics are a deliberate local relaunch helper, residual risk is unvalidated local config.
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-07 · activity: Stable
• Repo created: 2026-08-16
• 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-header-controls?
dsh-header-controls 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-header-controls?
Run dsh plugin --profile web add github:kgwdonkey/dsh-header-controls 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-17 (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.
