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.
Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.Install verification details →
Data as of (UTC)
What it doesAI
Lightweight launcher for deepseek-harness with cross-platform support.
- Lightweight launcher for deepseek-harness
- Cross-platform: Windows, macOS, Linux
- Requires Node.js >= 22
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:XXLxhPLMM/dsh-start#v0.1.6Install method: GitHub · runtime test inconclusive (L5 unknown) · verified on dsh 0.1.7-rc.2
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.
4 samples (roughly every 3 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 10-09 · 4 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
Only 2 points (< 3): no chart yet
10-06 → 10-09 · 2 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○ Ecosystem plugin
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
package manifest not collected — the declared range is unknown.
| plugin \ dsh | dsh 0.1.7-rc.2 | dsh 0.1.7-rc.1 | dsh 0.1.7-alpha.2 | dsh 0.1.6-alpha.2 | dsh 0.1.6-alpha.1 |
|---|---|---|---|---|---|
| v0.1.6 | ○ | · | ○ | ○ | ○ |
| v0.1.4 | · | · | · | · | · |
v0.1.6github○ 8 ecosystem plugin2026-09-25
https://github.com/XXLxhPLMM/dsh-start
○dsh 0.1.7-rc.22026-09-25Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/XXLxhPLMM/dsh-start#v0.1.6
ID: dsh-start-3@v0.1.6@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
not present in web-profile loader inventory
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-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/XXLxhPLMM/dsh-start#v0.1.6
ID: dsh-start-3@v0.1.6@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
not present in web-profile loader inventory
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-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/XXLxhPLMM/dsh-start#v0.1.6
ID: dsh-start-3@v0.1.6@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
not present in web-profile loader inventory
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-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/XXLxhPLMM/dsh-start#v0.1.6
ID: dsh-start-3@v0.1.6@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
not present in web-profile loader inventory
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-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/XXLxhPLMM/dsh-start#v0.1.6
ID: dsh-start-3@v0.1.6@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
not present in web-profile loader inventory
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-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/XXLxhPLMM/dsh-start#v0.1.6
ID: dsh-start-3@v0.1.6@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
not present in web-profile loader inventory
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-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/XXLxhPLMM/dsh-start#v0.1.6
ID: dsh-start-3@v0.1.6@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
not present in web-profile loader inventory
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-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/XXLxhPLMM/dsh-start#v0.1.6
ID: dsh-start-3@v0.1.6@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.
v0.1.4github2026-08-24
https://github.com/XXLxhPLMM/deepseek-harness-desktop
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L4 · Ecosystem plugin (the not-bundle verdict comes from the install step; L5 does not apply). The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
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-start-3/?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.
Static low; dynamic medium (authoritative when present) → overall medium.
—v0.1.6git2026-09-25v0.1.6same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningcurlDownload · network
setup.sh:322curl -L --fail --progress-bar -o "$out" "$url" && return 0 - warningcurlDownload · network
setup.sh:327wget -O "$out" "$url" && return 0 - warningnetIp · network
start.sh:178curl -s -o /dev/null -w "%{http_code}" --connect-timeout 2 --max-time 3 "http://127.0.0.1:$PORT/" 2>/dev/null | grep -qE '^[1-9][0-9][0-9]$' - warningnetIp · network
start.sh:180wget -q --timeout=3 -O /dev/null "http://127.0.0.1:$PORT/" - warningcurlDownload · network
start.sh:178curl -s -o /dev/null -w "%{http_code}" --connect-timeout 2 --max-time 3 "http://127.0.0.1:$PORT/" 2>/dev/null | grep -qE '^[1-9][0-9][0-9]$' - warningcurlDownload · network
start.sh:180wget -q --timeout=3 -O /dev/null "http://127.0.0.1:$PORT/"
show 6 audit findings
- mediumDefault install rewrites the user's global npm registry to a third-party mirror (registry.npmmirror.com)
setup.sh:426In normal (non-debug) mode the script persistently changes the user's ~/.npmrc so every later npm install on that machine — not just this plugin's — resolves packages through registry.npmmirror.com. Any compromise or misbehaviour of that third-party mirror affects all subsequent package resolution. The change is announced in the log, but it is not opt-in and is not reverted.
- mediumNode.js archive is downloaded and executed without checksum or signature verification
setup.sh:316install_node() fetches node-vXX-<os>-<arch>.tar.gz/.zip over HTTPS and immediately unpacks it (tar -xzf "$tmpfile" -C "$INSTALL_DIR" --strip-components=1) and runs it as the node binary; no SHASUMS256.txt/GPG verification is performed. TLS is the only integrity control, so a compromised mirror, DNS/TLS interception or redirect yields code execution as the invoking user (or root when run under sudo).
- mediumGenerated systemd/launchd service runs dsh web as root with a user-supplied bind host
server/server-service.sh:258The generated [Service] unit has no User=/Group= directive (and the launchd plist no UserName), so `dsh web` runs with full root privileges, with Restart=always and Enable now. --host is taken verbatim from the command line and can be set to 0.0.0.0, exposing the network-facing web app as root; any vulnerability in the served application then becomes full host compromise. $PORT/$HOST are also interpolated into the unit/plist without validation.
- loweval of a PATH export line built from unvalidated --dir/NODE_INSTALL_DIR
setup.sh:503export_line is built as export PATH="$INSTALL_DIR/bin:$PATH" where INSTALL_DIR comes from --dir or $NODE_INSTALL_DIR. A value containing a double quote plus command substitution would be executed by eval, and the same line is appended verbatim into ~/.bashrc/.zshrc, giving persistence. Exploitation requires the caller to supply the malicious --dir/env value, so it is only reachable when another tool wraps this script with attacker-influenced arguments.
- lowUnquoted $PORT interpolated into cmd.exe and PowerShell command strings
start.sh:205PORT comes from --port/DSH_PORT (or from parsing a service file) and is inserted without validation into a cmd.exe command string and into PowerShell -Command strings (e.g. Start-Process ... --app=$url). A value containing shell/PowerShell metacharacters would break out of the intended argument. Only a user who already controls the script's arguments can trigger it, so impact is limited to privilege confusion rather than remote attack.
- lowPATH rewriting removes every entry containing 'node'/'nvm' and edits the Windows Machine PATH
setup.sh:573In --debug mode remove_node_from_path() drops any PATH element whose name merely contains 'node' or 'nvm' (substring match, not real ownership), silently breaking unrelated tooling; in non-debug Windows mode promote_user_node() writes the Machine PATH via SetEnvironmentVariable and deletes the corresponding User PATH entries. These are destructive, non-reversible environment changes performed without an explicit confirmation prompt.
Toolchain installer/launcher scripts: no backdoor or exfiltration, but they globally repoint npm at a third-party mirror, run an unverified Node download, and install a root service.
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-19 · activity: Inactive
• Repo created: 2026-08-15
• Stars: ★ 2 · Forks: 1
• Health: Inactive — no commit in 90+ days
Source
GitHub: github.com/XXLxhPLMM/dsh-start
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-start?
dsh-start is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
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-start?
Run dsh plugin --profile web add github:XXLxhPLMM/dsh-start#v0.1.6 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
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-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.
