Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Snapshots your Windows desktop session and restores open apps, documents, folders and window positions after a restart or power loss.
- Captures a snapshot of the current Windows desktop session
- Reopens apps, documents and folders after restart or power loss
- Restores window positions so your layout comes back as it was
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 github:FrogFlaying/dsh-deskresumeInstall 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
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.2-rc.1 current |
|---|---|
| 73a33e | · |
| 60d099 | ✓ |
73a33egithub2026-11-10
https://github.com/FrogFlaying/dsh-deskresume
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
60d099github✓ 1 runtime-verified2026-11-10
https://github.com/FrogFlaying/dsh-deskresume
✓dsh 0.2.2-rc.1current2026-11-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/FrogFlaying/dsh-deskresume#60d0996e68d4216c7b3155620aadde0d29067125
ID: dsh-deskresume@60d0996e68d4216c7b3155620aadde0d29067125@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-10 · expires: 2026-11-17
View checks & evidence
↳ carried from earlier record dsh-deskresume@73a33e@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-deskresume@73a33e@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-deskresume@73a33e@dsh0.2.2-rc.1 (l3-fullscan)
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-deskresume/?ref=badge)``[](https://www.dsh.so/artifact/dsh-deskresume/?ref=badge-install)`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.
Static low; dynamic no conclusion (static stands) → overall low.
—60d0996e68d4git2026-11-1160d0996e68d4same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (9)
- warningchildProcess · code-exec
lib/collector.js:64child = spawn(POWERSHELL, args, { windowsHide: true }) - warningchildProcess · code-exec
lib/recent-index.js:63child = spawn(POWERSHELL, [ - warningfsWrite · files
lib/recent-index.js:131fs.writeFileSync(file, utf8, 'utf8') - warningfsWrite · files
lib/reports.js:101fs.writeFileSync(file, JSON.stringify(doc, null, 2), 'utf8') - warningchildProcess · code-exec
lib/restore.js:51const child = spawn(args[0], args.slice(1), options) - warningchildProcess · code-exec
lib/restore.js:54// spawn() resolving only means the process was created, not that its - warningchildProcess · code-exec
lib/restore.js:67const child = spawn('explorer.exe', [folderPath], { detached: true, stdio: 'ignore' }) - warningfsWrite · files
lib/restore.js:119fs.writeFileSync(file, JSON.stringify({ pid: process.pid, startedAt: new Date().toISOString() }), 'utf8') - warningfsWrite · files
lib/restore.js:487fs.writeFileSync(inFile, JSON.stringify(placements), 'utf8')
not in the dynamic queue (the queue only covers plugins whose static tier is medium or above — medium/high/critical; since 2026-10-24 entries rated low are not audited even when dsh-only rules logged warnings) — this does not mean the dynamic audit found it safe.
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-11-03 · activity: Active
• Repo created: 2026-11-03
• 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).
Frequently asked questions
What is @FrogFlaying/dsh-deskresume?
@FrogFlaying/dsh-deskresume is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.
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 @FrogFlaying/dsh-deskresume?
Run dsh plugin --profile web add github:FrogFlaying/dsh-deskresume in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).
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-11-11 (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.