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
Standalone Electron desktop client for DeepSeek Harness with self-editing UI, long-context sessions, and plugin support.
- Electron standalone client on port 3998 with isolated DSH HOME
- Edit mode hot-reloads patches/plugins/UI with history & rollback (experimental)
- 400k-token sessions with progressive rendering, zstd replay, session deletion
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:lsz-asd/dsh-chameleonInstall method: GitHub · runtime test inconclusive (L5 unknown) · verified on dsh 0.2.2-rc.3
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.
10 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-17 · 10 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
09-28 → 11-17 · 9 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.2.2-rc.3 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| fe7d12 | · | · | · | · | · |
| 89ecda | ○ | · | · | · | · |
| 5f7651 | · | ○ | ○ | ○ | ○ |
fe7d12github○ 1 ecosystem plugin2026-09-04
github:lsz-asd/dsh-chameleon
○dsh 0.1.2-rc.12026-09-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · github:lsz-asd/dsh-chameleon#fe7d12
ID: dsh-chameleon@fe7d12@dsh0.1.2-rc.1 · profile: l5-web-smoke
Issued: 2026-09-04 · expires: 2026-12-03
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
89ecdagithub○ 1 ecosystem plugin2026-11-15
https://github.com/lsz-asd/dsh-chameleon
○dsh 0.2.2-rc.32026-11-15Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/lsz-asd/dsh-chameleon#89ecdaf934affe87883b234fda92d6085eb508b5
ID: dsh-chameleon@89ecdaf934affe87883b234fda92d6085eb508b5@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-15 · expires: 2026-11-22
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.
5f7651github○ 15 ecosystem plugin1 failed2026-11-05
https://github.com/lsz-asd/dsh-chameleon
○dsh 0.2.2-rc.12026-11-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/lsz-asd/dsh-chameleon (version unstated)
ID: dsh-chameleon@5f7651@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.2.1-rc.52026-10-31Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/lsz-asd/dsh-chameleon (version unstated)
ID: dsh-chameleon@5f7651@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.2.1-rc.32026-10-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/lsz-asd/dsh-chameleon (version unstated)
ID: dsh-chameleon@5f7651@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.2.1-rc.22026-10-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/lsz-asd/dsh-chameleon (version unstated)
ID: dsh-chameleon@5f7651@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.2.1-alpha.42026-10-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/lsz-asd/dsh-chameleon (version unstated)
ID: dsh-chameleon@5f7651@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.2.1-alpha.22026-10-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/lsz-asd/dsh-chameleon (version unstated)
ID: dsh-chameleon@5f7651@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.2.0-rc.22026-10-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/lsz-asd/dsh-chameleon (version unstated)
ID: dsh-chameleon@5f7651@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-rc.22026-09-25Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/lsz-asd/dsh-chameleon (version unstated)
ID: dsh-chameleon@5f7651@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-rc.12026-09-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/lsz-asd/dsh-chameleon (version unstated)
ID: dsh-chameleon@5f7651@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.6-alpha.22026-09-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/lsz-asd/dsh-chameleon (version unstated)
ID: dsh-chameleon@5f7651@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-19 · expires: 2026-09-26
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/lsz-asd/dsh-chameleon (version unstated)
ID: dsh-chameleon@5f7651@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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/lsz-asd/dsh-chameleon (version unstated)
ID: dsh-chameleon@5f7651@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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/lsz-asd/dsh-chameleon (version unstated)
ID: dsh-chameleon@5f7651@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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/lsz-asd/dsh-chameleon (version unstated)
ID: dsh-chameleon@5f7651@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-alpha.12026-09-02Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: artifact unstated (historical)
ID: dsh-chameleon@5f7651@dsh0.1.2-alpha.1 · profile: l5-web-smoke
Issued: 2026-09-02 · expires: 2026-12-01
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/lsz-asd/dsh-chameleon (version unstated)
ID: dsh-chameleon@5f7651@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-chameleon@89ecda…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.
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-chameleon/?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.
—89ecdaf934afgit2026-11-1989ecdaf934afsame versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningchildProcess · code-exec
apps/desktop/src/main.js:190const r = spawnSync('where.exe', ['dsh'], { encoding: 'utf8', windowsHide: true }) - warningchildProcess · code-exec
apps/desktop/src/main.js:222const r = spawnSync('where.exe', ['node'], { encoding: 'utf8', windowsHide: true }) - warningchildProcess · code-exec
apps/desktop/src/main.js:251dshProcess = spawn(node, [bin, '--profile', PROFILE, '--port', String(port)], { - warningfsWrite · files
apps/desktop/src/main.js:58fs.writeFileSync(logFile, `[${new Date().toISOString()}] dsh-chameleon started\n`) - warningfsWrite · files
apps/desktop/src/main.js:63try { if (logFile) fs.appendFileSync(logFile, line + '\n') } catch { /* ignore */ } - warningshellExec · shell
packages/workbench-core/src/index.js:245const out = execFileSync(node, argv, { encoding: 'utf8', timeout: 120000, windowsHide: true }) - warningfsWrite · files
packages/workbench-core/src/index.js:89fs.writeFileSync(hp, JSON.stringify(h, null, 2), 'utf8') - warningfsWrite · files
packages/workbench-core/src/index.js:144fs.writeFileSync(p, args.content, 'utf8') - warningfsWrite · files
packages/workbench-core/src/index.js:218fs.writeFileSync(p, last.prev, 'utf8') - warningfsWrite · files
packages/workbench-ui/src/index.js:70fs.writeFileSync(historyPath(), JSON.stringify(h, null, 2), 'utf8') - warningfsWrite · files
packages/workbench-ui/src/index.js:161fs.writeFileSync(p, last.prev, 'utf8') - warningnetIp · network
scripts/cdp-check.js:8http.get(`http://127.0.0.1:${port}/json`, (res) => {
show 3 audit findings
- mediumworkbench_patch_write writes agent-supplied YAML into the profile patch layer; the guard only inspects the first line
packages/workbench-core/src/index.js:143yamlListGuard only checks that the first non-comment line starts with '- '; everything after it is written verbatim to profiles/<profile>/cordis.patch.yml (or the repo bundle patch). The project's own template states this layer allows `!!js` expressions (see scripts/ensure-home.js: 'id-targeted config overrides, disables, and insert lists; !!js expressions allowed'), and the layer is re-read on every profile boot/HMR. A steered or prompt-injected agent therefore turns one tool call into persistent JS execution inside the harness host process on the next restart, with no confirmation step and n
- mediumworkbench_plugin forwards arbitrary agent-supplied package specs to `dsh plugin add`, which loads on next restart
packages/workbench-core/src/index.js:240spec comes verbatim from the tool argument and is passed to `dsh plugin --profile chameleon add <spec>`; the tool's own description advertises 'github:user/repo or file:path'. The installed package becomes part of the profile bundle layer and its code runs in the host process after the next restart (L2) or HMR (L1), so this is a second agent-reachable path to arbitrary code execution / supply-chain install. execFileSync with an argv array means there is no shell-injection issue; the risk is the install itself, which happens without user confirmation.
- lowLocal HTTP routes do no origin/auth check; rollback overwrites the patch file and status leaks absolute paths
packages/workbench-ui/src/index.js:142The three handlers are registered directly on the workbench webServer and perform no origin, token or CSRF check of their own. POST /__chameleon/rollback accepts a JSON body (sendable cross-origin as a simple text/plain request) and overwrites the patch layer file with the previous snapshot, so any page the user visits or any local process can revert the user's configuration; GET /__chameleon/status additionally returns absolute profile/bundle paths. Impact is limited to configuration rollback and path disclosure, not code execution.
Self-edit workbench: agent tools can rewrite the harness patch layer and install packages (persistent code execution); no backdoor, exfiltration or shell injection found.
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-14 · activity: Inactive
• Repo created: 2026-08-13
• Stars: ★ 1 · Forks: 0
• Health: Inactive — no commit in 90+ days
Source
GitHub: github.com/lsz-asd/dsh-chameleon
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-chameleon?
dsh-chameleon 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-chameleon?
Run dsh plugin --profile web add github:lsz-asd/dsh-chameleon 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-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.
