Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Syncs DSH sessions, attachments, settings and workspace project files across computers via your own private GitHub repo.
- Syncs sessions, attachments, model/UI settings and workspace files
- Data stored in your own private GitHub repository
- Each sync pulls remote data and uploads local changes
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 @dpskk2/dsh-chatsyncInstall method: npm · runtime verified (L5)
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.1-rc.2 current | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|
| 0.20.0 | ✓ | ✓ | ✗ |
| v0.20.0 | · | · | · |
0.20.0npm✓ 2 runtime-verified1 failed2026-10-19
@dpskk2/dsh-chatsync
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @dpskk2/dsh-chatsync@0.20.0
ID: dsh-chatsync@0.20.0@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: npm · @dpskk2/dsh-chatsync@0.20.0
ID: dsh-chatsync@0.20.0@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-15L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · @dpskk2/dsh-chatsync@0.20.0
ID: dsh-chatsync@0.20.0@dsh0.2.1-alpha.2 · profile: l3-fullscan
Issued: 2026-10-15 · expires: 2026-10-22
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.20.0github2026-10-14
https://github.com/dpskk2/dsh-chatsync
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-chatsync/)``[](https://www.dsh.so/artifact/dsh-chatsync/)`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 critical — stricter wins → overall critical.
v0.20.0dsh manifest0.20.0npm2026-10-210.20.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (12)
- criticalspawnShell · shell
lib/patches.js:53const r = spawnSync("npm root -g", { shell: true, encoding: "utf8", timeout: 8000, windowsHide: true }); - warningfsWrite · files
lib/index.js:423fs.writeFileSync(cfgFile, JSON.stringify(merged, null, 2) + '\n', 'utf8'); - warningfsWrite · files
lib/merge.js:290fs.writeFileSync(target, buf); - warningchildProcess · code-exec
lib/patches.js:53const r = spawnSync("npm root -g", { shell: true, encoding: "utf8", timeout: 8000, windowsHide: true }); - warningfsWrite · files
lib/patches.js:169fs.writeFileSync(targetPath, payload); - warningfsWrite · files
lib/patches.js:181fs.writeFileSync(backup, current); - warningfsWrite · files
lib/patches.js:182fs.writeFileSync(targetPath, payload); - warningchildProcess · code-exec
lib/sync.js:374const r = spawnSync('git', ['count-objects', '-vH'], { cwd: this.home, windowsHide: true, encoding: 'utf8', timeout: 15000 }); - warningchildProcess · code-exec
lib/sync.js:407child = spawn(cmd, args, opts); - warningchildProcess · code-exec
lib/sync.js:447const r = spawnSync('git', args, { cwd: this.home, windowsHide: true, timeout: timeoutMs, encoding: 'utf8', env: this._gitEnv }); - warningfsWrite · files
lib/sync.js:498fs.writeFileSync(p, JSON.stringify({ ...cfg, ...next }, null, 2) + '\n', 'utf8'); - warningfsWrite · files
lib/sync.js:605fs.writeFileSync(attrsPath, attrs.replace(/\s*$/, '') + '\n' + sessionRule + '\n');
show 3 audit findings
- criticalUnauthenticated /dsh-sync/api/conflict/preview reads arbitrary files (traversal and secrets)
lib/index.js:539Any caller can POST {"path":".credentials.yaml"} to leak DSH API keys, or use ../ traversal to read arbitrary files readable by the DSH process (SSH keys, browser data, etc.) and receive the contents in the JSON response, with no user action required.
- highWorkspace path override API creates arbitrary directories and redirects a synced work tree
lib/index.js:587An unauthenticated POST with an existing workspaceId and any path makes the process mkdir -p anywhere the user can write. That override is then used as the git work tree on the next sync, so the chosen directory's contents can be committed/pushed to the private remote, and a subsequent reset --hard can overwrite or delete files there.
- mediumSynced patch manifests are auto-applied into node_modules without path validation
lib/patches.js:145patch.json/payload files under ~/.dsh/patches (part of the git repo synced from the configured remote) are applied automatically at startup and after every sync. A malicious manifest can point target at ../../<path> to write arbitrary content or overwrite package code, yielding code execution on every synced machine; the remote is only verified to be private, not content-trusted.
Unauthenticated file read in /dsh-sync/api/conflict/preview (traversal, .credentials.yaml) and unvalidated workspace path override; patch auto-apply from synced repo risks code execution.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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-10-02 · activity: Active
• Repo created: 2026-09-01
• Stars: ★ 14 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/dpskk2/dsh-chatsync
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).