Install verification: Ecosystem app: not installed via dsh plugin add, so the L1-L5 plugin install-verification ladder does not apply; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
Wails desktop shell bridging Reasonix frontend to DSH backend with session, model, project tree, cost, history, and pricing features.
- Native Wails drag eliminating Chromium artifact
- Session, model, and project tree passthrough
- Cost budget, history search, and price calculation
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
Ecosystem apps are not installable via dsh plugin add: desktop / web shells install or deploy through their own release channel (GitHub Releases or the project site).
The level reads L4 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (ecosystem plugins are decided by the install step not-bundle check, so L5 does not apply; the ladder does not rate them); the security scan still runs.
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), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-14 · 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-02 → 11-14 · 8 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 app
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
| plugin \ dsh | dsh 0.1.5-rc.2 | dsh 0.1.3-alpha.2 | dsh 0.1.3-alpha.1 | dsh 0.1.2-rc.1 | dsh 0.1.2-alpha.1 |
|---|---|---|---|---|---|
| v0.1.0 | ◼ | ◼ | ◼ | ◼ | · |
v0.1.0github◼ 4 ecosystem app2026-09-11
https://github.com/sealfly/dsh-reasonix-desktop
◼dsh 0.1.5-rc.22026-09-11Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/sealfly/dsh-reasonix-desktop#v0.1.0
ID: dsh-reasonix-desktop@v0.1.0@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 app
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/sealfly/dsh-reasonix-desktop#v0.1.0
ID: dsh-reasonix-desktop@v0.1.0@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 app
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/sealfly/dsh-reasonix-desktop#v0.1.0
ID: dsh-reasonix-desktop@v0.1.0@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 app
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/sealfly/dsh-reasonix-desktop#v0.1.0
ID: dsh-reasonix-desktop@v0.1.0@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.
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-reasonix-desktop/?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.2.0git2026-11-19v0.2.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
The artifact has changed (audited git e098d065250ac54bdfa0d85a6ac2605e264848b2 → current git a52885ca351854bafd4dc836a148c92c0d43032e): the conclusion is still counted conservatively and has been queued for re-audit; it is replaced once that audit lands.
show 6 audit findings
- mediumfs:read IPC returns any file on disk to the renderer without path confinement
src/main.js:269The renderer-side bridge exposes this directly (preload.js: ReadFile: async (path) => { const body = await ipcRenderer.invoke('fs:read', path); }), so any script running in the page (e.g. an XSS reached through agent-rendered content, or a navigated remote origin) can read arbitrary files such as ~/.ssh/id_rsa, .aws/credentials or the DSH config. Related handlers have the same shape: fs:list base is hard-coded and path.join(base, rel) does not strip '..' (main.js:259-261), and dsh:createFolder runs fs.mkdirSync(target, {recursive:true}) on a renderer-supplied path (main.js:191-194).
- mediumGit commands are built by string concatenation and executed through a shell
src/main.js:275Callers interpolate renderer-supplied paths into that shell string: runGit(cwd, 'diff -- ' + JSON.stringify(path)) (main.js:320) and runGit(cwd, 'log -5 --format=%H|%an|%aI|%s -- ' + JSON.stringify(path)) (main.js:328). JSON.stringify double-quotes and backslash-escapes, but cmd.exe (execSync's shell on Windows) does not treat backslash as an escape, so a path containing a double quote breaks out and appends arbitrary commands. Practical reachability is limited because NTFS/Windows filenames cannot contain '"', so the path coming from 'git status --porcelain=v1 -z' cannot deliver the payload t
- mediumcontextIsolation disabled with a privileged preload and no navigation guard
src/main.js:145preload.js assigns window.go.main.App = AppProxy and window.runtime in the same global context as page scripts, and the proxy fronts privileged IPC (ReadFile, ListDir, git:*, prices:*). No will-navigate / setWindowOpenHandler is registered (main.js:151 only loadFile). Any script running in the page — including one reached by navigating the window to a remote origin the preload will be re-injected into, or an XSS in the agent-content renderer — can call those privileged IPC handlers directly.
- mediumUnpinned DSH package is downloaded and executed at every startup
src/main.js:113ensureDsh() runs before the window opens (main.js:128) and lets npx resolve whatever version of @deepseek-ai/dsh is currently published (also via the node -e wrapper at main.js:108), with no version pin and no integrity check. A compromised npm account, a hijacked release, or a poisoned registry/proxy response results in arbitrary code running with the user's full privileges, with no visible prompt and no way for the user to review what is executed.
- lowfindNode builds a shell command from environment variables
src/main.js:96The candidates include process.env.NODE_EXE (main.js:89) and 'C:\\Users\\' + (process.env.USERNAME || '') + '...' (main.js:92), both interpolated into a command string executed by cmd.exe. An attacker able to influence these environment variables (e.g. a shortcut, wrapper script, or the shipped install script) could inject shell metacharacters; a double quote is required to break out of the surrounding quotes, so this is not directly reachable with ordinary Windows account names.
- lowHard-coded developer workspace path leaks and is used as default working directory
src/main.js:259The same literal appears at main.js:284 (git:changes non-repo fallback) and in preload.js for WorkspaceChanges/WorkspaceGitHistory fallbacks. It discloses the author's Windows user name/host in a published artifact and makes the file browser and change-list fall back to a directory that does not exist for other users, silently degrading the intended confinement of the fs:list base.
Electron bridge to a local DSH service: no critical backdoor, but unrestricted file-read IPC, shell-concatenated git calls, disabled context isolation and unpinned npx execution are real risks.
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-05 · activity: Active
• Repo created: 2026-08-16
• Stars: ★ 1 · Forks: 0
• Health: Active — committed within last 30 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-reasonix-desktop?
dsh-reasonix-desktop is an ecosystem app listed on dsh.so, not a DSH plugin package: it cannot be installed with dsh plugin add and ships through the project's own release channel.
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-reasonix-desktop?
This is an ecosystem app, not a plugin installable via dsh plugin add: desktop / web shells install or deploy through their own release channel. The security scan still runs, but the L1-L5 plugin install ladder does not rate it.
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-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.
