Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
Automatic, versioned backup of your DeepSeek Harness home to your own private git repository. Cross-platform, configurable, never silent about failures.
Installation
dsh plugin --profile web add github:wwwangzilin/dsh-auto-syncInstall method: GitHub · 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 |
|---|---|
| c176df | ✓ |
c176dfgithub✓ 1 runtime-verified2026-10-19
https://github.com/wwwangzilin/dsh-auto-sync
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/wwwangzilin/dsh-auto-sync (version unstated)
ID: dsh-auto-sync@c176df@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.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-auto-sync/)``[](https://www.dsh.so/artifact/dsh-auto-sync/)`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 — stricter wins → overall low.
v0.1.0dsh manifest0.1.0git2026-10-210.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (4)
- criticalshellExec · shell
lib/git.mjs:31async exec(args) { - criticalshellExec · shell
lib/git.mjs:39execSync(args) { - warningchildProcess · code-exec
lib/exec.mjs:64const result = spawnSync(command, args, { - warningshellExec · shell
lib/exec.mjs:25execFile(
show 1 audit findings
- lowSnapshot mirror copies the whole home including .credentials.yaml into the worktree; only .gitignore prevents commit
cold-sync.mjs:158The home is copied file-by-file into the snapshot worktree with only the plugin state dir and .cache excluded, so .credentials.yaml (provider API keys) is physically duplicated into the worktree. Commit/push prevention depends on the home .gitignore carrying the .credentials.yaml rule that setup.mjs writes; if that rule were removed or setup never ran, `git add -A` would publish the credentials to the configured remote.
The two static-scan criticals are legitimate backup features (array-based child_process, GitHub API token usage), not exploitable; only a low secrets-copy residual remains.
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-18 · activity: Active
• Repo created: 2026-10-17
• Stars: ★ 0 · 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).
