Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Unofficial Windows guard that snapshots old file bytes and blocks destructive file operations during unattended DSH workflows.
- Snapshots previous file bytes before ordinary edits, no per-op confirmation
- Refuses permanent deletion and offers a recoverable removal tool instead
- Snapshot cap is 64 MiB per old file; not a sandbox or full backup
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.
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); the npm pair from every snapshot.
4 samples (roughly every 7 days), 2 of them reconstructed (hollow dots); sampled points, not a daily series
09-21 → 10-22 · 4 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-01 → 10-22 · 3 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:SPX43JL/dsh-safekeep#v0.1.0-rc.1Install method: GitHub · runtime verified (L5) · verified on dsh 0.2.1-rc.5
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.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| v0.1.0-rc.1 | ✓ | ✓ | ✓ | ✓ | ✓ |
v0.1.0-rc.1github✓ 8 runtime-verified2026-11-04
https://github.com/SPX43JL/dsh-safekeep
✓dsh 0.2.1-rc.52026-10-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/SPX43JL/dsh-safekeep#v0.1.0-rc.1
ID: dsh-safekeep@v0.1.0-rc.1@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
View checks & evidence
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@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.
✓dsh 0.2.1-rc.32026-10-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/SPX43JL/dsh-safekeep#v0.1.0-rc.1
ID: dsh-safekeep@v0.1.0-rc.1@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@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.
✓dsh 0.2.1-rc.22026-10-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/SPX43JL/dsh-safekeep#v0.1.0-rc.1
ID: dsh-safekeep@v0.1.0-rc.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@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.
✓dsh 0.2.1-alpha.42026-10-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/SPX43JL/dsh-safekeep#v0.1.0-rc.1
ID: dsh-safekeep@v0.1.0-rc.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
View checks & evidence
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@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.
✓dsh 0.2.1-alpha.22026-10-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/SPX43JL/dsh-safekeep#v0.1.0-rc.1
ID: dsh-safekeep@v0.1.0-rc.1@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
View checks & evidence
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@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.
✓dsh 0.2.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/SPX43JL/dsh-safekeep#v0.1.0-rc.1
ID: dsh-safekeep@v0.1.0-rc.1@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@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.
✓dsh 0.1.7-rc.22026-09-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/SPX43JL/dsh-safekeep#v0.1.0-rc.1
ID: dsh-safekeep@v0.1.0-rc.1@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-27 · expires: 2026-10-04
View checks & evidence
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@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.
✓prehistory2026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/SPX43JL/dsh-safekeep#v0.1.0-rc.1
ID: dsh-safekeep@v0.1.0-rc.1@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-safekeep@v0.1.0-rc.1@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.
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:
`[](https://www.dsh.so/artifact/dsh-safekeep/?ref=badge)``[](https://www.dsh.so/artifact/dsh-safekeep/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-safekeep/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-safekeep/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-safekeep/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-safekeep/?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 low (authoritative when present) → overall low.
v0.1.0-rc.1dsh manifestv0.1.0-rc.1git2026-11-05v0.1.0-rc.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- criticalshellExec · shell
lib/storage.mjs:45const { stdout } = await exec(pwsh(), ['-NoLogo', '-NoProfile', '-NonInteractive', '-File', fileURLToPath(new URL('./storage-acl.ps1', impor - warningshellExec · shell
lib/powershell.mjs:14const child = execFile(pwsh(), ['-NoLogo', '-NoProfile', '-NonInteractive', '-File', parserPath], - warningfsWrite · files
lib/recovery.mjs:22await fs.appendFile(filePath, `${JSON.stringify(value)}\n`, { encoding: 'utf8', mode: 0o600 }) - warningfsWrite · files
lib/safe-temp.mjs:23await fs.appendFile(registryPath, `${JSON.stringify(entry)}\n`, { encoding: 'utf8', mode: 0o600 }) - warningfsWrite · files
lib/safe-temp.mjs:73await fs.writeFile(path.join(realDirectory, MARKER), `${JSON.stringify(marker, null, 2)}\n`, { encoding: 'utf8', flag: 'wx', mode: 0o600 }) - warningfsWrite · files
lib/storage.mjs:40try { await fs.writeFile(marker, JSON.stringify({ format: 'dsh-safekeep-storage', schema: 1 }), { flag: 'wx' }) }
show 3 audit findings
- lowGuard resolves pwsh via env var / bare name instead of a pinned absolute path
lib/storage.mjs:11Every PowerShell parse (lib/powershell.mjs execFile at line 14) and the storage-ACL step use this value. Setting DSH_SAFEKEEP_PWSH, or planting a pwsh.exe in the host process's working directory (Windows resolves a bare image name through the current directory before PATH), makes the guard execute attacker-chosen code with the user's privileges. Not reachable from tool arguments; requires control of the host environment or of the process CWD.
- lowSecurity-critical guard modules and PowerShell helper scripts are absent from the reviewed source
lib/powershell.mjs:8The allow/deny classifier (lib/guard-core.mjs), the trash mover (lib/safe-trash.mjs) and the two executed scripts (powershell-analysis.ps1, storage-acl.ps1 via lib/storage.mjs secureDirectory) are not part of the provided source, so the plugin's key safety claims - 'the parser reads text; it never executes the supplied command' and the ACL hardening of ~/.dsh-safekeep - could not be verified. No malicious behaviour is visible in the reviewed files themselves.
- lowPowerShell analyzer creates snapshots only for cmdlet writes; .NET member-call mutations get none
lib/powershell.mjs:9Reachable snapshot targets are produced only from redirects and from this cmdlet allow-list. A Windows pwsh tool call such as [System.IO.File]::WriteAllText('C:\\data\\x.txt', '...') is passed to classifyCommand as memberCalls text for risk classification but never produces a target, so no recovery snapshot is taken; if the (unreviewed) classifier does not block it, the mutation proceeds unrecoverably. The plugin itself lists such paths as unobserved.
Refuted scan critical: pwsh is spawned via execFile with fixed args and command on stdin, no shell, so not injectable. Residual risk is low only.
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-21 · activity: Stable
• Repo created: 2026-09-20
• Stars: ★ 1 · Forks: 0
• Health: Stable — committed within 90 days
Source
GitHub: github.com/SPX43JL/dsh-safekeep
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 @SPX43JL/dsh-safekeep?
@SPX43JL/dsh-safekeep 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 @SPX43JL/dsh-safekeep?
Run dsh plugin --profile web add github:SPX43JL/dsh-safekeep#v0.1.0-rc.1 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-05 (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.