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-git-rescue avatar

dsh-git-rescue

DSH git 版本管理 + 崩溃自动救援插件(仅 GitHub token 方案)

Ecosystem appDeveloperStorageGitHub integrationStorage
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 →

Data as of (UTC)

What it doesAI

Git version control and crash auto-recovery for DSH user directories, with GitHub backup.

  • Auto-commit for .dsh and workspace
  • Crash detection and git rollback
  • Guardian self-check and restart
developerAIgithubAIstorageAI

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 L4 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (ecosystem plugins are decided by the install step not-bundle check, so L5 does not apply; the ladder does not rate them); the security scan still runs.

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.

GitHub stars
4★

3 samples (roughly every 5 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series

09-18 → 10-07 · 3 points

Weekly star gain
+0★

Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend

Only 2 points (< 3): no chart yet

10-02 → 10-07 · 2 points

Cumulative downloads
—

Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)

Only 0 points (< 3): no chart yet

no data yet

Weekly downloads
—

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

weekly board —total board —downloads ≠ unique usersstar weekly —

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 \ dshdsh 0.2.0-rc.1dsh 0.1.7-rc.2dsh 0.1.7-rc.1dsh 0.1.7-alpha.2dsh 0.1.6-alpha.2
v2.6.1·····
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
v2.6.1github1 failed2026-09-30

https://github.com/EIGHTfs/dsh-git-rescue

✗dsh 0.1.3-alpha.22026-09-09Ecosystem app · L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.3-alpha.2
  • • Plugin artifact: github · https://github.com/EIGHTfs/dsh-git-rescue#v2.6.1
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
Failed
Sandbox install failed
Ecosystem app · L5 · failed

ID: dsh-git-rescue@v2.6.1@dsh0.1.3-alpha.2 · profile: l3-fullscan

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

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-09-30
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-09-30
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-08
spec github:EIGHTfs/dsh-git-rescue#v2.6.1 · channel GitHub source · outcome ran · exit 0
check took: 2.5s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-08
spec github:EIGHTfs/dsh-git-rescue#v2.6.1 · channel GitHub source · outcome ran · exit 0
check took: 2.5s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-08
spec github:EIGHTfs/dsh-git-rescue#v2.6.1 · channel GitHub source · outcome ran · exit 0
check took: 2.5s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-08
spec github:EIGHTfs/dsh-git-rescue#v2.6.1 · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
plugin tree failed to load
HTTP endpoint served✕ Failed

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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/dsh-git-rescue.svg)](https://www.dsh.so/artifact/dsh-git-rescue/?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.

dsh-git-rescueAutomated review · daily

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

static low→dynamic medium→overall medium
dynamic findings0 critical·0 high·2 medium·2 low
mediumoverall · medium
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin versionv2.6.1dsh manifest
scanned versionv2.6.1git2026-10-07
current versionv2.6.1same version
vet verdictclean · git

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

show static findings (8)
  • warningfsWrite · fileslib/atomic.js:42

    await fs.writeFile(temp, content, { mode, flag: 'wx' })

  • warningfsWrite · fileslib/atomic.js:74

    await fs.writeFile(lockPath, `${process.pid}\n`, { mode: FILE_MODE_600, flag: 'wx' })

  • warningfsWrite · fileslib/atomic.js:126

    await fs.chmod(filename, FILE_MODE_600).catch(() => {})

  • warningchildProcess · code-execlib/process-capture.js:40

    const child = spawn('sh', ['-c', cmd], {

  • warningshellExec · shelllib/process-capture.js:103

    execFile(name, args, { timeout: 3000 }, (err, stdout) => resolve(err ? '' : String(stdout)))

  • warningfsWrite · fileslib/process-capture.js:25

    await fs.appendFile(file, text)

  • warningfsWrite · fileslib/process-capture.js:30

    await fs.writeFile(file, tail)

  • warningfsWrite · fileslib/save-lock.js:63

    await fs.writeFile(join(dshHome, LOCK_FILE), `clean-env-lock v1\ncreated: ${new Date().toISOString()}\n`, 'utf8')

2model reads redacted source context · never executes plugin code
highest grademedium
merged intooverall medium
audited at2026-10-17
audited artifactgit eae5dd1c5d1c812d73412e27b122b52bb9c46d20
findings0 critical·0 high2 medium / 2 low hidden
show 4 audit findings
  • mediumUnrestricted 'sh -c' execution helper whose callers are not in the harvested sourcelib/process-capture.js:40

    startDshWithLog() hands its cmd argument to a real shell, detached and with the plugin's privileges, with no escaping or allow-list. If any caller ever builds cmd from configuration, an HTTP-supplied 'start command', or any non-constant string, this becomes remote/privileged code execution. The guardian/server.js and lib/index.js that would call it were not harvested, so attacker control of cmd cannot be excluded.

  • mediumGuardian panel that collects the admin password is polled/served over plain HTTP with no visible origin gateguardian/public/inject.js:18

    The rescue UI is a cleartext http origin and the injector is explicitly designed to be embedded in arbitrary pages ('在 DSH 主页面(或任意页面)引入本脚本'), which implies the API answers cross-origin without an auth check. lib/admin-password.js documents that this same panel hosts the password form used for privileged operations (提权:Windows 开启 SSH 等), so the admin password can be exchanged over cleartext on a LAN and state-changing endpoints (save password, restart, rollback) have no demonstrated CSRF/origin protection in the harvested code.

  • lowdata/sensitive directory created with default umask instead of 0700lib/admin-password.js:36

    writeFileAtomic passes dirMode 0o700, but mkdir mode only applies when the directory is created; saveAdminPassword creates data/sensitive first with the process umask (commonly 0755), so the admin password sits in a group/other-listable directory together with github-token/sudo-key. File content is still 0600, so the impact is metadata/listing exposure and a weakened hardening baseline, not password disclosure.

  • lowClean-env install lock is advisory and self-exempt, so it is not a real boundarylib/save-lock.js:48

    checkInstallAllowed() is a pure string comparison on a caller-supplied pluginName; the module returns a boolean and enforces nothing by itself, and the locked 'clean baseline' env always allows its own installer. Any caller that passes the string 'dsh-git-rescue' (or simply does not call this function) installs/registers plugins, so the advertised clean-env protection should not be relied on as a security control.

No backdoor or secret exfiltration found; residual medium risks are a shell 'sh -c' execution helper and a cleartext-HTTP guardian panel that collects the admin password.

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

• Repo created: 2026-08-19

• Stars: ★ 4 · Forks: 0

• Health: Stable — committed within 90 days

Source

GitHub: github.com/EIGHTfs/dsh-git-rescue

Frequently asked questions

What is dsh-git-rescue?

dsh-git-rescue is an ecosystem app listed on dsh.so, not a DSH plugin package: it cannot be installed with dsh plugin add and ships through the project's own release channel.

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-git-rescue?

This is an ecosystem app, not a plugin installable via dsh plugin add: desktop / web shells install or deploy through their own release channel. The security scan still runs, but the L1-L5 plugin install ladder does not rate it.

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-10-17 (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.

Was this page helpful?