🗑️ The original repository has been deleted or made private. This page is an archival snapshot from indexing time; the install command may no longer work.

dsh-cc-backup

A batteries-included coding agent for DeepSeek Harness — Claude Code-style workflows, your choice of models, TUI, skills, subagents, hooks, MCP, memory, and worktrees.

Ecosystem appDeveloperTerminalKnowledgeAI ModelsTerminal / ShellMemoryFile

Verification

L5 · Ecosystem app

Risk

Out of scope

Health

Stable

Trust

Silver

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 →

What it doesAI

Batteries-included coding agent for DeepSeek Harness: Claude Code-style workflows, TUI, skills, subagents, MCP, memory, worktrees.

Claude Code-style coding workflows
Choose your preferred models
TUI with skills, subagents, hooks, MCP, memory, worktrees

developerAIterminalAImemoryAIfileAI

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

GitHub repository

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 L5 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (the L1-L5 ladder does not rate them); the security scan still runs.

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

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)

◼ Ecosystem app

At-a-glance → evidence in the cards below

plugin ＼ dsh	dsh 0.1.5-rc.2	dsh 0.1.3-alpha.2
v0.4.0	·	◼

Install compatibility (by plugin version, dsh versions within)

Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed

v0.4.0github◼ 1 ecosystem app2026-09-11

https://github.com/jianxx/dsh-cc-backup

◼dsh 0.1.3-alpha.22026-09-09Ecosystem app

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.1.3-alpha.2
• Plugin artifact: github · https://github.com/jianxx/dsh-cc-backup#v0.4.0

Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)

L1 static

Passed

L2 static

Passed

L3 static

Passed

L4 sandbox

Passed

L5 runtime

Unknown

Ecosystem app: not installed via `dsh plugin add` (desktop / web shell) and no install verdict was produced — it ships through its own release channel and the L1-L5 ladder does not rate it (shown as L5 · ecosystem app)

Ecosystem app

ID: dsh-cc-backup@v0.4.0@dsh0.1.3-alpha.2 · profile: l4-sandbox

Issued: 2026-09-09 · expires: 2026-09-16

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-09-11

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-09-11

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-09

spec github:jianxx/dsh-cc-backup#v0.4.0 · channel GitHub source · outcome ran · exit 0

check took: 2.5s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-09

spec github:jianxx/dsh-cc-backup#v0.4.0 · channel GitHub source · outcome ran · exit 0

check took: 2.5s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-09

spec github:jianxx/dsh-cc-backup#v0.4.0 · channel GitHub source · outcome ran · exit 0

check took: 2.5s

L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-09

spec github:jianxx/dsh-cc-backup#v0.4.0 · install mode reused L4 scratch

check took: 45ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

Source: DSH runtime · Method: web boot · Captured 2026-09-09

ready line dsh web: http://127.0.0.1:53500/?token=…

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

Source: DSH runtime · Method: HTTP request · Captured 2026-09-09

path / · HTTP 200 · took 45ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE? Unknown

Source: DSH runtime · Method: plugin inventory query · Captured 2026-09-09

verdict not-found · entries 149

phases: active 121 · null 28

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.

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 official badges in your README to showcase security & install-test status:

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.

dsh-cc-backupAutomated review · daily

Static critical; dynamic low (authoritative when present) → overall low.

static critical→dynamic low→overall low

dynamic findings0 critical·0 high·0 medium·0 low

lowoverall · low

1static scan · vet primaryvet AST static analysis (npm artifact or git source)

Version binding

plugin versionv0.4.0

scanned versionv0.4.0git2026-09-12

current versionv0.4.0same version

vet verdictcritical · git

Vet is an AST static scan (npm artifact or git source).

2dynamic auditmodel reads redacted source context · never executes plugin code

highest gradelow

merged intooverall low

audited at2026-10-24

findings0 critical·0 high

Harvested files are pure helpers, type schemas, TUI components, invariant stubs and a repo-internal build/copy script; no shell, network, secrets or dynamic code execution.

Rule (2026-10-24): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); without one, the static/vet fused tier applies. 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 static/vet.

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-09-07 · activity: Stable

• Repo created: 2026-09-08

• Stars: ★ 1 · Forks: 0

• Health: Stable — committed within 90 days

Source

GitHub: github.com/jianxx/dsh-cc-backup

Plugin notes

What is dsh-cc-backup?

dsh-cc-backup is an ecosystem app maintained by @jianxx, not a DSH plugin package — it cannot be installed via dsh plugin add; desktop / web shells ship through the project's own release channel. It is cataloged on dsh.so as a Developer entry, with a public source repository and automated static security scan.

How do I install dsh-cc-backup?

This is an ecosystem app, not a plugin installable via dsh plugin add: desktop / web shells install or deploy through their own release channel. Its level reads L5 · Ecosystem app; the security scan still runs.

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 (it can produce false positives and miss context), and the dynamic security audit has a model read the harvested source context with secret files stripped and content redacted inline — plugin code is never executed. The dynamic audit only covers plugins static-flagged at warn or above; when it reaches a conclusion that conclusion is authoritative for the combined verdict — it may raise or lower it — and the static/vet fused verdict applies only when there is none. Exemptions stay manual: the audit never writes the suppression list. Neither layer is a manual security audit or an endorsement; before using a plugin, review the repository and installed permissions, and combine both with the verification level (L4/L5) and health signals.

"DeepSeek Harness (dsh) is an open-source agent harness developed by DeepSeek AI. It uses an architecture where everything is a plugin, and is powered by Cordis."
— DeepSeek Harness README

Sources: GitHub repository · DeepSeek Harness README · security scan data · Maintained by dsh.so · Last updated 2026-09-08

dsh-cc-backup

What it doesAI

Installation

Verification & Compatibility◼ Ecosystem app

Author badges

Security Report

Activity

Source

Author README