dsh-backup
One-command backup & restore of DSH user data with a visual Settings panel: scheduled auto-backup, sha256 verification, hardened restore with auto-rollback, typed sub-backups (--types skills), credential redaction into a local vault, GitHub sync for cross-machine moves, and an out-of-process rescue channel that works even when the host won't boot. /backup doctor checks and repairs corrupt session logs from a known-good backup; migrate-check statically predicts which sessions a host upgrade would break (frozen event-list rules, filename/generation mismatch, hardlink support, legacy credentials layout) and the credential sentinel preserves pre-migration copies before the host rewrites them; smart backup snapshots before host upgrades and quarantines corrupt logs before rotation. macOS/Linux/Windows.
On this page
Review info: no independent structural review record is currently matched.
Community signals
Category
Development & Runtime
GitHub stars
19
npm downloads
2,400
Discovery registry added
2026-08-14
Review information
Scanner status
No review data
Review mode
No review data
Last checked
No review data
Build approval required
No review data
Lifecycle scripts
No review data
Runtime artifacts committed
No review data
Documented profiles
No review data
Why this site does not provide the install command
A third-party DSH plugin is executable local code. Even when structural review evidence exists, registry data, stars and metadata cannot prove the code is non-malicious. Read the current author repository and perform your own review in a disposable environment.
Install and usage source
This site links to the author's source, npm page and community registry instead of redistributing commands. A plugin may add Web UI, Settings, agent tools or background capabilities; follow the author README for the actual entry point.
Minimum checks before install
- Confirm package.json, the bundle patch and README belong to the same author repository.
- Inspect preinstall/install/postinstall/prepare, child_process, shell, filesystem, network calls and credential access.
- First install into a disposable profile/workspace without production credentials or an important repository.
- If pnpm asks for allowBuilds/build approval, treat it as permission to execute third-party code during installation; do not approve mechanically.
- For reproducibility, pin an exact npm version or Git commit yourself instead of depending on main/latest.
“Third-party” only means the plugin is not an official DeepSeek plugin. Structural checks improve transparency but cannot prove business logic is non-malicious or fully audit dependencies, future updates or runtime behavior.