⚠️ This repository has been renamed: DPH-1121/dsh-session-cleanup — click to visit the new location. Everything below is preserved as originally indexed.
Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Adds per-row delete and delete-all controls to the dsh web client for cleaning up archived session logs.
- Per-row delete for individual archived session logs
- Delete-all to wipe every stored session log at once
- Operates on the real session log files in the dsh web client
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.
3 samples (roughly every 13 days), 2 of them reconstructed (hollow dots); sampled points, not a daily series
09-18 → 10-15 · 3 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
Only 2 points (< 3): no chart yet
10-01 → 10-15 · 2 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:HaydenSmith1121/dsh-session-cleanupInstall method: GitHub · runtime verified (L5) · verified on dsh 0.2.1-rc.2
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.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 |
|---|---|---|---|---|---|
| 7296f6 | ✓ | ✓ | ✓ | ✓ | ✓ |
7296f6github✓ 8 runtime-verified2026-10-19
https://github.com/HaydenSmith1121/dsh-session-cleanup
✓dsh 0.2.1-rc.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/HaydenSmith1121/dsh-session-cleanup (version unstated)
ID: dsh-session-cleanup-2@7296f6@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/HaydenSmith1121/dsh-session-cleanup (version unstated)
ID: dsh-session-cleanup-2@7296f6@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
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-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/HaydenSmith1121/dsh-session-cleanup (version unstated)
ID: dsh-session-cleanup-2@7296f6@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
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-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/HaydenSmith1121/dsh-session-cleanup (version unstated)
ID: dsh-session-cleanup-2@7296f6@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
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.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/HaydenSmith1121/dsh-session-cleanup (version unstated)
ID: dsh-session-cleanup-2@7296f6@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
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-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/HaydenSmith1121/dsh-session-cleanup (version unstated)
ID: dsh-session-cleanup-2@7296f6@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
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.12026-09-23not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/HaydenSmith1121/dsh-session-cleanup (version unstated)
ID: dsh-session-cleanup-2@7296f6@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/HaydenSmith1121/dsh-session-cleanup (version unstated)
ID: dsh-session-cleanup-2@7296f6@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
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-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/HaydenSmith1121/dsh-session-cleanup (version unstated)
ID: dsh-session-cleanup-2@7296f6@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
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-session-cleanup-2/?ref=badge)``[](https://www.dsh.so/artifact/dsh-session-cleanup-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-session-cleanup-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-session-cleanup-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-session-cleanup-2/?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.2dsh manifest0.1.2git2026-10-180.1.2same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (10)
- warningnetIp · network
scripts/baseline-check.mjs:65await fetch(`http://127.0.0.1:${String(port)}/`) - warningnetIp · network
scripts/baseline-check.mjs:74const response = await fetch(`http://127.0.0.1:${String(port)}${path}`) - warningnetIp · network
scripts/compare-servers.mjs:29await probe('live GUI', 'http://127.0.0.1:3080') - warningnetIp · network
scripts/compare-servers.mjs:30await probe('throwaway', `http://127.0.0.1:${process.env['DSH_E2E_PORT'] ?? '3099'}`) - warningnetIp · network
scripts/diagnose-web.mjs:31await fetch(`http://127.0.0.1:${String(port)}/`) - warningnetIp · network
scripts/diagnose-web.mjs:42const response = await fetch(`http://127.0.0.1:${String(port)}${path}`) - warningnetIp · network
scripts/e2e-log.mjs:30await fetch(`http://127.0.0.1:${String(port)}/`, { method: 'HEAD' }) - warningnetIp · network
scripts/e2e-probe.mjs:28await fetch(`http://127.0.0.1:${String(port)}/`, { method: 'HEAD' }) - warningnetIp · network
scripts/probe-live.mjs:12const base = process.env['DSH_LIVE_URL'] ?? 'http://127.0.0.1:3080' - warningnewFunction · code-exec
scripts/smoke.mjs:36const run = new Function('window', 'require', 'module', 'exports', source)
show 2 audit findings
- lowDev script spawns pnpm through a shell with a command name taken from an environment variable
scripts/install-profile.mjs:48On Windows the command string is parsed by cmd.exe; if DSH_PNPM_CLI is attacker-influenced it can inject shell metacharacters and execute arbitrary commands as the developer. Preconditions (manual run of an install helper plus control of the developer's environment) keep real impact low.
- lowRuntime entry points lib/index.js and lib/client.js are absent from the audited source
package.json:13The only code that actually runs in the host process - the session-log directory deletion and archive-set mutation - could not be reviewed for path traversal, authorization, or symlink abuse. This is an audit-coverage gap, not a demonstrated vulnerability.
All risky constructs live in manually-run dev scripts (localhost-only, fixed commands); no runtime-reachable risk was found in the supplied source.
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-01 · activity: Active
• Repo created: 2026-09-18
• 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 @HaydenSmith1121/dsh-session-cleanup?
@HaydenSmith1121/dsh-session-cleanup 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 @HaydenSmith1121/dsh-session-cleanup?
Run dsh plugin --profile web add github:HaydenSmith1121/dsh-session-cleanup 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-01 (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.